Slashdot Mirror


Kernel Builders Appeal For Open Source Drivers

snydeq writes "The Linux kernel development community has released a statement emphasizing the need for open source drivers. The statement, signed by 135 developers, is aimed at preventing future vendors from following the closed source path. One holdout cited is Nvidia. The Linux Foundation has also released a statement in support: 'The Linux Foundation recommends that hardware manufacturers provide open source kernel modules. The open source nature of Linux is intrinsic to its success. We encourage manufacturers to work with the kernel community to provide open source kernel modules in order to enable their users and themselves to take advantage of the considerable benefits that Linux makes possible.'"

34 of 336 comments (clear)

  1. Re:Tell that to Lexmark by NoobixCube · · Score: 2, Insightful

    Same here. My printer was a Lexmark, before I replaced it after moving to Ubuntu. It was a fine printer, when I was using Windows, but hardly enough to govern my choice of OS.

    --
    Admit it. You post strawman arguments as AC so you get modded Insightful for refuting them, rather than Troll
  2. what is the use of this? by at_slashdot · · Score: 4, Insightful

    Does begging really work? I mean asking people doesn't usually solve anything, you need to either show them a carrot and/or a stick... not sure if Linux has enough of either (yet)

    --
    "It is our choices, Harry, that show what we truly are, far more than our abilities." -- Prof. Dumbledore
  3. Re:Drivers, yes, but let's not kill the applicatio by mazarin5 · · Score: 3, Insightful

    Be that as it may, this is an appropriate place for the kernel developers to focus their attention.

    --
    Fnord.
  4. Re:Drivers, yes, but let's not kill the applicatio by alxtoth · · Score: 3, Insightful

    You've got it backwords regarding drivers: hardware vendors sell hardware, and "give away" the drivers so that people can actually use said products. As there will be more Linux users, so there will be incentive for providing drivers. As in Linux there are so many distros, it makes no sense to offer "closed source" drivers. And there are other operating systems which are not Linux, for example the BSD family

    Same goes for software: if there will be enough demand, there will be more software for Linux. Even closed source. For example there is Intuit for Mac OS.

    But instead of pushing water uphill with those software companies, why don't you look for software that does equivalent things on Linux (open source, or proprietary) ?

    --
    http://revj.sourceforge.net
  5. open source drivers and gaming 4 linux by Icy_Infinity · · Score: 5, Insightful

    There is only one thing holding back Linux from being used more wide-spread.

    Gamers, the Linux community just doesn't care for them. But that is wrong, just wrong. Gamers are the reason why computers are the way they are nowadays, without good games to play on our electronic devices I guarantee that computers wouldn't be a big as they are today, and that's something that Linux has always failed to do bring us top-shelf gaming

    having open source graphic drivers would be nice but i don't think that is the true problem for games on Linux

    there true enemy that needs to be defeated before Linux even has a chance at becoming mainstream:

    Games for Windows

    The fug-tards at Microsoft pay off every last PC game maker to put their dirty label on everything even the damn game reviews have that garbage label on it for god sakes.

    They do it because they know no one else stands a chance in the PC gaming market. Stop them please stop Microsoft and there proprietary-ness. Defeat games for windows and Linux will be main stream, because freedom and openness shouldn't be a standard just for big iron. Theirs little guys like me that would love nothing other than to give windows the old heave-ho but can't because where all locked down in a homeostasis environment.

    Also running in an emulated environment just doesn't cut it - it could be possible but WINE just can't do it for some games. Normally the games that don't run are the most proprietary ones sadly but there's still room for them in the sphere that is Linux. Help make a home for gamers where there not locked and bogged down by corporate greed. crack Games for Windows and please dear god make "Games for Linux" a reality

    1. Re:open source drivers and gaming 4 linux by mrsteveman1 · · Score: 2, Insightful

      DirectX is the real problem there i suppose.

    2. Re:open source drivers and gaming 4 linux by Yvanhoe · · Score: 2, Insightful

      Gamers, the Linux community just doesn't care for them. Why do you think kernel developers want nvidia drivers to open ?
      The OSS community cares for gamers but can't care too much for commercial games. Look around a bit, you'll find many OSS games. Strategy, FPS, action. There are also more and more commercial games that come with a linux version.

      The niche of the "latest cutting-edge FPS with extra glitter and shaders 15.6 with 2X PhysX simulation" is today on windows, that's right. That's in part because graphical drivers sucks on linux. Open them, let them improve, and see what happens when OSS drivers become more robust than windows drivers.
      I long for that day. All gamers are not coders but a lot of them are power users who configure their OS, mod their PCs. Linux is just made for their mindset.
      --
      The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
    3. Re:open source drivers and gaming 4 linux by daffmeister · · Score: 3, Insightful

      In what way doesn't the linux community care for gamers? What features of the kernel or graphics systems do you believe are missing?

      The problem is with the game developers, not the linux community.

      And that's a simple problem of market share. As long as Windows is by far the dominant OS game developers will focus their efforts on that.

  6. Where's Linus? by Ewasx · · Score: 2, Insightful


    Did anyone else notice that Linus himself is not on that list? Does this mean that he doesn't mind closed source modules?

  7. Open Technical Documentation by Anonymous Coward · · Score: 5, Insightful

    Shipping drivers for only windows is bad, but shipping drivers for only windows and linux is (magically!!) good???

    Fight for open specifications. That will enable any competent driver-writer to write drivers and all OSs can compete on fair grounds. By technical documentation, I don't mean "the guide to programming the Emc2x86" kind of stuff. There should be "The exhaustive reference to programming the Emc2x86" kind of stuff. There should the following guarantees associated with the documentation, only then the hardware can be called as "openly documented hardware":

    1. For a sufficiently competent programmer, the documentation supplied is enough to achieve 100% feature parity with the proprietary drivers.

    2. The documentation supplied must contain as a subset, all interfacial knowledge known to the writers of the proprietary drivers.

    1. Re:Open Technical Documentation by Anonymous Coward · · Score: 5, Insightful

      > 1. For a sufficiently competent programmer, the documentation supplied is enough to achieve 100% feature parity with the proprietary drivers.

      No it doesn't. Your assuming time doesn't matter and that the hardware follows the documentation.

      Time does matter because if a person releases a product to market without a pre-existing Linux driver then Linux people can't use it until developers purchase it and begin hacking on it.

      Hardware has bugs, like software. Also hardware deviates from specifications. For example with both ATI and Intel video hardware they are subject to variations that individual motherboard and video card manufacturers create.

      Without assistance from the people who actually worked on developing the hardware then your going to end up doing a lot of trial and error to figure out what is wrong.

      > 2. The documentation supplied must contain as a subset, all interfacial knowledge known to the writers of the proprietary drivers.

      Your assuming that such documentation exists or that it's even possible for that manufacturer to create, and that they can afford to create such documentation. Not everybody has all the time and money in the world to create extensive documentation for their products.

      Not everybody has the budget and experience that Intel and AMD have...

      The reality of the situation that is unless you have the attention of OEMs and have people that are willing to work on the inside with the manufacturers to work on documentation and drivers then isn't going to get the same level of attention that even Linux gets.

      Because of the realities surrounding developing hardware having working, open source, Linux drivers is the best documentation that your going to get, and in fact are often superior.

  8. Re:Drivers, yes, but let's not kill the applicatio by dotancohen · · Score: 2, Insightful

    But instead of pushing water uphill with those software companies, why don't you look for software that does equivalent things on Linux (open source, or proprietary)? There is currently no Solidworks-compatible program (open- or closed- source) available. The problem is not that I need to work alone, the problem is that I need to interoperate with other engineers.
    --
    It is dangerous to be right when the government is wrong.
  9. Re:Tell that to Lexmark by dotancohen · · Score: 4, Insightful

    Who cares? Why didn't she stay on Windows. She should have checked her compatibility status beforehand.

    For most people, applications dictate OS dictate hardware. I prefer KDE, so I run Linux. I run Linux, so I buy an HP printer.
    --
    It is dangerous to be right when the government is wrong.
  10. Value of NVidias drivers, from another post. by thesupraman · · Score: 5, Insightful

    I posted this over at RWT a month or so ago..

    >Here is really the main point, which you're brushing
    >aside -- this makes the hardware worth more, because
    >you're making it potentially more usable for end users.
    >Maybe not all end-users, but certainly some. I don't
    >understand why you say it's a "very different kettle of
    >fish" ? Different than releasing the specs? If anything
    >it means fixes will happen faster.

    I am not brushing anything aside, I am saying that a lot of people for a long time have ranted about opensource drivers for advanced video cards - and as yet I have seen no-one discuss it at a level that actually addresses what would be involved.

    My 'very different kettle of fish' above is the vendors actually releasing full-stack sourcecode, versus just hardware specs.

    My position on the hardware specs (and I am not claiming proof for this, it is only my position) is that it is next to useless for high-performance users. We may well see competent 2d opensource drivers, and 3d ones that can limp along - however graphics hardware has moved a LONG way from there.

    I would *love* to see a fully opensource stack with high performance for opengl, however is it practical?

    In your reply (sorry, I clipped it back a bit for brevity) you mentioned harddrive makers doing sector remapping - that is probably a whole few pages of code in their controllers. For a full modern opengl stack we are probably talking in the millions of lines region - we are talking of something with a scope not unlike the linux kernel itself, or at least a good proportion of it.
    This is NOT similar to any other type of driver that I can think of - it is an almost unique case.

    Just looking at opengl, the cards driver needs to be able to handle multiple simultaneous execution of overlapped and scheduled code, all in realtime, on in the region of 100-300 semi-linked vector cpus, all without cross-interference, while also maintain multiple streams of data at GB rates in and out of the card, and all while following a VERY explicit and highly complex set of rules governing the results.

    Put another way, these devices are bleeding edge modern realtime computers, on a card - and their 'drivers' are really realtime OSs, although highly specialised.

    Intel, in its infinite wisdom, as about to try and take that to the next level - making such cards x86ish, with an eye I suspect to reducing the complexity of software entry, after having failed miserably to write working drivers for their existing (965, g35, g45 so far) hardware.

    All I say is lets cut these guys some slack - the capability of the hardware/software combination of a 9600gt, for around $150, is simply astounding. Should they expect 'help' from kernel developers, etc? of course not. Should they be punished? I say no.

    Anyhow, I know that is bordering on preaching, and of course very opinionated - however I do like to see things treated with an even hand, and I have not always seen that happen with the issue of opensource 3d graphics drivers.

  11. Re:No Linus? by pembo13 · · Score: 4, Insightful

    I suspect Linus specifically likes to take no (public) stand on these things, and I don't blame him. People use his name for so many different things as it is, even though, interview after interview he states that he is just an engineer and doesn't really care. I myself care, but that's besides the point.

    --
    "Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
  12. The carrot & stick already exist. by Whiney+Mac+Fanboy · · Score: 3, Insightful

    This petition is just a gentle reminder that the carrot (utilizing OSS community development process) & stick (customers switching vendors) already exist. (from TLA):

    Vendors that provide closed-source kernel modules force their customers to give up key Linux advantages or choose new vendors. Therefore, in order to take full advantage of the cost savings and shared support benefits open source has to offer, we urge vendors to adopt a policy of supporting their customers on Linux with open-source kernel code.
    --
    There are shills on slashdot. Apparently, I'm one of them.
  13. Re:Tell that to Lexmark by profplump · · Score: 4, Insightful

    Or you could buy a printer that supports PostScript. I know it's an evil Adobe abomination, but it's really easy to print to, commonly supported in both network and local drivers, and has a standard printer-definition format to allow selection of hardware-specific options without the need for a hardware-specific driver.

    Honestly, in a day and age when even non-tech families have a home network it seems silly to use USB connections and hardware-specific drivers for printers -- just spend the extra $50 and get a printer that can operate with direct interaction from a host CPU.

  14. about 2 years behind OpenBSD by Anonymous Coward · · Score: 1, Insightful

    Release 3.9 had the "blob" theme.

    Crikey! They're catching up!

  15. Re:Tell that to Lexmark by ettlz · · Score: 3, Insightful

    PostScript's not an abomination, just an anachronism. I'd like to see more printers supporting PDF "natively".

  16. Such arrogance... by JazzManDRP · · Score: 4, Insightful
    Hardware vendors like nVidia run a business. They run a business to make money. If nVidia didn't make financially-successful decisions, they wouldn't exist to be producing the graphics cards in the first place. That's all there is to it.

    If there was money in Linux they'd be right there, open-source drivers and all, but there isn't. This is a fact that open-source developers never seem to understand. You can cheerfully dedicate half your life to creating this wonderful utopian software, but you can't force your ideals on someone else - especially on a company whose aims do not coincide with yours. Make it a financially beneficial proposition, and nVidia will spend the time and money on creating those drivers - but I doubt it's anything near that.

    What responsibility do nVidia have towards the Linux desktop? The same as they have towards Windows: absolutely none. But they support Windows because 90% of desktops with their graphics cards installed run Windows.

    And yes, Intel and ATI have managed to push out open source drivers - that's up to them, but I don't imagine they make profit from it. Yes, it's a real pain in the arse to work with binary drivers. Yes, if nVidia were to release open-source drivers the world would be a happier place. But to act like Linux users have some *right* to these drivers is childish and arrogant.

    What Linux users have the right to do is buy a different graphics card.

    1. Re:Such arrogance... by chrb · · Score: 4, Insightful

      It might be arrogance to *force* nVidia to support Linux, or to insist that Linux users have the *right* to open source drivers. However, that isn't what the authors of this statement are doing - they aren't storming nVidia HQ in an armed revolution, but merely pointing out that binary drivers are a PITA, and asked companies nicely to consider releasing open source drivers in the future. And that's fine.

  17. Linux Users vs hardcore Windows gamers? by Marcion · · Score: 2, Insightful

    Nvidia is a company that exists to make money.The question that Nvidia needs to think about is whether the number of Linux users (including those on the EEEPC, high-end phones and more specialised embedded devices) have outgrown the number of hardcore Windows PC gamers?

    Whatever you think about the answer to the question, I'm sure you will agree that going forwards, the growth in embedded devices will certainly increase faster than Windows gaming.

    When a company makes an embedded device, time to market is often really critical, so of course it chooses whatever hardware causes the the least fuss. Nvidia might find that Intel and ATI will increasingly dominate this space.

    If Nvidia wants a share of the open source market in five years time, then it needs to start planning for an open source driver now, e.g. not putting any more third party proprietary code in its driver.

  18. Re:No example of open source driver that doesn't s by crimperman · · Score: 3, Insightful

    Is there an example of an open source driver that doesn't suck? Kernel driver? I'm sure there is but I'm not always sure which ones have been written by the manufacturer.
    Fro non-kernel drivers HPLIP is a pretty good example of a company opening up it's driver base properly and with some success http://hplip.sourceforge.net/. I still wish they'd notify of Linux support on the boxes though.
  19. Re:Tell that to Lexmark by inasity_rules · · Score: 3, Insightful

    Until the new owner fires up his ubuntu PC...

    --
    I have determined that my sig is indeterminate.
  20. Re:Tell that to Lexmark by searlea · · Score: 5, Insightful

    The manufacturer might want repeat business...

    They're not selling suicide bombs.

  21. Re:Tell that to Lexmark by dangitman · · Score: 3, Insightful

    The sale was already made. The manufacturer has nothing more to gain.

    Nonsense. Consumer-level printers get replaced very frequently. They had future sales to gain (or lose).

    Likewise, they have gained poor word-of-mouth, or lost positive word-of-mouth referrals. And it's pretty widely acknowledged in business that word-of-mouth is the most powerful means of advertising, and a real driver of sales.

    --
    ... and then they built the supercollider.
  22. Re:I don't understand nVidia by mpe · · Score: 4, Insightful

    There are three reasons why nVidia claims they can't open source their drivers:

    This isn't what they are being asked for. They are being asked for specifications, there are people perfectly prepared to write drivers.

    1) They incorporate third party proprietary code. This is almost certainly the case. I'm betting that some or maybe even all of it isn't secret, but it is still licensed none the less. That means they'd have to either change the driver to leave those features out and/or rewrite the code themselves which could involve some expensive clean room/dirty room techniques. Remember that they can't play the Xvid game of "Well we don't distribute it compiled so don't need to pay a license." Ya that won't won't work for a company who is providing the code for the clear purpose of making their cards work. They'd get sued (and they'd lose).

    None of it's secret since they make all sorts of binaries available. Indeed having multiple binaries for the same piece of hardware may make reverse engineering easier.

  23. Re:Is this a technical or religious issue? by ledow · · Score: 5, Insightful

    "Is it technically impossible to provide for closed-source drivers in Linux?"

    No. But it provides an ENORMOUS technical and legal hurdle (nobody's even sure yet if binary kernel modules are legal in most countries, although the *intention* is that they are). Supporting closed-source means, at some point, freezing interfaces, which means supporting every version of every interface created indefinitely. That's an AWFUL lot of work that would have to be done by precisely the people who don't want to do it and have enough to do already. You are doubling their workload by this simple request.

    "Many people simply want Linux as an alternative to Windows, and a good alternative it is already."

    Correct. Unfortunately, that's up to THEM to do something about, because that's not why Linux existed, exists or continues to exist. Linux is an OS, so in that sense it's an alternative. But it's not Windows. It won't ever BE Windows. It's just an OS. Who here complains to Apple because the Mac doesn't work with their Windows-only printer? Very, very few people.

    "But insisting on open-source drivers will make the situation worse, not better in the long run: more and more special-purpose hardware is getting attached to the computer; mobile devices, chipcard readers, entertainment devices, GPS devices ... the list goes on and on."

    Yep. And none of it we know how to drive, how to support, how to operate, how to upgrade, how to interface or how to port to other machines (like, I don't know, all those other alternative OS's that don't have compatibility layers). It's all just "black boxes" that sometimes (often, actually) the manufacturer's don't even know how they work. Just throwing in drivers "because they work now" isn't any good in the future, and certainly isn't any better than saying "Well, you'll have to run DOS if you want X to work". What's the difference between that and "You have to use Linux kernel 2.5.12 and our binary-only driver v 1.4.1"? The latter is available now for all current closed-source Linux drivers too... I can run my ATI card on Linux 2.6.1 with an old ATI driver just dandy. I could never upgrade that machine, though. They stopped supporting my card and they made the last compatible release for kernel 2.6.15.

    Closed source drivers work now and break (for certain) in the future. Open source drivers have trouble working now (although that's not certain) but work the same or better in the future. With company co-operation, that can turn into "works before the product is out, works until there aren't any products that use the same driver in the general marketplace". Look at some of the 10Gig cards, or NX-capable processsors - there were drivers in Linux for them before anyone had even put their products out on the market.

    "It is simply naive to think that we will get open-source drivers for all of these."

    But experience shows you wrong - every single network card vendor on the planet had the same idea of not supporting their cards. Now almost every single network card, from token ring to wireless-N, on the planet is supported, and usually supported under Linux first. The only hardware that *doesn't* work is stuff that people don't care enough about to reverse-engineer or to build a compatibility layer for, or where there are legal issues. For those same hardware, even the closed-source drivers are now usually, or will be soon. And to be honest, most of that stuff won't work in Vista, or ME, or 98, or DOS, or Mac or anything else. And in a few years time, it'll break BEYOND REPAIR even in Windows either by a Window Service Pack or the next version of Windows.

    Intel have Open-Source chipsets. AMD/ATI are open-sourcing. RaLink release a set of GPL drivers for their wireless cards. *Virtually* every piece of hardware in the world (as a percentage of overall items sold, e.g. the "production-run-of-ten" cheap knock-off PCI cards that don't have OS drivers don't really count against the 10 million sound cards sold which run

  24. Re:Tell that to Lexmark by dave420 · · Score: 2, Insightful

    Unless they start getting those emails in sufficient quantity, they'll just be replied with the usual boilerplate response. They won't think it's worth their time to make drivers for only a "few" people.

  25. Why not standardise the hardware? by Bert64 · · Score: 5, Insightful

    Why does hardware need to be so non standard and proprietary requiring its own drivers?

    Take for example USB1, all USB controllers from many different manufacturers work with generic UHCI or OHCI drivers.

    USB2 is even better, since all controllers support EHCI.

    SATA potentially has AHCI, tho not all controllers support it.

    Most CPUs have the x86 instruction set.

    Video cards have VGA/SVGA/VESA, tho these specs are obviously far too old to be useful today.

    Sound cards have soundblaster compatibility, and more recently AC97.

    Proper modems have the Hayes command set, not counting some software modems.

    Printers have postscript, tho typically only higher end printers support it.

    If you have standards in hardware then the issue of drivers goes away... Your OS can provide drivers for the standard hardware, and thus not have third party driver code in the kernel... This would cure the Linux driver problem, and cure a majority of Windows crashes.

    --
    http://spamdecoy.net - free throwaway anonymous email - avoid spam!
  26. Re:Is this a technical or religious issue? by ledow · · Score: 4, Insightful

    "And that means connecting a huge amount of strange hardware."

    I would differ on this point. Most hardware works. Most of the hardware that doesn't is niche, old, obscure or rare. This doesn't mean we should be supporting it all, because most people who own it will KNOW that - every OS they try with have limited support for it. I own a vast array of hardware collected over the last decade from schools - there are esoteric, unusual, low-production, specialist, ancient, homebrew, brand-new and just plain weird hardware in my boxes. The vast majority of PC-compatible stuff works on Linux. The only examples I've personally found that DON'T work at all are:

    - A £2 USB IrDA adaptor (the other ten just work). It's not detected and looking up the usb.ids list shows me that almost nobody else has one the same model - I suspect it was recalled or had a very limited production run.
    - An ISA "video backer" card (uses VHS tape for backup through component video - 4Gb on a 180min tape!), actually, there is software for it but I couldn't get it to work (I wasn't trying hard). I reckon it's just too old for the kernel I was trying on. But then, I had to hunt around to find a computer with an ISA card - I found several dozen but most of them were too old to boot up or couldn't run even an ancient version of Linux/Windows/DOS.
    - A handful of Winmodems that work with the proprietry "Linuxant" drivers if I pay for it. About a one in five ratio between working modems and non-working Winmodems out of the dozens I store. That's pretty damn good but still the worst ratio for any hardware I know.
    - A parallel port scanner that I can't even connect to anything past Windows 95 without it crashing the machine dead. It gets conflicts if you have a soundcard installed at all, it crashes all the time, it doesn't allow ANYTHING to use its passthrough parallel port.

    I estimate less than 1% of the hardware fails to work entirely, and less than 2% will load if you can use a binary driver. The rest is just pure hardware that just works. And this is in schools, where cheap crap gets priority and teachers buy things because a salesman says so. Examples of things that work include:

    - PCI S3Virge card with FOUR S3 chips and four D-Sub outputs each (possibly the largest interface card you've ever seen in your life), for multi-displays back when SLI hadn't even been heard of.
    - Electronic microscopes designed for Windows only.
    - Various "control" hardware, including Lego, robots, the original floor turtles, hardware originally made to work with BBC Micro D->A convertors.
    - Fingerprint scanners for library control systems (we don't use them for legal reasons).
    - Card readers/writers
    - Scanners that plug direct into ISA sockets (literally - the interface card is little more than a voltage-regulator with a plug on the back of the computer to plug the scanner in)
    - Interface cables for Psion organisers that have been "customised" for educational use.

    And most of that's before you get near the stuff made in the era when Open Source started to take hold. The Wiimote, for instance, was supported very, very quickly without any help from Nintendo. The OS drivers mean it works on all platforms now. It's being used in everything from military research to "over-the-net" hospital operations. All without Nintendo's help. But *with* Nintendo's help, it could be the de-facto controller for just about anything.

    "So yes, having open source drivers for everything would be great. However I think that we can agree that this wont happen"

    I don't think we *can* agree here. I don't see it happening *any time soon* and it will never be for *everything* but the vast majority of hardware that's out there already has OS drivers, whether by the manufacturer or third-parties.

    "I think you greatly exaggerate the issue of kernel versions."

    I honestly don't. Taking, for instance, the drivers for my ATI/nVidia cards (the closed-source binary in an open source wrapper) - every few mo

  27. Re:I don't understand nVidia by mrchaotica · · Score: 2, Insightful

    So release a GPL driver that doesn't optimize! I don't even care if my framerate is a little low compared to Windows; I just want it to at least work!

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  28. Re:Tell that to Lexmark by LWATCDR · · Score: 2, Insightful

    Why in the Kernel.
    That is what drives me nuts. Why do we have to have stinking web cam, printer and goodness knows what else drivers in the Kernel! Yes I know Linux is a monolithic kernel and that is why but good grief that just seems like a bad idea.
    I didn't think that printers did need to be in the Kernel I thought they used a CUPS driver but I will admit that I don't mess with printers on Linux much.
    Wouldn't it be better to move some drivers out of the kernel? I mean should a bad web cam or printer driver really take down a system?
    I really think that Linux needs to offer a stable binary driver interface and offer a microkernal like interface for some less critical drivers.

    --
    See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
  29. Re:I don't understand nVidia by bradkittenbrink · · Score: 2, Insightful

    Fair. From what I've heard though, ATI/AMD isn't releasing their optimized drivers. They're releasing open source reference drivers. There's no reason nVidia can't do that.