NVIDIA's Andy Ritger On Linux Drivers

tykev writes "The Director of Unix Software at NVIDIA talks about Linux drivers, planned features, development cycle, and the open source Nouveau driver. (The interview is in English but all the comments are in Czech.) Quoting: 'NVIDIA's stance is to neither help nor hinder Nouveau. We are committed to supporting Linux through a) an open source 2d "nv" X driver which NVIDIA engineers actively maintain and improve, and b) our fully featured proprietary Linux driver which leverages common code with the other platforms that NVIDIA supports.'"

Comments

Nouveau

[nxsty]

NVIDIA's stance is to neither help nor hinder Nouveau. We are committed to supporting Linux through a) an open source 2d "nv" X driver which NVIDIA engineers actively maintain and improve, and b) our fully featured proprietary Linux driver which leverages common code with the other platforms that NVIDIA supports.

But what will they do when nouveau is complete, and replaces the nv driver? Will they stop commiting to xorg?

Re:Nouveau

[babbling]

Nouveau probably won't ever be "complete" since there's always new cards to add support for and that sort of thing. If Nouveau gets good enough and is the default driver they will probably start contributing to it. They would save money on driver development, and continuing their proprietary driver would be a bit pointless since everyone would be using Nouveau.

Until Nouveau gets good, I imagine they'll keep pushing the proprietary driver, though.

Re:Nouveau

[Andy Dodd]

Yeah. I interpret their "help but not hinder" comment to mean:

"Some of our license agreements prevent us from contributing 3D support to open source drivers, we like Nouveau but can't legally contribute to it."

One wonders what happens if Nouveau becomes the official xorg driver. Perhaps NV will be able to legally contribute to the 2D aspects of the driver. The binary drivers will likely continue to exist as long as they are encumbered by technologies licensed from other vendors which NV has no direct control over (such as S3TC support).

Re:Nouveau

[b1ufox]

The problems as i look at it is loosely like this. Nouveau being a reverse engineered driver misses to harness complex Nvidia specific GPU features.Yes, mod me down if you feel like but that is the truth, a reverse engineered software for a complex GPU is not simple.And now please don't give me example of Samba and et all, i know it. The way hardware evolves in today's hardware industry Nouveau will find it extremely difficult to sustain the pace to match it.

Moreover reverse engineering being a difficult task, it will take time.

Here is the alternative IMHO, AMD open sources ATI drivers. ATI 3D driver gets into mainline kernel. Nvidia will *have* to open source their driver, which can be possibly merged with the nouveau project to make sure it is constantly up to date with the Nvidia's cutting edge technology advances.

But thats just optimistic me. :-)

Re:Nouveau

[babbling]

Do you really think Nvidia couldn't renegotiate license agreements, work around patent problems, or at least release a data sheet for their cards?

It's all a matter of how desirable it is for them.

If Nouveau became the official xorg driver and was decent enough that people wouldn't rush to replace it, Nvidia most likely find a way to contribute to it to ensure that Nvidia hardware has a good quality driver on Linux.

Re:Nouveau

[babbling]

It would be pointless for Nvidia to continue developing their proprietary driver once very few people use it because the Free Software one is "good enough" and installed by default. Nvidia doesn't directly make money off drivers, so in such a scenario it would be in their interests to just make sure the Free Software driver is as good as it can be.

What's the point of spending money developing a proprietary driver if everyone just uses the default Free Software one which works reasonably well?

Re:Nouveau

[jonwil]

I wonder if it would be possible to produce a driver that didnt use the patented features (and as such presumably didnt support that relies on the patent) but still implemented the rest of the functionality of the GPU. For example, if nvidia has licensed the S3TC patent, they could remove the S3TC code from the "open source" driver.

