Here's an update on the Linux Driver Project. "The Linux Driver Project is alive and well, with over 300 developers wanting to participate, many drivers already written and accepted into the Linux kernel tree, and many more being currently developed. The main problem is a lack of projects. It turns out that there really isn't much hardware that Linux doesn't already support. Almost all new hardware produced is coming with a Linux driver already written by the company, or by the community with help from the company. There are two main classes of hardware, video input devices and wireless network cards, that is not well supported by Linux, but large efforts are already underway to resolve this issue, with the wireless driver issue pretty much taken care of already, however there are a few notable exceptions. Because of this, our main effort has turned into one of education. Educating vendors of how to become members of the Linux kernel community, proper coding standards and procedures, and how to get their code into the kernel tree."
To read all comments associated with this story, please click here.
Member since:2005-07-21
Typical Linux (et al in OSS) thinking. As an end-user I don't care if the problem is in the kernel, the library, or the application. True that as a technical person I can appreciated the differences. When it comes to being a user, it comes down to the question "Can I get similar functionality I had in Windows?" Heck, even if the library did support my scanner, AFAIK, there is no decent application for KDE 4 for scanning with it! Sorry but people need to realise that hardware support means the full stack. Until it is complete, I'll keep XP installed on my machine and I actually hesitate about booting into Linux* since I might need to scan something and I hate rebooting.
* Though I much prefer it.
Member since:2005-11-11
"Typical Linux (et al in OSS) thinking."
Ridiculous. This is a typical arrogant "all developers are demons that must be killed" kind of arrogant comment that seems to plague the Linux world these days.
Suppose you are a car radio manufacturer. I come to you to complain that my car lights are broken.
Me: "My car is broken. Fix it."
You: "The problem is not in the radio. We're only specialized in car radios. You should see a car mechanic if you want your lights fixed."
Me: "Typical 'car people' (et all) thinking! As a driver I don't care whether the problem is in the radio or the lights! Fix it!"
Riiiight. Your comment is like flaming the plumber that he doesn't fix your television.
There is a difference between kernel developers and userland developers, whether you like it or not. It doesn't matter what you say about end users "not caring", it doesn't make the difference go away, nor should the difference go away because if it does, chaos will ensue.
These people are kernel developers who try to help you with their expertise. Their expertise do not lie in userland. Just because you don't understand the difference doesn't mean you have any right to blame them for not being the people responsible for fixing your problems.
Member since:
2005-07-23
"""Category 1 is already being handled very well by the Linux Printing project and the SANE project. Printer and scanner drivers in Linux are userspace programs and libraries and have nothing to do with the kernel at all. If you have any issues with these types of devices, please go ask the developers of those projects about it. They are very knowledgeable, skilled, have vendor contacts, and can do a lot to help resolve your issues. This area is already aptly covered by these people."""
Nonetheless, it would be great if some of those 300 spartans^W kernel developers could help CUPS and SANE anyway.
Edit: since they are underworked and craving for devices to hack on.
Edited 2008-04-08 13:19 UTC