Linux Kernel Devs Offer Free Driver Development
schwaang writes "Linux Kernel hacker Greg Kroah-Hartman, author of Linux Kernel in a Nutshell has posted an epic announcement on his blog. This could portend increased device compatibility for Linux users, higher-quality drivers, and fewer non-free binary blobs." From the announcement: "[T]he Linux kernel community is offering all companies free Linux driver development... All that is needed is some kind of specification that describes how your device works, or the email address of an engineer that is willing to answer questions every once in a while. If your company is worried about NDA issues surrounding your device's specifications, we have arranged a program... in order to properly assure that all needed NDA requirements are fulfilled. Now your developers will have more time to work on drivers for all of the other operating systems out there, and you can add 'supported on Linux' to your product's marketing material."
I wonder how many companies will be imprudent/progressive enough to take up this offer.
Something bad is coming when people are suddenly anxious to tell the truth.
Seems like a good idea, but it also seems like it would give the device manufacturers an out. "I'm sorry, but we don't officially support the linux operating system". This way they get drivers written for them for free, and don't need to provide any tech support for the device to those users who purchase it for linux. Anyone else see this happening?
"All that is needed is some kind of specification that describes how your device works". They also need some real hardware to test the brand new written drivers. Specifications are not enough. Who will test the real hardware with the fresh drivers in a real-world operation ?
-- Rastignac was here.
Whatever you might say about the Linux community - that it is elitist or sanctimonious or whatever - it is impossible to ignore their commitment to what they believe in. That somebody would be willing to write device drivers for nothing, apparently just to forward the cause of a free operating system, is pretty impressive. Microsoft and Apple can match this devotion only in the ferocity with which they defend their control over their customers, in anti-trust trials and by imposing DRM.
Peter
I think this kind of action, and offer for help is needed by companies. I hope it will be touted enough. What I know is that, companies having really hard times finding skilled coders for developing Linux drivers. Most of them does not care about the specifications, as they have already patents pending for their works, but they can't actually find people to code for Linux and/or they don't willing to pay more than Windows developers for Linux developers for a smaller market.
Is this any different from what Theo De Raadt (from OpenBSD) and others were implying? The only exception being that they believe in 'True, Open Source Software & Documentation' without license or other restrictions, and no accepting ridiculous NDA's for just 'documentation' - hence the BSD license and OpenBSD's goal(s). In the end, Linux will be half OSS half NOT, with NDA's up the wazzo and a huge mess. I used both for now, but personally, I'll stick with OSS as it was originally meant to be. Even Linus Torvalds is losing control of his original ideology too.
LOAD "SIG",8,1
Except Linux has supported _more_ devices than any version of Microsoft-windows for some time now. Okay so most of those drivers are for older hardware that is no longer supported by new versions of Microsoft-windows... but that doesn't change the facts. You need to qualify your statement, and say what you mean. I guess something like "Microsoft Windows gets support for some new devices more quickly than Linux"... thats about it. I am not even sure there is any truth to OSX supporting more of anything than Linux, Apple-mac hardware is all the same after all.
Infact Linux supports more devices that any other operating system ever... and thats one of the advantages of open-source kernel drivers... they are maintained with the Kernel, so they remain usable through kernel architecture changes with zero effort from the original contributer of the device-driver. I am sure Microsoft would love to do this with windows, but of course they cannot, as they don't have the source code to the drivers they did not write themselves.
Not if Linux devs will be signing NDAs. They'll have the info, they'll code up something for linux which works, but everyone else who develops a Free/Open OS will have to fight the battle all over again -- if not be told "Why not use linux? we helped with drivers for THAT!"
Other than the public announcement, how is this any different from the way things already work?
Actually this really is something new, and quite an announcement. It was never the case before that any old random driver would get created by the open source community. The way OSS development generally works is there has to be a strong need, strong backing, or a high fun factor, for things to get done.
Prior to this announcement it's not like there was a group of people dedicated to writing drivers -- just waiting for companies to release new hardware, then they'd scurry to reverse engineer it and write a driver. Nor do companies (generally) release hardware specs in the hopes that others will provide a driver for their product.
A significant portion of initial open source driver development comes from the device manufacturers themselves, and smaller companies without the resources to spearhead these developments simply don't have the ability to have Linux support.
Your conception that "The community already writes free drivers for vendors who provide specs and loan some hardware" isn't true in the vast majority of cases.
This really is a big change, because now anyone can create a hardware device and actually have formal linux support, and have this printed on the box. This creates a formal avenue for companies to easily, reliably, and cheaply have Linux support for their products.
No-one seems to have commented on the fact that if NDA requirements are met the drivers cannot be open source. This doesn't mean fewer binary blobs, it means more.
And what about Vista's new requirement that all hardware mustn't be compromised by hackers or else the drivers will be remotely disabled? Might a company which produced hardware which is part of the DRM stack risk being more likely to be seen as compromised if it has collaborated with the OSS community?
// MD_Update(&m,buf,j);
There are huge advantages to going the driver route rather than wrappers for windows drivers. For a start, the community can update any open drivers, whereas they cannot touch closed windows drivers. There are many to whom open drivers over closed ones is a big deal.
Sorry if I sound pedantic, but we are already "able" to specify a standard driver model. I can specify one right now: the Linux driver model. It's pretty well-documented; just check out "Linux Kernel In a Nutshell" or "Linux Device Drivers" or the Linux kernel source.
Specifying one is not a problem. It's getting OS developers to adopt it that's a problem. Microsoft obviously isn't going to adopt Linux' driver model since they have so much invested in their own. Linux can't adopt Microsoft's because it's proprietary. Most of the reasons are political.
But there are also technical reasons. With a common driver model, you would force every OS to adopt a layer of abstraction or API which they might not want to have. Every layer of API inserted into a system adds overhead and degrades performance. No other OS would have a chance of kicking the ass of any other OS, performance-wise. In fact the performance advantage would go to the OS which the standard was most closely based on. Therefore, no OS wants to adopt any other OS' native model - they would only do a worse job of it by comparison.
Xen implements something like this for block and network devices, and the USB and Bluetooth specifications do something similar for a few categories of device. The problem comes with things like GPUs where each new generation provides some extra functionality that the last one didn't; you'd need to constantly update your driver model to work with the new functionality. It's not impossible, but it does require a standards body that can quickly specify interfaces to the new functionality, which is quite improbably.
I am TheRaven on Soylent News
I'm confused, is it Ubuntu that is writing wireless NIC drivers, or is it projects like Madwifi?
XML causes global warming.
Hopefully we'll see a corresponding announcement by TLF to clear up any doubt.
Like that wasn't one of the most to-the-point comments in this whole thread, and what happens...
YOU GET MODDED 5 FOR "FUNNY"!!!
No wonder the DOJ gets laughed off...
People who fall into the trap of installing and using proprietary video card drivers then later discover that their video card (which still works fine) is no longer "supported" by the latest driver update would disagree with you that "Video cards are already well-supported by their manufacturers.".
I believe this kind of thing happens more than others know, particularly as GNU/Linux distributors that distribute proprietary software make it easier for users to acquire proprietary software (as I understand Ubuntu is working on). Users shouldn't be left without their software freedom, nor should they have to choose between updating their system kernel and using their video card.
Making users helpless and keeping them separate is no way to live. Users need software freedom now.
Digital Citizen