Or they could go half way by taking all the code that they don't own and all the code that relies on 3rd party patents where the patent holder has forbidden them from releasing source and put those into the "binary blobs" (like they have now) and make the rest of the code (which they own the copyright to and which is not covered by whatever 3rd party patents they have licensed) available (in much the same way at least one vendor of WiFi cards has put only the bare minimum code that has to remain closed for FCC certification into a binary blob and made the rest of the code open source)

Re:Nouveau

[MoxFulder]

There is no way that an open-source GPU driver can ever achieve same quality (in terms of performance and compatibility at a given timeframe) as an actively developed proprietary driver. GPUs are very complex devices, and drivers make a huge difference on performance. In order to make a fast driver you really need to know how the target GPU works on a very low level.

This is the same tired, fallacious argument NVidia has been trotting out for years: "Developing GPU drivers is much too complex. Why don't you Linux kids go run along and play with your toys, and let us write the GPU drivers?"

Well, it's just wrong. I have used many reverse-engineered drivers for complex pieces of hardware, and nearly all of them work as well as or better than the original vendor's drivers. Most recently, I had the pleasure of trying out the Broadcom 43xx wireless driver, which was painstakingly reverse engineered in the face of an INCREDIBLY recalcitrant vendor that won't release a shred of documentation on their devices to open source developers, even under NDA! And, surprise, the card works better under Linux with the reverse-engineered driver than it does with the Windows driver, which seems to lose the signal quite often. The bcm43xx developer Michael Buesch has even got some evidence that certain parts of their code are implemented more efficiently and elegantly than the original driver.

Naturally, NVidia will not disclose this low level stuff about their GPUs to outsiders.

Why is this "natural"? Intel releases documentation on the low level stuff about their GPUs, Realtek goes out of its way to help the Linux community with Ethernet and wireless IC documentation, and Linksys has released the complete code for its Linux-based routers. If a business is based on continual innovation--rather than maintaining an entrenched monopoly--it is entirely possible to be successful and open at the same time.

You can compare GPU drivers to compilers. There is no way that open-source compiler (GCC) will ever produce as good code for new Intel's CPUs as Intel's own compiler (ICC) as long as ICC is actively developed.

Again, this is only true if Intel holds back some of the documentation necessary to make a good compiler. If they publish complete instruction set information, with accurate timing, cache, and pipeline data (which they have done, for the most part), then making a better compiler is "merely" a question of developer resources and talent.

I suspect that, to the extent that GCC code doesn't run quite as fast as ICC, it's because GCC has higher priorities for its code base, especially ensuring support for an incredible breadth of platforms. GCC has essentially become the reference compiler for a lot of embedded development in particular. Even companies like Broadcom that won't lift a finger to help open source out rely on GCC to build the firmware for their own devices.

Re:Nouveau

[notamisfit]

Because nv is obfusticated crap.

Re:Nouveau

[WilliamSChips]

The problem with that is that AMD is bound by the same patent crap nVidia is on a lot of their 3D features and neither one can actually open their drivers because it wouldn't be worth the patent minefield to navigate around. But if Nouveau advances far enough to supplant nv, then nVidia will probably send a few engineers to contribute to Nouveau code like they currently do with nv and forcedeth(nForce network driver for Linux)

Re:Nouveau

[jonwil]

The smaller you make the binary blobs, the easier it is for other people to clean-room reverse engineer and clone said binary blobs (as has been done for some of the WiFi cards with binary blobs)

Re:Nouveau

[ppanon]

My understanding is that GCC doesn't perform as well as ICC because ICC uses a number of patented algorithms in its optimizations which GCC cannot yet legally use. Not sure if somebody in Europe might be able to fork a version of GCC that uses those algorithms for use outside the US. The problem of course is that many of the maintainers of GCC work for Cygnus Software (now part of Redhat?) and are based in the US.

Re:Nouveau

[jdschulteis]

No open source is ever "complete", for good and for worse :) Even a dead open source project is only "temporary dead"! (whatever that means...) It just so happens that your open source project here is only MOSTLY dead. There's a big difference between mostly dead and all dead. Mostly dead is slightly alive.

