NDIS Wrapper For Wireless LAN Cards Under GPL 222
An anonymous reader writes " Shortly after Linuxant has released their commercial
DriverLoader, Pontus Fuchs
has made an NDIS wrapper available under the GPL.
Since some vendors refuse to release specifications or even a binary Linux-driver for
their Wireless LAN cards he has decided to
solve it himself by making a kernel module that can load Microsoft-Windows NDIS drivers.
ndiswrapper
has been tested with some BroadCom miniPCI cards and it seems to work on some laptops . With some more work it
should be possible to support more cards. Hopefully this will be the case for
the many owners of Linux laptops based on Intel's Centrino technology.
Please contact Pontus if you are interested in helping out!"
That's Easy (Score:5, Informative)
Re:Sweet! (Score:3, Informative)
Re:How (Score:5, Informative)
Platform independent drivers (Score:4, Informative)
Unfortunately Caldera was the main weight behind this, back when they actually did something silly like write code to make money instead of sue. They fell on hard times and essentially pulled support, and it's been dead in the water since.
Re:Double edged sword (Score:1, Informative)
Re:Support supported cards (Score:4, Informative)
Re:one bad thing (Score:4, Informative)
Re:Cross Platform Drivers (Score:2, Informative)
Now, if someone will just write a similar layer for Linux that can load Windows NT filesystem drivers, then I can get read/write access to my NTFS partitions... Hmm...
Re:Support supported cards (Score:4, Informative)
Likewise, I've also been able to use the Linux-WLAN-NG [linux-wlan.com] drivers to make various wireless adapters work under Redhat Linux versions 7.2 and 9. The devices that I have actually used successfully are:
I noticed that the README file included in the download mentioned a "BroadCom" wireless card. I'm curious as to whether or not this is the newer Linksys PCI wireless card (WMP11) which used to work with Linux-WLAN-NG before they changed the friggin' chipset from Prism2 to Broadcom.
Re:Cross Platform Drivers (Score:2, Informative)
Re:Cross Platform Drivers (Score:3, Informative)
Here is a link [reference.com] to a page about it.
It's a neat idea, but I'm not sure how popular it is with hardware makers, and it somewhat constrains the implementation in hardware. The basic underlying princepals of the hardware would have to support the way the high level model is written, as opposed to having the software conform to the software.
It has to be a split driver model, as OS's organize themselves differently, so what would be highly efficient in one would be dog slow in another. This is also why various people recommend not porting a Windows driver to Linux, but to instead write a native Linux driver. Somebody presented a paper on the 10 things not to do while writing a Linux driver.
Notice, that I2C is also how lots of Linux drivers are written for block devices, because lots of block devices have a high layer, a mid layer, and a low level. Normally the high level, and mid layer are similar between lots of drivers, and generally get squeezed into a single driver.
Kirby
Ask Intel (Score:2, Informative)
Frankly, I'm rather surprised that no Linux company has sued them yet, for unfair competition. Disclosing drivers and documentation to one OS maker and hiding it from the others IS unfair competition.