Date: Wed, 27 Aug 2008 20:02:58 -0500 From: eculp@cloudmaster.info To: freebsd-mobile@freebsd.org Subject: Re: Is 'ath' going to be updated for 7.1-RELEASE ? Message-ID: <20080827200258.96985hbhy2n5urs4@cloudmail.cloudmaster.info> In-Reply-To: <48B45BEB.2090502@freebsd.org> References: <87vdxr9d9y.fsf@chateau.d.lf> <48B42777.1050304@freebsd.org> <48B43D90.8090807@twilley.org> <48B44FCA.9070609@freebsd.org> <48B4526E.8000802@twilley.org> <48B45BEB.2090502@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Sam Leffler <sam@freebsd.org>: > Jack Twilley wrote: >> Sam Leffler wrote: >>> Jack Twilley wrote: >>>> Sam Leffler wrote: >>>>> Ashish Shukla =C3=83 =C3=82=C2=A4=C3=A2=E2=82=AC =C3=83 =C3=82=C2=A4= =C3=82=C2=B6=C3=83 =C3=82=C2=A5=C3=A2=E2=80=9A=C2=AC=C3=83 =C3=82=C2=A4=C3= =82=C2=B7 =C3=83 =C3=82=C2=A4=C3=82=C2=B6=C3=83 =C3=82=C2=A5=C3=82=C2=81=C3= =83 =C3=82=C2=A4=C3=A2=E2=82=AC=C2=A2=C3=83 =20 >>>>> =C3=82=C2=A5=C3=82=C2=8D=C3=83 =C3=82=C2=A4=C3=82=C2=B2 wrote: >>>>>> Hi, >>>>>> >>>>>> Just came across the release schedule of 7.1-RELEASE. I'm wondering i= f >>>>>> new version of 'ath' driver (for Athereos Wireless chipsets) is going >>>>>> to be included or not ? If yes, I'll be glad to try the betas :). >>>>>> >>>>>> >>>>> Not sure what "new version" means. I'm unlikely to have any time to >>>>> look at existing ath problems in RELENG_7 before the release. >>>> I am hoping against hope it means "whatever it takes to make the Asus >>>> Eee PC work without having to follow the steps on the EeeBSD page". I >>>> rebuilt kernel and world today and forgot *again* to do the madwifi >>>> dance. It's getting old. >>> >>> The required hal is not even committed to HEAD yet; there's no way it's >>> going to get into RELENG_7 w/o significant testing. As to "getting old" >>> others are free to pitch in to make things happen. I have very little >>> time for freebsd right now and what time I do have is focused on higher >>> priority issues. >> >> All I can offer is the ability to test. I do not have the skill =20 >> necessary to fix this or I would have written a fix and asked for =20 >> it to be committed. It is amazingly frustrating to know that there =20 >> is a workaround and to see that others consider this a low priority =20 >> issue. >> >> If not you, then who should I ask about committing the new HAL to =20 >> HEAD and helping me check out whatever I need to check out to test =20 >> the fix so the rest of us can have wireless Ethernet working out of =20 >> the box? > > I have repeatedly asked for testing of the 0.10.5.6 hal sitting in =20 > http://www.freebsd.org/~sam on HEAD but not gotten enough results to =20 > commit to HEAD. I've been using ath_hal-20080528.tgz. with HEAD for quite some time =20 and it works great on my AcerAspire 5520-5679. I'm automatically =20 cvsuping, adding the contents of ath_hal-20080528.tgz and rebuilding =20 world and kernel daily with no issues at all. It works perfectly for =20 me. ed > I will not commit a hal to any tree that causes regressions. =20 > Atheros long ago yanked the testing resources I used to validate =20 > hal's for md5release so I am uncertain whether this hal will =20 > introduce regressions. If things go bad I simply don't have the =20 > time to deal with it so nothing has gone in. > > Past that a backport to RELENG_7 is straightforward but again =20 > nothing happens until code is in HEAD. > > I am asking around for someone else to deal with a commit to HEAD. > > Sam > > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080827200258.96985hbhy2n5urs4>