Nvidia Engineer Asks How the Company Can Improve Linux Support

sfcrazy writes "It seems that recent comments made by Linus Torvalds have made the people at NVIDIA take Linux more seriously. Recently Nvidia employee Stephen Warren asked in the Kernel Summit mailing list what could be done differently to make Linux support better. 'In a Google+ comment, Linus noted that we have mainly been contributing patches for Tegra SoC infra-structure details. I'm curious what other areas people might expect me/NVIDIA to contribute to. I assume the issue is mainly the lack of open support for the graphics-related parts of our HW, but perhaps there's some expectation that we'd also start helping out some core area of the kernel too? Would that kind of thing help our image even if we didn't open up our HW?'"

Comments

Ugh, this makes me mad.

[intellitech]

[...] we'd also start helping out some core area of the kernel too? Would that kind of thing help our image even if we didn't open up our HW?

You seem to care more about NVIDIA's image than about what the Linux community actually needs.

I truly don't understand what the big deal is. Just open up your damn specifications already.

Re:Ugh, this makes me mad.

[ethan961]

If this engineer knows that will never happen (through no fault of his own, higher-ups would have decided this) then at least he's making an effort. People can get upset all they want, but nothing other than good is going to come out of this, whether it's exactly what would be ideal or not. Some help is better than none.

Re:Ugh, this makes me mad.

[SwashbucklingCowboy]

"You seem to care more about NVIDIA's image than about what the Linux community actually needs."

Of course they do. Why in the world would this surprise you? It's a public, for-profit company. The vast majority of contributions to open source by companies are not done out of altruism. They're done out of self-interest.

"I truly don't understand what the big deal is. Just open up your damn specifications already."

There's probably something in how they do things that they think (rightly or wrongly) that gives them an advantage over their competition that either isn't patented or can't be patented (or maybe violates someone else's patents).

Re:Ugh, this makes me mad.

[Sir_Sri]

Or would give away something about how their hardware, or hardware development works that they don't want anyone to know too much about. Or at least not to wave around in public. I'm sure AMD know, enough staff move back and forth, but some random chinese hardware maker, that I'd be worried about.

Remember nVIDIA sells it's 'first silicon' runs, they don't usually prototype, they do simulations first, and from the simulations that are used to design the hardware they go straight to manufacturing. It's possible some of their driver support would have some hooks (or parts) of their simulation tools in it that they don't really want to be broadcasting around.

But broadly ya, for whatever reason, if their higher ups don't want to be telling the world how their drivers work, and so they won't. Hell for all we know it could be entirely paranoia from an MBA type who just doesn't understand and doesn't want his ass fired if something goes wrong.

Re:Ugh, this makes me mad.

[X0563511]

We're asking for specs, not driver code. There's no reason they would have to give us any of those simulation hooks, or any information about them.

Re:Ugh, this makes me mad.

[rtfa-troll]

If this engineer knows that will never happen (through no fault of his own, higher-ups would have decided this) then at least he's making an effort. People can get upset all they want, but nothing other than good is going to come out of this, whether it's exactly what would be ideal or not. Some help is better than none.

Right; I'm not getting upset about him. We love him and if he ever gets kicked out by NVIDIA, I'm sure there are lots of us here who will want to hear about it and offer him a job. What upsets us is that NVIDIA clearly has people who understand that we are upset and why we are upset and they still don't do anything. From my point of view this makes things even worse.

NVIDIA; please: even if it's incomplete and misses your latest fastest newest stuff, please provide the Linux developers; both kernel and Noveau; with publishable open documentation which tells them how to set up the rest of the features and at the very least provide good, reliable and colour tunable 2D and low level support for your cards. Preferably provide full, documented access to any feature older than two years.

This can have no possible bad influence on your competitive advantage and will go a long way to making those of us using Linux happier.

Re:Ugh, this makes me mad.

[SplashMyBandit]

> The pilot project was worth an initial 250-350 million dollars, with the potential of much more to follow.
People always say this, "more work to follow" but it hardly ever works out like that. The Chinese are notorious (as in *consistently and repeatedly*) ask for samples with the promise of more orders and they take it apart and reverse engineer it. They do this with electronics, shoes, ships, MiG and Sukhoi jets, missiles, commercial agricultural strains even Austrian towns. I'm not anti-Sino, just reporting what has been documented as happening and appears to be a sustained, systematic and government condoned effort to make unlicensed copies of technology (that is, 'steal'). Perhaps NVidia were aware of this, even if many Slashdotters are not.

Optimus

[jaminJay]

Better power management. KMS. More timely releases. Stop whinging that there are problems with Linux/Xorg/whatever preventing you from doing something and work with those up-streams to fix it. Stop making excuses, start releasing code. Extract the proprietry stuff to (a) smaller blob(s) and expose the trivial interconnects and such at the very least. Never say it can't be done: everything's possible. Etc.

Re:The very thing that they don't want to do.

[Gaygirlie]

Open up the hardware such that proper drivers can be written for any card (recent or not) and platform w/o the need of binary blobs.