Re:Nouveau

[MoxFulder]

I don't see your point. You talk about ethernet drivers which are ususally low complexity drivers and use this as an argument to support your 3d driver claims.

Full-featured 802.11g wireless drivers are pretty darn complex. I don't believe there is anything particularly "exceptional" about 3D drivers, so I see the comparison as perfectly valid. For years we've seen proprietary software makers concede that "open source can do X, but Y is too complicated." I have no reason to believe that 3D drivers are any different.

People have *talked* about developing 3D drivers for modern GPUs for *years* and go figure they don't exist or are even anywhere near existing today. Its a horizontal market and there is a lot of demand for 3D so I don't see the excuse. I'll believe it can be done when someone actually does it.

Well, the Intel GMA drivers already exist, having being released by Intel as fully open-source. And the open source community is (surprise!) working on improving them.

And the Nouveau Project seems to be making quite a lot of progress on NVidia drivers.

As far as Intel... lets see Intel sells general purpose CPUs that need to interoperate within a wide range of operating environments. Intel has to release the specs in order for this to be achivable to the mutual benefit of all parties.

NV and AMD are interested only in winning their bloody GPU war and have no interoperability requirements or constraints. Giving away their secrets/work/whatever you want to call it at this level is of no advantage to these companies and I think this is all pretty obvious. Why is this so hard for some to understand?

I don't think this is quite accurate. As long as it's only NV vs. AMD, they may not have much reason to release anything. However, this creates an opening for a third player, who will start out behind but gain a competitive advantage by releasing open-source driver.

And at this point, Intel is clearly gunning for that spot. They already have an extensive line of integrated graphics, and they'll be making discrete graphics chips soon. If Intel follows through and releases open-source drivers for these new cards, I expect that open-source developers will flock to them in droves and rapidly improve the drivers. This will put more pressure on NV and AMD.

Well, time will tell which of us is right :-)

Re:Nouveau

[the_greywolf]

Do you really think Nvidia couldn't renegotiate license agreements, work around patent problems, or at least release a data sheet for their cards?

No, I don't think NVIDIA are in the position to renegotiate a license that they don't have direct involvement in. I'll give a few examples from OpenGL extensions for why I think this way:

• ARB_occlusion_query -- HP claims the IP to this extension and licensed it to the ARB.
• ARB_fragment_program, ARB_fragment_program_shadow, ARB_vertex_program -- Microsoft claims ownership of the IP. What, precisely, they claim they own, I don't know. They're not likely to favor opening related source.
• ARB_texture_float, ARB_color_buffer_float, ARB_half_float_pixel -- SGI patent #6,650,327
• ARB_point_parameters, ARB_multisample -- "TBD," according to NVIDIA. It's probably not clear just who has the claim on it.
• EXT_texture_compression_s3tc -- S3 owns the IP on this specific compression scheme. It's the most popular and most widely-used compression format, so removing it might break a lot of games.

A number of other OpenGL extensions are NVIDIA proprietary, and most of the suits will probably hang on with their dying breath, if typical corporate behavior is any indication.

It'd be nice if they opened the driver, but half of the OpenGL ARB's members would probably sue their pants off if they tried.

Re:Nouveau

[KDR_11k]

Tell that to ATI. Their r100/200/300 cards were just about fully supported by free drivers for both 2D and 3D.

Yes but how long did it take? I know when I first used Linux with my r200 I couldn't get any 3d capable driver except the FireGL and I never really got 3d to work.

Re:Nouveau

[Andy Dodd]

Regarding the last one (S3TC) - removing it WILL break a lot of games.

Unreal Tournament's need for the last one marks the beginning of ATI providing proprietary drivers and partial specs for their cards rather than full specs. There was a huge to-do about Unreal Tournament 2003 only working on NVidia cards in Linux back when UT2K3 was released. Epic's response was basically "we use this feature, it's implemented in all Windows drivers and the NVidia 3D drivers, we cannot work around the lack of this feature in the ATI drivers."

