Date: Thu, 18 Jul 2013 19:22:30 +0200 From: CeDeROM <cederom@tlen.pl> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-net@freebsd.org, "freebsd-usb@FreeBSD.org" <freebsd-usb@freebsd.org>, freebsd-hardware@freebsd.org Subject: Re: Atheros AR9002U-2NG based TP-LINK TL-WN822N Ver:2.0 - adding support to FreeBSD Message-ID: <CAFYkXjm698ghQu7o-vFPaqvXy%2B7tTqThWhD3HKR13f=OLOUWoA@mail.gmail.com> In-Reply-To: <CAJ-Vmokd%2BB8zMjAHB4vNE67FWn63JZvkR1wohUgZDr5sLqbJhA@mail.gmail.com> References: <CAFYkXjm13NGT2gasFB9NtsTcw9d=aH9jE=7f6r6GM99sZPTwUA@mail.gmail.com> <CAJ-Vmokd%2BB8zMjAHB4vNE67FWn63JZvkR1wohUgZDr5sLqbJhA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 18, 2013 at 7:06 PM, Adrian Chadd <adrian@freebsd.org> wrote: > It's not uath. It's a different beast entirely. > > Basically, it requires someone with USB clue to write the USB glue > between the ath(4) and ath_hal(4) code and the USB interface. > > Look at what ath9k_htc implements. It uses most of ath9k, but it > implements a data/control pipe over USB and some commands to tell the > firmware to do things (like new/delete client, etc.) Yea, I have grepped the sources and that this chip seems to have already some support, but it needs some more glue to work over USB as you tell Adrian :-) Not sure if I can do this, but I can always try :D :D Be(a)st regards! :-) Tomek Cedro -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXjm698ghQu7o-vFPaqvXy%2B7tTqThWhD3HKR13f=OLOUWoA>