Slashdot Mirror


NVIDIA Responds To Linus Torvalds

jones_supa writes "NVIDIA's PR department has issued a statement following the harsh comments by Linus Torvalds last week where he referred to the graphics company as the single worst company he's ever dealt with, called them out on not supporting Optimus, and other issues. Basically the company replied they're committed to Linux using their proprietary driver that is largely common across platforms, and this allows for same-day Linux support with full OpenGL implementation. They also say that they're active in ARM Linux for Tegra and support a wide range of hardware under Linux. Despite having not made any commitment to better support Optimus under Linux nor providing technical assistance to the Nouveau community, NVIDIA assures us that 'at the end of the day, providing a consistent GPU experience across multiple platforms for all of our customers continues to be one of our key goals.'"

8 of 497 comments (clear)

  1. Re:I'd agree with them on that.. by TWX · · Score: 4, Interesting

    I don't need my graphics driver to necessarily be open-source. I need my graphics accelerator to function though, and it's been my experience that proper acceleration support has lagged. Simply bringing up a desktop in X is not the same as being able to navigate a 3d environment at-speed at the quality that the video card manufacturer touts. If they won't support 3d acceleration then I'm better off dusting off my old S3 Virge and buying a much more powerful microprocessor, letting the microprocessor do all of the work.

    If these cards don't do 3d acceleration in my computing environment, what good are they?

    And yes, I had this problem once before, with Matrox and the G450/G550 cards, back in the day. Aggravating as hell. Worse, if you were their corporate customer and asked for 3d accleration drivers they'd release them to you, but as a private consumer you had to justify the need. Apparently nothing that a noncommercial user did was considered justified. It was friggin' compiled! I wasn't even asking for source code!

    --
    Do not look into laser with remaining eye.
  2. "consistent" experience? by DdJ · · Score: 4, Interesting

    They're saying "providing a consistent GPU experience across multiple platforms for all of our customers continues to be one of our key goals".

    So, my interpretation of that is:

    "If we released the drivers as open source, then people might figure out how to optimize and tune the Linux drivers. This could result in a better GPU experience on Linux than under Windows. That would embarrass us. To ensure a consistent experience across platforms, we therefore must prevent others from tinkering with the drivers, which mandates closed source."

    Does anyone else read it that way?

  3. Re:Cannot open drivers source by am+2k · · Score: 4, Interesting

    Most common excuse for don't open the source for drivers is IP. But most part of times, the real reason is users will see there is no difference in hardware between standard and platinum cards.

    Well, there's one that's not visible in software: The RAM is tested to be less error-prone. If one pixel in a game isn't correct for 1/60 of a second, it doesn't matter. However, it does matter (potentially literally making the difference between life and death) when your CUDA calculation returns incorrect values.

  4. Disappointing response by peppepz · · Score: 5, Interesting

    Basically they're confirming Linus' words, not denying them. Linus never said that they don't make good drivers. He said that they suck at doing open source, which is an objective truth. Their response is that they do that because they don't want to invest resources to specifically support Linux. Which is exactly what Linus was upset about.

  5. Right to Repair bill in Massachusetts by Latent+Heat · · Score: 5, Interesting
    The Commonwealth of Massuchesetts is going to have a ballot question on whether auto companies have to reveal all of their "codes" so that independent repair shops (and I guess do-it-yourself people) would have access to diagnostics on cars. Some assembly member is attempting legislation to preempt the referendum question, telling the auto companies, "We can do this the easy way, or we can do this the hard way . . ."

    So, maybe we could get Bay State voters interested in open other things?

    1. Re:Right to Repair bill in Massachusetts by Lonewolf666 · · Score: 5, Interesting

      Getting a bit off topic, but I don't see the conflict between Federal law and state law.

      By not providing the codes (including decryption codes for encrypted onboard electronics) the auto manufactures would be violating state law. Instead of trying to crack the encryption, auto mechanics could sue them. No DMCA violation necessary there.

      --
      C - the footgun of programming languages
  6. Re:The community failed on ATi by cockroach2 · · Score: 4, Interesting

    Huh? The radeon driver is pretty damn good these days.

  7. MBA's and idiots without cloths. by bored · · Score: 4, Interesting

    They all think there is secret sauce in their product with some genuine trade secret level information.

    In reality, having seen the secret sauce from a 3rd party perspective a few times, it turns out that often times the competitor is doing it basically the same way. So the only people being hurt by not publishing the hardware specifications (as was the normal state of things until the late 1990's) are the hackers and budding engineers trying to make the product better in some way.

    In the case of graphics companies, it seems they are somewhat justified for not releasing the source to the proprietary drivers, as that is such a huge part of their performance work (aka sometimes the games aren't faster because the hardware is faster, they are faster because the driver is using a better algorithm, or has more micro optimization). Not releasing the hardware specs is just silly, because at this point, a big portion of the graphics chips are understood well enough that releasing information on mode setting or shader setup is more like filling in the details, rather than giving away any secrets.

    The Optimus stuff is a prime example, its basically just going to be information on enabling/disabling parts of the chip or setting power envelops for certain functions. The real secret sauce is how to use that information. I have a similar issue with my little NAS box at home based on a guru plug. Marvell claims to be open source friendly, and gives away specifications that look good until you actually try to do something like power down an unused sata port. Then your SOL without the NDA, because knowing the register which controls the power gating is some kind of secret....

    Mostly, what is being hidden is the fact that the emperor has no cloths.