Shortly after, the first binary ATI drivers were released, with the main difference between them and the open-source drivers being S3TC. They have diverged since then, as clearly a number of other encumbered extensions have gone mainstream after looking at your list.

black window bug

[xNstAble]

Improving our GLX_EXT_texture_from_pixmap implementation's handling of out-of-videomemory scenarios (this is the cause of the "black window bug" when running Compiz or Beryl composite managers) Good to see that this issue is still wellknown to nvidia developers, this bug has been around for a lot of months and has never been addressed yet. This is the typical problem that open sourcing the drivers would solve in a much shorter timeframe I guess..

Re:Move along, nothing to see here

[Anonymous Coward]

Still no 3D support without having to use a proprietary (closed) driver. Wake me up when that changes.

Sure thing, Mr. Rip Van Winckle!

Considering

[Z00L00K]

the fact that the "nv" driver is buggy there is a lot of room left to improve on here.

I experienced a problem with the "nv" driver on my computer with dual 7600GS cards and three displays. It wasn't possible to run all three displays at all with the "nv" driver, but the binary driver from nvidia works. The part that I'm not satisfied with is the need for an alternate driver.

I haven't tried the Nouveau driver, but somebody else may. As I see it, Nvidia should release all information needed to allow others to write suitable drivers. (should apply to all HW manufacturers).

NVIDIA driver team members use Debian?

[Karellen]

From TFA:

"Across the NVIDIA Linux Graphics Driver team, everyone has their own favorite Linux distribution as their primary desktop: Debian, [...]"

Interesting, given that Debian can't ship their driver.

Oh, I know that none of the driver team will be using a distro-bundled version of the driver anyway, but still...

What a crazy world we live in

[east coast]

The interview is in English but all the comments are in Czech

Stop the planet. I want to get off!

From now on I vow that when I code the code will be in English but the comments will be in Slovak.

Re:What a crazy world we live in

[the_arrow]

Well, it's time to switch from hungarian to slovakian notation!

Re:A question

[Whiney Mac Fanboy]

seems to me demanding that a company release their drivers in open source

I read & re-read the parent comment, but couldn't see them demanding anything. WTF are you talking about?

I mean, to the exclusion of actually using the software which could make their computer experience better.

Some people have quite pragmatic reasons for preferring open software - particularly kernel software. Driver crashes were one of the things that made windows (particularly in the late 90's / early 2000s) such a mess.

If you're making a hardware purchasing decision and want to run linux, of course you should try to buy from a company that supports FOSS.

Surely we haven't got that many mini-RMSes?

Finish the troll with a flourish. Nice work.

Re:A question

[Aladrin]

Because it works! There's a saying, 'The squeaky wheel gets the grease.' If Linux users are very vocal about how they expect companies to do business, those companies -will- feel pressured to move more towards that way of doing business.

It's the exact same reason that lobbying a congressman (without money) works. Once they hear it enough, they know it's important to the people that are most important to them: Their customers. (Or voters, as the case may be.)

When people don't tell a company how to behave, you end up with companies like Walmart. Walmart used to be about the country, the consumer, and the profit, in that order. They gave up on the whole 'made in the USA' thing quite a while back. They gave up on customer service even longer ago. They only care about the profit now. They do it by having cheap goods and cheap wages. For people who only care that the goods are cheap, it's a great store. For the rest of us it sucks.

nVidia has the choice of only catering to the mainstream Windows-based gamers, or also adding on a rabidly-loyal group of fanatics that are willing to work for free to make their business better. All nVidia has to do is LISTEN TO THEM and release their drivers open-source.

Yes, there was a great amount of R&D involved in their drivers, but most of the stuff that makes their drivers 'great' on windows just doesn't apply to Linux, like that massive control panel. That doesn't even exist in the binary Linux driver.

The code doesn't have to be GPL or any such. They could release it under their own license that specifically states the code can only be used for a driver for nVidia cards. The only thing necessary is the ability to improve the code at will. (I think they would find it advantageous to go to GPL later, but that's another discussion.)

