DragonFly BSD
DragonFly kernel List (threaded) for 2012-03
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: ath(4) failing with ath_reset for AR9285


From: Adrian Chadd <adrian@xxxxxxxxxxx>
Date: Mon, 5 Mar 2012 14:12:55 -0800

Hi,

The problem is "dfbsd should port over the ath driver." ;-)

The actual cause is likely radio related - the AR9285 code that Rui
initially ported over was based on what was in ath9k and it was
suitably unfinished. (So it's not Rui's fault, he did a great job with
what he had.) I subsequently found/fixed/ported a bunch of stuff with
an ath9k developer as we *ahem* discovered the ath9k support was
incomplete.

In fact, if the dragonfly bsd guys were interested, I could have my
arm twisted into forking off a "shared" project where we have a shared
ath driver and HAL, and pull it into *BSD as a contrib project.

That way I'd only have to fix bugs once (hah), and everyone could
immediately benefit from it.

What do you all think? You'd (mostly) get 802.11n for free. :-)



Adrian

On 19 January 2012 00:31, ssgriffonuser <ssgriffonuser@gmail.com> wrote:
> I just installed DFBSD on my EEE netbook and the ath driver seems to be
> failing after wpa_supplicant is run.  The connection is established but the
> message "ath_reset" is also printed.  After that message is printed,
> dhclient wlan0 cannot connect to the dhcp server.
>
> I had a similar problem when I installed FreeBSD 8.2 on the same netbook.
>  However, Adrian Chadd had already fixed the problem in -HEAD so I was able
> to update the driver and everything worked fine.
>
> I'm fairly certain that these problems were one in the same but if somebody
> else has any ideas I'm all ears.
>
> If Adrian is listening on this list, do you remember what that problem was?
>  If so, is it something that I can fix or do I need to know the inner
> workings of the ath card that are hidden behind an NDA?
>
> Thanks



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]