Should Linux Use Proprietary Drivers?

Richard Gray writes "Should Linux accept proprietary video/graphics drivers from likes of Nvidia and ATI ? The GPL written by FSF says that the license prohibits proprietary drivers. From the article: 'To write open-source graphics drivers without help from Nvidia or ATI is tough. Efforts to reverse-engineer open-source equivalents often are months behind and produce only 'rudimentary' drivers, said Michael Larabel, founder of a high-end Linux hardware site Phoronix ... Torvalds has argued that some proprietary modules should be permissible because they're not derived from the Linux kernel, but were originally designed to work with other operating systems.' The FSF however, sharply disagrees. 'If the kernel were pure GPL in its license terms...you couldn't link proprietary video drivers into it, whether dynamically or statically.' Where do you fall on this issue?"

Comments

Come on

[liliafan]

Obviously it would be nice if nvidia and ATI would open their drivers, the opensource community would benefit hugely from such a move, I also think the chip makers would benefit from it in terms of code improvements and fresh ideas....I don't see it happening anytime soon though, there has been calls in the past for drivers to be opened and it hasn't happened yet.

As for this statement:

For Nvidia, intellectual property is a secondary issue. "It's so hard to write a graphics driver that open-sourcing it would not help," said Andrew Fear, Nvidia's software product manager. In addition, customers aren't asking for open-source drivers, he said.

Firstly that is a very arrogant approach, some of the best developers in the world work on open source stuff, saying it is to hard is just stupid. As for customers not asking for open-source drivers, all I can say is huh? There have been dozens of calls over the years for drivers to be open sourced!

Regardless so long as the drivers are proprietary, I will continue to load proprietary drivers into my kernel, the FSF has a fairly narrow minded view here, yes it would be great if the drivers were open, but they aren't, and I am not going to restrict my system capablities just because the FSF doesn't approve.

Re:Come on

[Ravenscall]

There have been dozens of calls over the years for drivers to be open sourced!

And they ship millions of units per year. So while every few years a few thousand people may clamor for them to change thier business models and practices (which is expensive to thier eyes), millions more happily use thier products without a problem.

What do you think thier course of action would be here? They could lose every Linux customer they have, and it would probably not adversely affect thier bottom line too much.

Re:Come on

[Halo1]

And now with proper formatting:

Previously, they used other arguments:

From: Jon Smirl
Date: Mon, 25 Oct 2004 23:55:58 -0400

After talking to representatives of both companies, it seems that the
patent system has completely perverted the IP situation between them.
But are staying secret because of fear of being sued by the other for
infringement. This is exactly the opposite of what full disclosure of
patents was supposed to achieve.

I wish they could just get together and agree not to sue each other
over stupid things like register designs and programming models. The
designs are horrible on both cards due to accumulation of historical
cruft. Save the lawsuits for the core of the engines if you really
have to sue each other.

--
Jon Smirl

Re:Come on

[Bitsy Boffin]

You are very naieve. For Nvidia to open source thier code would cost them a significant amount of time, money and quite possibly customers if they didn't do it right. Just off the top of my head...

• Paying an army of lawyers to ensure that they CAN release in the first place. I'd bet that they don't have clean rights to distribute the source to everything in thier code, bet they licence some stuff.
  
• Paying more lawyers and consultants to work out the best licence, or more probably write thier own.
  
• Paying thier developers to clean up the code base before release, package it, setup version control access for the public.
  
• Paying thier developers while they now unquestionably spend time liasing with the new open source developers.
  
• Paying thier support staff when people using modified drivers ring up because stuff isn't working.
  
• ...
  

There IS a cost for companies to release closed source code to the open source world, it's significant, and in terms of support it can be ongoing (and if they put thier foot down and refuse to support modified code then they look bad to thier customers who don't know any better).

Re:Come on

[NutscrapeSucks]

So, what are the video card's products? Are they the hardware cards or the drivers?

A huge chunk of it is drivers. Frequently you will see new driver releases that massively improve performance in certain games without diminishing visual quality. That's all "proprietary" software R&D that no sane company is going to publish for their competitiors. And then you have "professional" cards where literally the only difference is drivers certification.

Anyway, there's a giant difference in video drivers and (say) ethernet drivers in terms of the importance of driver R&D.

Why not?

[tomstdenis]

Linux should be *open* to using either. If not than it's not really a "open" tool.

The real question is: Should we buy hardware with closed source drivers.

Tom

As others have pointed out...

[agraupe]

Yeah, it's great to be an idealist, but there are some of us who want usable 3D. I fall squarely in the latter category, and I will continue to load proprietary modules into my kernel.