nVidia really has little reason not to open their source code to the public, unless they are doing something illegal or extremely unethical in their drivers. (Cheating at benchmarks, etc.)

Noticeable absence

[redelm]

I read TFA fairly closely, as usual looking as much for what could have been said but wasn't. iReading tea leaves. First, NVidia did not complain they had licenced technology from others which they couldn't "open source". It would have been a great excuse, but since they didn't use it, it doesn't apply.

Second, while they certainly want to be seen as supporting Linux, they really believe their closed-source drivers give them some source of competitive advantage. That's either in clever code or what the coding reveals about the internal organization of their GPU hardware. It would have been relatively easy and palatable to say: "We'd like to release full GPU asm specs and code, but believe this will help our competitors design better hardware. So we can only provide APIs." They didn't say this, so I think they consider their actual driver code to be very clever (main competitive advantage). No such secret will last.

Yes, I know there are many other explanations for "negative knowledge" -- things that didn't happen. But when they could have and would have been easy, perhaps we need to wonder why they didn't.

I'll still switch..

[pjr.cc]

ATI said they'll go OSS with their drivers and if they do i'll switch away from nvidia and be happy to do so given that article.

Re:A question

[mrcgran]

One big problem in not releasing the source code is that they actually are not making our computer experience better: their drivers have bugs, and we will be locked to whatever features and bugs THEY want to make available to us -- so, basically we become hostages of their will, they can do whatever they want, because whithout THEIR driver, your nvidia card isn't worth its weight.

In the future, when new versions and extensions of OpenGL are released, we won't have any guarantee that they will properly update the drivers. So, you'll probably won't be able to use their proprietary drivers in 5 years for new applications (shining new wobbling effects), because these apps will need new extensions, but the driver for your specific nvidia card is arbitrarily not supported anymore by them (they want to force you to throw the old one away). Too bad for you.

On the other side, if we have access to the source code (or at least the hardware specification), we don't even need nvidia's help: we can do the updates/bug-squatting ourselves, much better than a small team at nvidia. This is something that these companies don't get: the whole world is willing to write their drivers for free and maintain them to the end of times, but they refuse the consumer this right (or maybe they get, they just want you to throw away your old card and buy a new one). We don't want a huge amount of work from them, quite the contrary! It's *way* cheaper for them to release an open-source driver: it costs nada/zero, we can build one with the bare bones of a reasonable hardware specification, a little pdf file -- how much does it cost to post a pdf file on the Internet?

There's no RMS ideology in that, only the absolute minimum someone would expect in terms of support for something you bought. Nowadays, the choice is clear: go Intel X3000/X3500, which supports open source and you can be sure will always be up-to-date. Ignore nvidia and ati, until at least one day (I hope so) nouveau arrives.

nVidia PS3/Linux Driver?

[Doc Ruby]

How about a driver for Linux on the PlayStation 3, which would let the PS3 RSX chip actually work for Linux apps?

Right now PS3 Linux runs all display processing on the PPC core on the Cell, which needs to do a lot of other processing to keep the complex Cell going. Meanwhile there's an RSX chip that runs at 1.8TeraFLOPS, dwarfing even the Cell's 0.2TFLOPS. But Sony's Hypervisor virtualization layer that runs Linux hides the RSX from Linux. However, the RSX is exposed in some API, otherwise PS3 Linux wouldn't display on the HDMI port out of the PS3, and sound probably wouldn't work (probably also running on the RSX somehow).

Sony doesn't want the RSX exposed to Linux apps, because then Linux apps could compete with Sony-licensed games (without paying Sony the royalty that even subsidizes over 25% of the PS3 purchase price). But can't nVidia release a driver, or some kind of specs, that expose a 2D API for running X desktops? Sony's money all comes from 3D games.

Or maybe someone else has a way.

