I'm sorry, but I don't understand your point. To my knowledge NVIDIA doesn't use KMS in their proprietary driver. They have a completely separate graphics stack in the kernel. So why would they be affected by problems in Linux' KMS. Also why would they start caring about this now and not 5 years ago, when KMS was new?
If it's not for Steam, I could imaging that they want support for Wayland without committing resources for maintaining a KMS driver. Supporting nouveau with documentation is the next best option then.
Posted Sep 27, 2013 14:35 UTC (Fri) by Lovechild (subscriber, #3592)
[Link]
The problem nvidia is facing is that distributions will be or is using boot splashes and/X technology that relies on KMS. They could at best screw up only a boot splash but the pain just grows.
If they inplement KMS support in their driver they will at least subject that part to the GPL2 clause relating to derived work. Effectively meaning at least the parts KMS support touches would have to be under the GPL2 like the Linux kernel. Nvidia really don't want that, likely for legal reasons. E.g. they might not be absolutely sure all their code base is licensed as to allow them to open source it, in cases of code that comes along with buying another company. The answer might simply be a complicated, expensive "we don't know for sure, better not".
Button line expect nvidia to be able to play this many ways. Initially it might allow them to easily run on modern Linux distributions with their existing code. Long term it might allow them to move some parts more in the open if that makes sense for them (e.g. the way Intel's Graphics drivers work in many ways)