On Wed, 04 Jan 2006 09:23:42 -0800 Sam Leffler <sam_at_errno.com> wrote: > Sigh, I can't take any more of this nonsense. wi was one of the first > drivers moved over to use net80211. It is not using "outdated WLAN" > code. The problems with wi are almost entirely due to my being coerced > into bringing updated net80211 code before all the drivers (other than > ath) were ready. I did this because I was PROMISED (in person) that wi > would be maintained and any problems fixed as they arose. That did not > happen and ever since wi has languished. I have several wi cards and I > test them each time I make changes to the net80211 layer to make sure > there are no regressions but there are known outstanding problems that I > am unlikely to work on. Find someone that cares and I will help them > (as I've said numerous times). I may have used the wrong words to describe the problem. I didn't meant to say that the bits from the WLAN framework the wi driver uses are outdated. What I meant was, that the wi driver isn't up-to-date how it uses the WLAN framework code. So the wi driver is "outdated" in this regard, not the net80211 code. Sorry for not finding the right words earlier, and thanks for explaining the issue in a better way. Bye, Alexander. -- Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks. http://www.Leidinger.net Alexander _at_ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 WL http://www.amazon.de/exec/obidos/registry/1FZ4DTHQE9PQ8/ref=wl_em_to/Received on Wed Jan 04 2006 - 16:48:34 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:50 UTC