The Battle for Wireless Network Drivers 163
An anonymous reader points out this Jem Matzan article "about the pain Linux and BSD programmers have in trying to obtain/write device drivers for various wireless cards," writing: This article also has a fairly detailed explanation of how wireless firmwares and drivers work. Two of the manufacturers are actively working with the FOSS community without requiring an NDA."
As someone that has been there (Score:5, Interesting)
Trying to develop wireless 802.11 interfaces for embedded platforms I agree that it is a total pain in a arse. I even knew people that I worked with before at broadcom and couldn't get them to kick down the Software API. We finally got a Philips BGW200 system working and that wasn't easy either since even after filling out NDAs we got messed around for a few months trying to get the right documentation.
But now it does seem that Atmel is working with people, and accourding to the article so is raylink.
What you can do to help is if you have choice, support these guys when you have to buy a wireless adapter even if it is a few bucks more.
-M
I know what IBM will do. I don't know why. (Score:4, Interesting)
I don't know about redistribution rights; you can always ask.
If an open-source developer wants to see the source for the adapter microcode, ask about that one too.
Who's afraid of NDAs? (Score:2, Interesting)
Re:As someone that has been there (Score:3, Interesting)
the response was... surprising.
"Due to proprietary and copyright policies of our company, this information is not divulged for end users."
Is the FCC the cause? (Score:3, Interesting)
madwifi info is wrong (Score:1, Interesting)
Re:What bullocks! (Score:2, Interesting)
Main issues I've had were with VIA EHCI usb 2.0 host controller crashing Linux when I tried to use the adapter on my router. I use the Belkin F5D7050 v2000 on my desktop machine in Windows, Linux, and MacOSX. Interestingly enough the Linux and MacOSXdrivers are way better than the windows drivers. In windows 80% of the time I have to "Repair" the adapter, which basically disables & re-enables the drivers. Then 10% of that I have to do it 2 or more times to get it to finally work. Otherwise it can see my network but won't associate. In Linux, 100% of the time it just works. In MacOSX, a generic apple compound device driver wants to take over the adapter before the rt73 driver loads, so I've had to use another driver that grabs the rt73 before apples driver loads, and releases it to the real rt73 driver once its loaded.
Usually within 15-25 seconds of boot the adapter is associated.
There's more needed than just documentation (Score:4, Interesting)
Re:Is the FCC the cause? (Score:4, Interesting)
> on the interpretation of the requirements.
Likely this is true.
In the case of IBM (now Lenovo), their laptops will not boot with a non-IBM-certified wireless mini-PCI card in the system. Their interpretation of the FCC regulations is that the complete laptop, with wireless card, is FCC-certified. Installing a different wireless card, even though it is a standard component, even from IBM itself, and has been FCC-certified by itself, in IBM's opinion, makes the entire laptop no longer certified. Therefore, they must prevent the now non-certified laptop from working so as to meet FCC compliance.
It is a singular interpretation of the rules, as far as I know. There is a simple third-party fix to poke a byte to disable the check, so it can be worked around, but is still aggravating.
While a bit off-topic to wireless drivers, this example shows that the rules are subject to such extreme interpretation. I can easily see the legal department of Intel, et al, deciding some rule would break FCC compliance and thus preventing open sourcing the driver or even making the specifications available.
The reason I use windows... (Score:2, Interesting)