Re:nVidia's Buggy Closed-Source Drivers

[spikeb]

and get even worse drivers! horray!

Linux-certified hardware

[athloi]

Windows certifies hardware, and Apple makes it clear what they support. Could it be useful for an agency of Linux developers to certify hardware that is open (standards released so drivers can be written) and well-designed enough to support the rigors of a "UNIX-like" OS?

I do not know the answer to this one. My inner four-year-old anarchist is leery of certification in anything, but even something as simple as a list of supported hardware like BSD does, with the requirement that its standards be open so drivers can be developed, might help companies market to Linux users (1 in 10 users, by my estimate) and help Linux users get their market share behind a few quality products so they can stand up and be counted.

Just an idea. Feel free to mod -1, this guy's an idealistic moron.

Re:A question

[pkphilip]

Though one may argue that having the source for a driver may result in the driver becoming more stable over time as a lot of people contribute changes/fixes to it, I feel that this may be overstated.

Consider Nvidia/ATI drivers on Windows or Mac OSX - these binary-only drivers are feature rich (are they more feature rich than their binary-only drivers on Linux?) and most users are quite happy. Bugs do occasionally show up, but they are normally fixed by Nvidia/ATI within a reasonable time frame.

However, I have noticed that these same manufacturers take forever to fix bugs which show up only on Linux.

That indicates to me that the reason that these binary drivers are not that stable on Linux is not because of the binary nature of these drivers but because the Linux user community matters less to Nvidia/ATI than the Windows user community.

And that is understandable - the number of windows users is roughly 93% http://http//en.wikipedia.org/wiki/Comparison_of_W indows_and_Linux/ and Linux users probably account for about 3% to 4% for all computer users.

So it is understandable that a hardware manufacturer prioritizes bug fixes for their larger user base (windows) rather than for the Linux users.

Unless Linux gains the kind of market share which will force hardware manufacturers to take it seriously, we can expect less than stellar drivers and support from them.

Re:Video Acceleration Suppport

[kimvette]

Instead, I think the way to go is with Intel integrated GPUs. They don't have MPEG acceleration yet, but they are working on APIs and drivers to greatly improve this (the hardware has very good video support). I'm hoping Intel GPUs quickly become the far and away best option for Myth users.. let open source prevail.

Intel open source drivers are fine and all but before I abandon Nvidia for Intel I need:

  - Dual dual-link DVI ports (the nvidia cards we buy have these)
  - HDTV & S-video ports
  - dedicated video ram
  - in a discrete card (are there add-in video cards based on Intel GPUs?) - if I need to upgrade the video, or replace a bad video card, why the hell should I have to upgrade the board (and processor, and CPU) all at the same time?

I, for one, am hoping that AMD forces ATI to open up their drivers. THAT will create a ripple effect through the entire industry. Nvidia will have no choice but to follow suit.

Re:Video Acceleration Suppport

[sbryant]

I'm one of those people who are interested in better 2D acceleration and hardware MPEG-4/H264 acceleration. I'm a MythTV user. Nvidia's hardware does have support for such acceleration; they call it Purevideo. Unfortunately, the Linux drivers don't support it.

Well, the "nv" driver doesn't support it, but Nvidia's own driver does ("it" being the XvMC extension in Xorg).

Given that you're a MythTV user, here's a link to their Wiki, which contains a page about XvMC support.

The new 7050PV [nvidia.com] chipset would be perfect for a high-definition ...

I've not tried it, but the 7300GS just came out a month ago, and I happened to be upgrading so I got one - for 40 Euros; it's passively cooled, and so far has been working really well in TwinView mode on my Linux box. I use Kaffeine (Xine-based) rather than MythTV, but it's very smooth. I'm sure MythTV would be the same.

I wish Intel would release a standalone video card.

BTW, I'm using a machine with an integrated Intel VGA at work. It's OK - has open source drivers, and 3D acceleration, but it uses system memory, only has one output (not DVI either), and doesn't always behave itself. Personally, I much prefer the 7300. Oh yeah - the Intel driver supports XvMC too.

