Date: Sun, 17 May 2009 21:18:14 +0200 From: Lucius Windschuh <lwindschuh@googlemail.com> To: Sam Leffler <sam@freebsd.org> Cc: Weongyo Jeong <weongyo@freebsd.org>, current@freebsd.org Subject: Re: HEADSUP: uath(4) has been committed. Message-ID: <90a5caac0905171218r6de3473le8edcac3dab7e2bb@mail.gmail.com> In-Reply-To: <4A0F419A.2020700@freebsd.org> References: <20090407022956.GA71377@weongyo.cdnetworks.kr> <90a5caac0905161502x3771072n22d58111a235de24@mail.gmail.com> <4A0F419A.2020700@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--0015175707f40df55e046a208abc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 2009/5/17 Sam Leffler <sam@freebsd.org>: > Lucius Windschuh wrote: >> Thanks for porting the driver. > This is not a port of anyone else's driver. Sorry, my fault. I saw the comment in if_uath.c, but Damien's driver is very different, you are right. >> I tried it with a TRENDnet TEW-504UB/EU on CURRENT as of today. >> But there are a couple of problems with that device: >> 1. Different product ID >> My TEW-504UB/EU becomes 0x3207 after loading the firmware. OK, this one = is >> easy to fix: >> Index: sys/dev/usb/usbdevs >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- sys/dev/usb/usbdevs (revision 192196) >> +++ sys/dev/usb/usbdevs (working copy) >> @@ -2425,6 +2425,7 @@ >> =A0product UMEDIA ALL0298V2 0x3204 ALL0298 v2 >> =A0product UMEDIA AR5523_2 0x3205 AR5523 >> =A0product UMEDIA AR5523_2_NF 0x3206 AR5523 (no firmware) >> +product UMEDIA AR5523_3 0x3207 AR5523 >> >> =A0/* Universal Access products */ >> =A0product UNIACCESS PANACHE 0x0101 Panache Surf USB ISDN Adapter >> Index: sys/dev/usb/wlan/if_uath.c >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- sys/dev/usb/wlan/if_uath.c (revision 192196) >> +++ sys/dev/usb/wlan/if_uath.c (working copy) >> @@ -192,6 +192,7 @@ >> =A0 UATH_DEV(NETGEAR3, WPN111), >> =A0 UATH_DEV(UMEDIA, TEW444UBEU), >> =A0 UATH_DEV(UMEDIA, AR5523_2), >> + UATH_DEV(UMEDIA, AR5523_3), >> =A0 UATH_DEV(WISTRONNEWEB, AR5523_1), >> =A0 UATH_DEV(WISTRONNEWEB, AR5523_2), >> =A0 UATH_DEV(ZCOM, AR5523) >> >> I don't know why this device has another product ID with a loaded firmwa= re, >> but perhaps because it is an 802.11a capable device? > > The device works by changing identity once the firmware is downloaded. > One id is for the stick w/o fw and one for the stick w/ fw loaded and > running. I was a bit unclear, but what I meant to say: My device uses a different product ID in warm state (0x3207) than what the driver expects (0x3205). Interestingly, when booting the vendor's driver, the warm product ID is 0x3205. Anyway, with the extra ID, it works. >> >> So, now to the second problem: >> The device works like a charm in 802.11b/g mode (ifconfig wlan0 chanlist >> 1-13) with FreeBSD's firmware. >> But 802.11a scanning does not work. Without the chanlist restrictiong, I= get >> the following messages: >> (plug in the device) >> =A0 ugen4.2: <Atheros Communications Inc> at usbus4 >> (uathload) >> =A0 ugen4.2: <Atheros Communications Inc> at usbus4 (disconnected) >> =A0 ugen4.2: <Atheros Communications Inc> at usbus4 >> (ifconfig wlan create wlandev uath0) >> =A0 wlan0: Ethernet address: 00:14:d1:c0:23:5f >> (ifconfig wlan0 up) >> =A0 uath0: uath_cmdsend: empty inactive queue >> =A0 uath0: could not init Tx queues, error 55 >> =A0 uath0: uath_cmdsend: empty inactive queue >> =A0 uath0: could not set channel, error 55 >> =A0 [...] >> =A0 uath0: could not set channel, error 55 >> =A0 uath0: uath_cmdsend: empty inactive queue >> =A0 uath0: could not write register 0x08 >> =A0 uath0: uath_cmdsend: empty inactive queue >> =A0 uath0: could not set channel, error 55 >> =A0 uath0: could not switch channel >> I'd like to provide additional debugging information. If you need more, >> please tell me what. > > Known problem. =A0Weongoy didn't have a dual-band stick and I never had > time to track down why 5Ghz channels failed. Set OFDM instead of no modulation when setting the 802.11a channel... See the attached mini patch. >> BTW: Could you add a message declaring the device when it is plugged in? >> Something like "uath0: <TRENDnet TEW-504UB wireless LAN adaptor> on usbu= s?" >> and "uath0: ether aa:bb:cc:dd:ee:ff"? > > I thought it did this but perhaps not; we can try to add it. That would be nice. Unfortunately, I can provoke 3 different panics when detaching the running device. But this is sometimes mixed with data corruption on device removal -- on two different machines. I still have no clue which kernel part is guilty. More in a different mail to current@. Lucius --0015175707f40df55e046a208abc Content-Type: application/octet-stream; name="uath-11a-ofdm.patch" Content-Disposition: attachment; filename="uath-11a-ofdm.patch" Content-Transfer-Encoding: base64 X-Attachment-Id: f_fuu456340 SW5kZXg6IHN5cy9kZXYvdXNiL3dsYW4vaWZfdWF0aC5jCj09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KLS0tIHN5cy9kZXYv dXNiL3dsYW4vaWZfdWF0aC5jCShyZXZpc2lvbiAxOTIxMDgpCisrKyBzeXMvZGV2L3VzYi93bGFu L2lmX3VhdGguYwkod29ya2luZyBjb3B5KQpAIC0xNDkyLDcgKzE0OTMsNyBAQAogCWlmIChJRUVF ODAyMTFfSVNfQ0hBTl81R0haKGMpKQogCQlyZXNldC5mbGFncyB8PSBodG9iZTMyKFVBVEhfQ0hB Tl81R0haKTsKIAkvKiBOQjogMTFnID0+J3MgMTFiIHNvIGRvbid0IHNwZWNpZnkgYm90aCBPRkRN IGFuZCBDQ0sgKi8KLQlpZiAoSUVFRTgwMjExX0lTX0NIQU5fRyhjKSkKKwlpZiAoSUVFRTgwMjEx X0lTX0NIQU5fRyhjKSB8fCBJRUVFODAyMTFfSVNfQ0hBTl9BKGMpKQogCQlyZXNldC5mbGFncyB8 PSBodG9iZTMyKFVBVEhfQ0hBTl9PRkRNKTsKIAllbHNlIGlmIChJRUVFODAyMTFfSVNfQ0hBTl9C KGMpKQogCQlyZXNldC5mbGFncyB8PSBodG9iZTMyKFVBVEhfQ0hBTl9DQ0spOwo= --0015175707f40df55e046a208abc--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?90a5caac0905171218r6de3473le8edcac3dab7e2bb>