= 0x
bMaxPacketSize0 = 0x0040
idVendor = 0x148f
idProduct = 0x5370
This is indeed a Ralink RT5370, so run(4) as it attached.
There seem to be at least 4 versions of the “TP-LINK TL-WN321G” all
being Ralink chips.
Earlier versions were indeed Ralink RT25xx based it seems, which is
rum(4
On 27/10/2018 18:50, Bjoern A. Zeeb wrote:
The problem with these dongles is that sometimes there’s a rev A and a
rev B which use entirely different chipsets and hence are entirely
different drivers. That is rarely observable from online shopping sites
or even product packaging. I haven’t ch
On 27 Oct 2018, at 16:01, tech-lists wrote:
Hi,
context: 12-stable amd64
When TP-LINK TL-WN321G usb dongle is inserted, this appears in dmesg:
ugen1.3: at usbus1
..
run0: MAC/BBP RT5390 (rev 0x0502), RF RT5370 (MIMO 1T1R), address
[REDACTED]
..
and run0 appears, and works, yet:
rum(4
Hi,
context: 12-stable amd64
When TP-LINK TL-WN321G usb dongle is inserted, this appears in dmesg:
ugen1.3: at usbus1
run0 numa-domain 0 on uhub3
run0: <1.0> on usbus1
run0: MAC/BBP RT5390 (rev 0x0502), RF RT5370 (MIMO 1T1R), address [REDACTED]
but run(4) says it supports these:
TP-L
