Why would Nvidia use KMS, when they have their own modesetting in the kernel (well, in their kernel module)? They don't use DRI or AIGLX or EXA either, and yet no one is harping on them for that. But when it comes to modesetting, there's screaming for KMS.
If it's a high-res console you want, then say so. But KMS is not the one true holy way to achieve that. I don't think there's anything preventing Nvidia from implementing a fbcon driver on top of their modesetting, a "nvidiablobfb" if you will. Well, except incentive. If there is a technical reason I don't know about preventing Nvidia from creating that, please tell.
About Wayland, ninez covered that. Nvidia isn't "refusing" anything, there's just no incentive yet to support it. It's API isn't even finalized yet AFAIK, there'll be changes still until 1.0 is released.
If it's a high-res console you want, then say so. But KMS is not the one true holy way to achieve that. I don't think there's anything preventing Nvidia from implementing a fbcon driver on top of their modesetting, a "nvidiablobfb" if you will. Well, except incentive. If there is a technical reason I don't know about preventing Nvidia from creating that, please tell.
About Wayland, ninez covered that. Nvidia isn't "refusing" anything, there's just no incentive yet to support it. It's API isn't even finalized yet AFAIK, there'll be changes still until 1.0 is released.
Comment