From: Denis V. <vd...@il...> - 2006-02-21 06:53:16
|
On Monday 20 February 2006 20:44, Jacek Jablonski wrote: > Hello! > Version 20060205 worked well for me. 0205 -> 0206 diff is: diff -urpN acx-20060205/Changelog acx-20060206/Changelog --- acx-20060205/Changelog Sat Feb 4 13:28:48 2006 +++ acx-20060206/Changelog Sun Feb 5 14:17:00 2006 @@ -104,6 +104,9 @@ TODO: from Efthym <ef...@gm...>: 13:14:13 wlan0: tx error 0x20, buf 07! 13:14:13 wlan0: tx error 0x20, buf 08! +[20060206] +* Register driver device ids to usb device table + [20060205] 0.3.33 * Andreas Mohr <an...@rh...> - implement much more flexible firmware statistics parsing diff -urpN acx-20060205/usb.c acx-20060206/usb.c --- acx-20060205/usb.c Sat Feb 4 14:46:36 2006 +++ acx-20060206/usb.c Sun Feb 5 14:16:03 2006 @@ -150,10 +150,12 @@ acxusb_ids[] = { {} }; +MODULE_DEVICE_TABLE(usb, acxusb_ids); /* USB driver data structure as required by the kernel's USB core */ static struct usb_driver acxusb_driver = { + .owner = THIS_MODULE, .name = "acx_usb", .probe = acxusb_e_probe, .disconnect = acxusb_e_disconnect, I am sure 20060206 would work equally well. I'd like to know which version started to work worse. > Andreas, as You says that, I will change from 50 to 20. Getting wireless to work needs a lot more thinking about how it actually works (compared to simplicity of wired net). Think about retries: if you had just one tx retry, you've spend enough time to send that one frame without retries at *half tx rate*! Thus even 1 retry is bad. It's ok if you get, say, 1 retry per 10 packets. It's NOT OK if you get them on almost every paskets. If you need many retries in order to successfully tx a frame, you definitely will be better off lowering your max tx rate instead. -- vda |