Slashdot Mirror
Novell Delivers Device Driver Breakthrough
An anonymous reader writes "Novell today announced a new Linux device driver process to make it easier for third party device driver writers to integrate their drivers with SUSE Linux." From the article: "The new driver process allows customers to obtain drivers independently of Novell® kernel updates and supplies a straightforward approach third parties can use when developing device drivers for Novell's SUSE® Linux Enterprise products. The new Linux driver process developed by Novell allows hardware and software vendors to provide Linux drivers and driver updates for their products to customers directly and transparently, in a way that is completely integrated with SUSE Linux Enterprise delivery and support."
... it is generally the result of a badly written 3rd party device driver, and the inability of the OS to protect itself from that driver. Have Novell delivered a major breakthrough here (as the article suggests) or the beginnings of a major headache?
I know there will be replies about how the architechure of Linux protects us from some of the risk, but in reality 3rd parties will circumvent any device driver model in an effort to make their device perform optmally, even at the expense of the wider platform.
The Article is a merketing blurb, anybody knows how it's actualy implemented?
Indeed. They keep using the word "process" and I keep thinking "Microkernel!"
In reality, it sounds like a simple driver abstraction layer which will allow commercial entities to plug in binary drivers without any fear of the GPL.
Javascript + Nintendo DSi = DSiCade
Well I hope it is! The last thing we need is a whole bunch of obscure binary blobs running in kernel mode!
http://outcampaign.org/
It is a breakthrough, because having a shitty, flaky, unfixable and unsupportable binary-only driver is better than having no driver at all. Don't use it if you don't like it. As someone who writes closed source device drivers, I sincerely welcome this. Now, if someone just convinced Linus to add this (or similar functionality) to the "vanilla" kernel...
This argument is repeated time and again here on Slashdot and the fact is it is rediculous. Want to know why? Because Novell's customers want it. In fact, they want Suse Linux to run on whatever white-box thrown-together-component list they decide, and having vendors supply drivers to reach that goal makes Novell a more attractive company.
Novell isn't /. - this is the real world. Compatability = greater acceptance = better marketing position & happier customers = more sales. Period.
Excuse my speling.
Making The Bar Project
i hope you burn in hell for writing closed source drivers.
... this isn't 1998 anymore, I understand the need for open source drivers so you can troubleshoot issues with both them and the kernel but, come on now, grow up - either figure out a way to make it so binary only drivers aren't a problem with stability, make a certification process, or forever be stuck with having 1/3rd the devices supported, 1/3rd supported poorly, and 1/3rd oblivious to your existence.
Sad thing is, this probably isn't a troll. You sound like most of the kernel developers who refuse to make a stable API or ABI.
You wonder why Linux has such shitty support? Your attitude and the attitude of the devs
I'll bite, troll, cause I'm bored and you're an especially easy target.
/etc where everything related to a system-wide configuration belongs.
Before this, there was almost no hope at all to get a working driver installed in less than 4 hours.
Wrong. There are many options to getting a driver in less than 4 hours. I did it just this morning (dropped the rt2500 driver back to the pre-smp ebuild). Time? Including compile, less than 5 minutes. I even restarted the network interface without dropping any existing ssh connections.
For all the people out there that are about to go on about apt-get or some stupid distro, here [sic] this: give it up.
See, a distro is a kind of linux operating system thingie, and a apt-get is a package management system thingie. Google is your friend, try looking up concepts once in a while.
Your "points":
We need to get a truly working pluggable driver model.
The content of your post clearly presents the fact that you are not part of the "we" here.
We need to have a registry to track applications, and their installation paths, and installation parameters. (This will help with the install, uninstall, and dependency headaches)
Linux needs no registry. Refer to
We need a unified configuration system and configuration user interface.
There are several: xterm + vi, aterm + emacs, konsole + nano, the combinations are nearly endless!
We need a great GUI development IDE
Again, several. The one that rocks the most IMO is KDevelop for GUI stuff. Emacs works for everything else.
We need to not release products with 200 dependencies that change every 4 weeks
Reference? Oh, wait, no, that sounds like hyperbole.
The only thing Linux has over other operating systems right now, is price.
You meant to say:
The only things Linux has over other operating systems right now are price, power, flexibility, and freedom.
As my children (who use Linux) would say: Go away little boy, and take your long nose with you.
Linux got to where is is precisely because of the kernel devs not producing a stable API. Think about it, what would the kernel be if it was stripped of all the drivers? Not much use at all.
Now that Linux has a large userbase, you're arguing that is ok to relax that since some user wants binary drivers that just work. However, when you go that route, it's hard to go back because everybody *expects* the ABI to remain stable. Instead of improving the kernel, the devs will waste time sorting out ABI issues; not the best use of time.
:. Ultimate Control Dedicated/VM Servers
It just pisses me off how Novell might be very successful in this, and if they are, it has no benefit for Linux (as in, you know, the free/open source side), and quite possibly a negative effect. All this does is benefit Novell, and once companies write up their drivers, where are the rest of us that use real Linux left? In the dust, and possibly moreso, because now the companies can say with a smile on their faces that they support Linux, and may not ever bother to turn back and support the rest of us. Thanks Novell, for giving the world a stabler Windows.
From the point of view of your average home desktop user, being able to install any 3rd-party driver with a single click (and a uniform installation process!) and then automatically track the updates to all installed drivers whenever kernel is updated is a breakthrough. For developers, it means that they no longer have to wait for the distributor to package the driver for YaST - they can do it themselves, retaining more control over how things work.
This is only a new process for Novell to deal with vendors to make kernel upgrades more seamless to customers. I don't think this is going to cause all the vendors to release binary only drivers, but for the ones who do, SUSE will now work better with kernel updates. Personally, every system I use has an nvidia card in it and a marvell sata controller which only has a binary driver, about 75 systems btw... So, what kernel am I running? Oh, the stock one that came with red hat el 4, have there been security updates? YES, have I updated NO! because that is 75 systems I have to boot into text mode, rebuild the Nvidia drivers, rebuild the sata drivers, and reboot back to X windows... and that's if everything just works... I've had it not work before. Then of course you have to wait at least 2-3 weeks after red hat releases a new kernel before nvidia publishes the new version of the driver, and all in all its just a huge headache.
Binary only drivers are here to stay folks, we aren't going to abolish them, and as long as Linus is in charge of the kernel we aren't going to get a stable ABI, so, kernel update means recompile all your drivers... Any way to ease this burden is a GOOD THING because it encourages people to update their kernels. upgrading a kernel right now on any somewhat complex system, or anything that might not be 100% supported (IE wifi, some network cards, some storage devices and video cards) means a huge headache every single time a new kernel is released (by the major vendors at least 6 times a year). I estimate that if I were to keep my system updated it would take an additional 6-700 man hours per year, that is 30,000-35,000 dollars at $50/hour (which is low), you have to figure 1+ hour per system 75 systems, 6 times a year...