Re: at76c503a and Kernel 2.6.14

On November 10, 2005 4:08, Christoph Biedl wrote:
> Everybody out there: Please test :-)
It doesn't work for my:
Bus 001 Device 009: ID 077b:2219 Linksys WUSB11 V2.6 802.11b Adapter

with Linux-2.6.14.2.

Syslog says:
Nov 12 16:54:48 DigitalMercury kernel: /root/at76c503a/at76c503.c: wlan0: 
mgmt, but not beacon, subtype = 0
Nov 12 16:54:50 DigitalMercury 
kernel: /root/at76c503a/at76c503.c: /root/at76c503a/at76c503.c:2950 assertion 
dev->istate == INIT failed
Nov 12 16:54:51 DigitalMercury kernel: /root/at76c503a/at76c503.c: wlan0: 
set_mib: wait_completion failed with 2
Nov 12 16:54:51 DigitalMercury kernel: /root/at76c503a/at76c503.c: wlan0: 
set_mib (frag threshold) failed: -156
Nov 12 16:54:51 DigitalMercury kernel: /root/at76c503a/at76c503.c: wlan0: 
handle_mgmt_timeout_scan: Bad scan status: CMD_STATUS_UNKNOWN

Out of curiosity, why did your patch patch against a kernel tree?  Did you use 
that kernel_patch.sh script?  (I modified your patch to patch against my 
at76c503a dir)  I should mention that I'm using ad-hoc mode, with "Security 
mode:restricted", and 104bit WEP key.  (apparently 128bit, is really 104...)


> How are the chances to get this driver into the
> main stream kernel anyway?
I think that we would need a permanent maintainer to always make sure that our 
USB driver compiles with the latest kernel.  Interestingly enough, there is 
already at76c50{3,5} stuff in the kernel for PCI, and PCMCIA.  Both need the 
external atmel-firmware (http://www.thekelleys.org.uk/atmel).  Also, one 
wonders what the plan for Linux WPA support is.  I seem to remember there 
being generic WPA support, underneath that generic 802.11 stack.  Probably, 
the thing to do would be to make at76c503a depend on external firmware.  
That's how all of the Debian-derived distributions are packaging it, because 
apparently, our bundled firmware creates some sort of licensing 
conundrum--which thekelleys firmware apparently does not. <shrug>  If that's 
the way the other in-kernel atmel drivers do it, it is reasonable to assume 
that that's the way we'd be expected to do it.

Cheers,
Nick

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBDdoltK7MBjsyBF48RAlxIAJ4ktQCqklaWaWhb/XgFGeQ5nC38mgCg0hFO
3BSYGDNsqqTyyBxpZjZTb7o=
=xlXY
-----END PGP SIGNATURE-----