-- Steve

Re:NDAs and Patents Suck Life.

[mikael]

What you say is confusing and has the smell of a well crafted lie. Can you set me straight so I can understand why Nvidia is unable to do like Intel and fully co-operate with the free software community?

Have a look at NVidia's OpenGL specifications web-page

Every extensions comes with an IP Status field. For example ARB_color_buffer_float has the following:

IP Status

        SGI owns US Patent #6,650,327, issued November 18, 2003. SGI
        believes this patent contains necessary IP for graphics systems
        implementing floating point (FP) rasterization and FP framebuffer
        capabilities.

        SGI will not grant the ARB royalty-free use of this IP for use in
        OpenGL, but will discuss licensing on RAND terms, on an individual
        basis with companies wishing to use this IP in the context of
        conformant OpenGL implementations. SGI does not plan to make any
        special exemption for open source implementations.

        Contact Doug Crisman at SGI Legal for the complete IP disclosure.

Last I tried the 2d "nv" driver...

[mi]

It could not even support a dual-head setup. If that's what he means by "NVIDIA engineers actively maintain and improve", then it is simply sabotage:

• Why don't we fix the dual-head setup, boss?
• Because we want people to use "nvidia" driver instead.
• What do we care — we give it away for free anyway?
• Because we drop support for older cards from our official driver, thus pushing people to upgrade them.

The nv-driver was my only option on FreeBSD/amd64, yet it would not drive the second monitor, so I changed the card for a Radeon. The open-source driver for ATI, at least, supports dual head and plenty of other features found on the hardware.

OK, that Sucks Life.

[twitter]

Thanks for the link, it clears up a lot. The site itself is a pain, so it would probably be easier to Google site:developer.nvidia.com for "IP Status".

As for the example you give, Holy Shit!

SGI owns US Patent #6,650,327, issued November 18, 2003. SGI believes this patent contains necessary IP for graphics systems implementing floating point (FP) rasterization and FP framebuffer capabilities.

A patent on floating point raterization and framebuffers? Is that what I think it is? Yes it is. I can not think of anything more obvious in high quality imaging than representing the image as a floating point matrix. It may be true that there are still "fat line" patents out there.

Kudos to Nvidia for shining a small light on this insanity. Knowing the problem is always the first step. It would be nicer if they would put patent and other encumbering as symbos on the reference page and a link to the actual patent in the description page.

Re:NDAs and Patents Suck Life.

[Macthorpe]

Reading your posts today has been a joy. This piece of abject stupidity regarding patent licensing, and your other comments regarding GSM phones, have only proved that towing the /. party line leads directly to mod points, no matter how uninformed you actually are.

It's bloody obvious what's really happening here..

[advocate_one]

Microsoft are the real owners of the SGI OpenGL patents and are blocking this entire show by insisting on those anti-GPL RAND terms for the licensing... not SGI...

http://www.theregister.co.uk/2002/01/16/sgi_transf ers_3d_graphics_patents/

http://www.smithhopen.com/news_briefs_display.asp? ID=301

http://www.forrester.com/Research/LegacyIT/Excerpt /0,7208,28681,00.html

that last is is a doozy... they want $99 for a one page article...

Microsoft has nVidia over the certification barrel... if they make the nv driver support 3D, then nVidia may find it very difficult to get their windows drivers certified... they're having enough problems at the moment...

SGI aren't the problem

[Anonymous Coward]

As far as SGI have said (very publicly) there is nothing that SGI have patents for that they don't have a problem being GPL'd

Re:SGI aren't the problem

[ichigo 2.0]

They could always change their mind. The GPLv3 would help in this case only if SGI themselves distributed/contributed code that covered the patent in question. If they are really serious about not minding GPL code that use those patents, maybe they will release something under v3 themselves? Just saying something publicly doesn't make it legally binding.