Any move by the FSF to prohibit this will only drive people away from Linux, since it's not likely that NVidia and ATI will ever open their drivers completely. Free Software is great for some things, but occasionally the FSF has to recognize that some proprietary elements are unavoidable.

Open

[Moby Cock]

If a Linux Distro is really open, should the user not have the freedom to choose if he wants to use open-source drivers or proprietary drivers. Being slavish to the 'open-source only' rule is in fact counter to the spirit of it all.

The kernel should offer API's, no more and no less

[scsirob]

The Linux kernel offers API's and services that allow proprietary applications to run. If you look at a video driver as an "application to display information" then I see no reason why a proprietary driver couldn't be used with the Linux kernel. Just stick to a well defined set of API's and this discussion becomes a non-issue.

Re:Sometimes

[Billosaur]

Useability beats ideology.

There you have it. If Linux systems ever want to develop greater market penetration and actually challenge the dominance of Windows, they need to to be able to handle all the same things, including video. I say, use the proprietary drivers until approrpiate ones can be reverse engineered, then dump them for the open source versions. If more and more people begin to use Linux systems, eventually the graphics systems manufacturers are going to have to cave to market forces and support the open source system.

Re:Wrong way around

[jdcook]

"It's like AMD or Intel selling an OS. And saying 'you must use this OS with this processor'. That trick didn't fan out to well for IBM (System/360 anyone?) and wouldn't work for x86 processors either."

Yeah, nobody, not AMD, not Intel, NOBODY would want to repeat the s/360 debacle. Domintaing an industry for decades, tens of billions in sales. Really. Who wants that?

Re:If you're going to be picky, hardware's not ope

[jonwil]

I dont want to know how it works.
I just want to know how to talk to it properly so I can make it do what it is supposed to do (and push it to its full potential).
My microsoft optical mouse might have code in a little embedded processor inside it (I dont know) but regardless of how it works, what matters is that it talks over USB and it talks using a known documented protocol (so any operating system is able to use it).
My Intel Pentium IV 3.4GHz HT CPU does contain microcode that I dont have any source code for. But, it doesnt matter since the documentation of how to talk to it (the x86 instruction set) is open. (I dont know if the physical specs of how to talk to it and how to build a motherboard for it are open though)
Its the same with graphics cards. We dont want or need the origonal design files for the custom ASICs used on the cards. Or the complete schematics for the cards. All we need is details of how to talk to the card and how to get it to draw stuff on the screen. (which these days means full hardware accellerated 3D being powered by OpenGL) If a manufacturer can provide a graphics card where the hardware interface is open and which supports all the things you need these days for games like Doom III, Unreal Tournament and Neverwinter Nights (like pixel and vertex shaders), I for one am prepared to put my money where my mouth is and support them.

Snappy Answers to Stupid Questions

[npsimons]

Q: Should [GNU/]Linux Use Proprietary Drivers?

A: No.

A little more seriously, let me just repost part of a comment that really illustrates the veracity of this answer:

And really, I don't know when you started to use [GNU/]Linux, but when I
started (pre-1.0) we didn't have video drivers. We wrote them ourselves.
We chose the freedom of [GNU/]Linux over the convenience of binary-only
platforms with working drivers. It shames me that so many of the current
generation of [GNU/]Linux users don't understand what the world before
[GNU/]Linux was like. It was hell. Closed source binary-only drivers
everywhere. Buggy code that you couldn't fix. [GNU/]Linux changed all
that. Finally we have source and freedom and rights. Finally there's
something to be proud of; an entirely open source operating system built
through the sweat and tears of 1000s of volunteers. And you would
sacrifice all that for slightly faster 3D graphics? I can't comprehend
your state of mind. Your priorities are completely foreign to me.

(seen on slashdot, not said by me)

GPL over the users

[Enrique1218]

I find this fanaticism in the open source community is what's crippling Linux. OMG, some are actually considering using code in the kernel to block proprietary drivers. Imagine the problems that is going to cause for the end user. That's insane, but that is the mentality in the open source community that puts the GPL over the user. The gpl purpose is to foster cooperation not to force it. If an entity believe its needs to protect its IP, then why does that preclude their software from operating with GPL software. Majority of users (99%) want something that just works. They don't care about proprietary, open source, or philosophy. They don't have a CS degree nor care to get one. They don't even read the EULA. They just want the function which coincidentally is the purpose of making software. The end is function! The end is the user! GPL is just a means to get there but it is not the only way.

Re:Sometimes

[Just Some Guy]

Useability beats ideology.

RMS eventually founded the FSF because he couldn't get the source code to a broken printer driver. Learn your history or be doomed to repeat it.