GPL-only symbols and ndiswrapper
Posted Oct 25, 2006 21:08 UTC (Wed) by drag
In reply to: GPL-only symbols and ndiswrapper
Parent article: GPL-only symbols and ndiswrapper
Like maybe spend their time working on something like the BCM43xx drivers instead which eliminate 90% of the reason for having ndiswrapper drivers in the first place?
No joke it's silly to be pissed off about this when they've made allowances for NDIS wrapper in the past. Do you remember the 4k vs 8k kernel stacks and the effect it made on supporting ndiswrapper?
We now have open source drivers aviable for virtually every single wireless device you want. But it depends on distributions for testing and support. The kernel developers can't do it all by themselves..
So they work hard on this support.. The broadcom driver now has decent in-kernel driver. It's not perfect, but it works. This, along with the intel drivers, give you support for the vast majority of 802.11g devices out there.
And as a response to this what do you see happenning? Instead of distribution beta testers troubleshooting these things and sending in bug reports and such so that people can improve on support you get a crapload of howtos on Ubuntu's websites and other distro's websites on how to blacklist the open source drivers and install the ndiswrapper drivers in their place
What sort of BS is that? It's almost like a slap in the face of the people that went through the trouble of reverse engineering the broadcom drivers for driver documentation and a whole 2nd set of people using that documentation for writing decent drivers!
And the same thing with the Ralink drivers. The ralink company released documentation and source code and you have people telling end users that they should blacklist those drivers also and install ndiswrapper!!
To me that is complete bullshit. Distros should work on getting those things working well and ndiswrapper should only be used if nothing else using open source drivers can be made to work in a sane manner.
I know nothing is perfect and that ndiswrapper is legitament way of getting oddball hardware to work.. but maybe, just maybe the Kernel developers are tired of putting up with this crap themselves.
to post comments)