Discussion:
Atheros AR9002U-2NG based TP-LINK TL-WN822N Ver:2.0 - adding support to FreeBSD
(too old to reply)
CeDeROM
2013-07-18 15:39:17 UTC
Permalink
Hello :-)

I have just bought USB WiFi b/g/n dongle from TP-LINK model TL-WN822B
Ver:2.0 [1] which use following chipsets: Atheros AR9002U-2NG, Atheros
AR7010, Atheros AR9287. It looks nice bacuse it cost ~20EUR it has
external antennas and has very good opinions. Now, I start to think
that finding Ver:3.0 based on RTL8192CU [2] might be a better
choice..? Still I consider Atheros to be a better solution than
Realtek..?

I have made simple modification of /usr/src/sys/dev/usb/usbdevs and
/usr/src/sys/dev/usb/wlan/if_uath.c to get it recognised, but uath
driver seems to only support AR5005UG according to manpage. Is there
any known driver to operate AR9002 chips?

Here is what dmesg shows after my kernel modification/rebuild:

ugen1.3: <ATHEROS> at usbus1
uath0: <ATHEROS USB WLAN, rev 2.00/2.02, addr 3> on usbus1
uath0: could not allocate USB transfers, err=USB_ERR_NO_PIPE
device_attach: uath0 attach returned 12

So it looks this driver will not operate with this chipset..?

Any hints appreciated! :-)
Tomek

[1] http://wikidevi.com/wiki/TP-LINK_TL-WN822N_v2
[2] http://wikidevi.com/wiki/TP-LINK_TL-WN822N_v3
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Adrian Chadd
2013-07-18 17:07:09 UTC
Permalink
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.)



-adrian
Post by CeDeROM
Hello :-)
I have just bought USB WiFi b/g/n dongle from TP-LINK model TL-WN822B
Ver:2.0 [1] which use following chipsets: Atheros AR9002U-2NG, Atheros
AR7010, Atheros AR9287. It looks nice bacuse it cost ~20EUR it has
external antennas and has very good opinions. Now, I start to think
that finding Ver:3.0 based on RTL8192CU [2] might be a better
choice..? Still I consider Atheros to be a better solution than
Realtek..?
I have made simple modification of /usr/src/sys/dev/usb/usbdevs and
/usr/src/sys/dev/usb/wlan/if_uath.c to get it recognised, but uath
driver seems to only support AR5005UG according to manpage. Is there
any known driver to operate AR9002 chips?
ugen1.3: <ATHEROS> at usbus1
uath0: <ATHEROS USB WLAN, rev 2.00/2.02, addr 3> on usbus1
uath0: could not allocate USB transfers, err=USB_ERR_NO_PIPE
device_attach: uath0 attach returned 12
So it looks this driver will not operate with this chipset..?
Any hints appreciated! :-)
Tomek
[1] http://wikidevi.com/wiki/TP-LINK_TL-WN822N_v2
[2] http://wikidevi.com/wiki/TP-LINK_TL-WN822N_v3
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
_______________________________________________
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
CeDeROM
2013-07-18 17:22:52 UTC
Permalink
Post by Adrian Chadd
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
Hans Petter Selasky
2013-07-18 19:41:42 UTC
Permalink
Post by CeDeROM
Hello :-)
Hi,

The atheros driver has the endpoint numbers hardcoded. I recommend using
relative indexes for each interface. Should be trivial to fix. I'll
leave that for the author of the uath driver.

--HPS
Post by CeDeROM
ugen1.3: <ATHEROS> at usbus1
uath0: <ATHEROS USB WLAN, rev 2.00/2.02, addr 3> on usbus1
uath0: could not allocate USB transfers, err=USB_ERR_NO_PIPE
device_attach: uath0 attach returned 12
So it looks this driver will not operate with this chipset..?
Any hints appreciated! :-)
Tomek
[1] http://wikidevi.com/wiki/TP-LINK_TL-WN822N_v2
[2] http://wikidevi.com/wiki/TP-LINK_TL-WN822N_v3
Loading...