That shouldn't be an impossible task given how much weight NVidia has towards third parties.

People keep spouting these things without actually taking into account that NVIDIA most likely has all sorts of contracts and license agreements they just can't break. Yes, it's fun to bash NVIDIA and try to paint them as some sort of a big, black demon worth all the hatred in the world, but in the end that doesn't actually *help* anyone, least of all F/OSS movement. Intel has the advantage in that that they entered the GPU-market a lot later than NVIDIA et.al., so they could avoid many of the mistakes their competitors did and they also have the whole, complete chain needed to produce and ship GPUs all by themselves and that really makes the comparison feel more like apples and oranges than anything directly comparable.

NVIDIA could possibly open up future hardware, but they'd still possibly have to then develop some areas completely from scratch in order to not run afoul of their previous engagements and such a move obviously would cost them huge amounts of time and money. And well, Linux-users simply ain't worth that. All this is to say that NVIDIA should open up as much as they can, that I agree with, but that it is also highly unlikely they could open it all up even if they wanted to.

Re:The very thing that they don't want to do.

[Gaygirlie]

I see why you're writing as an AC.

because nothing prevents nVidia from collaborating

Copyright, patent and contract laws quite likely do. Oh, but let's not let real-life facts bother us, eh? Ignorance is a bliss and all that.

Re:Same thing as always

[Crosshair84]

All that's needed is for Nvidia to release the documentation on the components they manufacture, as AMD/ATI did in 2008 (and Intel has always done). The existing nouveau driver team will take it from there.

Yea, how well has that actually worked. Oh yea, it's failed miserably. 4 years later and ATI Linux drivers are still garbage and the only reason Intel drivers work is because of the server market and because chips don't change often. It's not rocket science, writing graphics drivers are HARD and Linus continually poking his pecker into the kernel means they continually break and have to be tinkered with to work again.

The VOIP visitation recorders at work have to have updates turned off because Ubuntu craps itself whenever it tries to update. When the box is 4 hours away that is a big deal. Our windows machines have auto-updates turned on and never have problems. We've tried having a development machine at the office to test the updates, but for whatever reason, the number of VOIP boxes and minor hardware revisions make it impossible to develop a standard update profile for us to reliably push out to all machines. So we have to just lock them down as much as we can and hope for the best. We are working on a Windows based solution so we can eliminate the Linux boxes in the future.

It needs to be repeated so it sinks in, Linux needs a reliable ABI so ATI and others can just slap a Linux driver onto the CD that comes with the card and call it a day.

The Good, the Bad, and the Ugly

[DrJimbo]

Years ago I got good support from Nvidia. I had a problem and sent a bug report and got a response late on a Saturday night (West Coast) that involved a kernel patch to fix a bug in the kernel that was causing the problem. I was an Nvidia fanboy for many years after that. I helped dozens of people get things like Twinview working.

In recent years, working with Nivida has been very frustrating and I can no longer recommend them for Linux systems. For example some interaction between closed-source Flash and the closed-source Nvidia drivers turns people blue in Youtube videos but not other sites.

There has also been a heart breaking struggle to remove video "tearing" (vsync problem) when watching dvds and blurays. The last time I checked I needed to use the GL video to remove tearing when watching dvds but I still have some tearing when watching blurays which is kind of heart breaking. At the very least Nvidia should have a sticky post in the Linux forum explaining all the hoops one must jump through to try to get rid of video tearing. Also, having the sticky posts show up on all pages, not just the first page is a big PITA. It wastes my time and attention. It is disrepectful.

I don't understand why video tearing is such a recurring problem. Are these environment variables still needed?

export VDPAU_NVIDIA_SYNC_DISPLAY_DEVICE="DFP-0"
export __VDPAU_NVIDIA_SYNC_DISPLAY_DEVICE="DFP-0"
export GL_SYNC_TO_VBLANK=1
export __GL_SYNC_TO_VBLANK=1
export GL_SYNC_DISPLAY_DEVICE="DFP-0"
export __GL_SYNC_DISPLAY_DEVICE="DFP-0"

When an nvidia driver update causes tearing to start again, or worse, if it causes X (or the entire machine) to crash, it feels like you are telling me "F- you!"

I get it that opening up your drivers is not an option. The problem is that this decision causes a lot of breakage and you do not make it easy to fix this breakage. Please just make it easy for me to get your drivers to work. Is Twinview plus non-tearing video playback really too much to ask for? Also, what about the problem with non-tearing and composite? Has that ever been fixed? If not, maybe that's something you could help with.

Years ago I felt like I was getting support. Nowadays I'm not feeling the love.

Re:Nvidia Open Source Policies

[Chibi Merrow]

Eventually this policy is going to cost Nvidia in the pocket book, and they will either come around or sink into nothingness.

And yet, our new deployment of thirty Linux-based image generators I just setup all have GeForce cards in them... Do we live in the same world?

nVidia cards, with nVidia's binary blob driver, are the only way I can get any work done in Linux. That doesn't seem to be changing anytime soon, either.

I wish it would. My home PC has a Radeon card... But the support under Linux just isn't there.