Linked by Hadrien Grasland on Thu 13th Jan 2011 17:13 UTC, submitted by Michael
Permalink for comment 457848
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2007-02-17
This story that proprietary drivers won't work with Wayland is incorrect. It won't CURRENTLY work, but the Wayland devs have already stated that it would be simple to add another backend which could call into the proprietary drivers. The KMS interface in Wayland could easily be extended by NVidia and AMD, just as they are already extending parts of X now. "
KMS and kernel memory management are dependencies for Wayland support. The kernel developers will not accept KMS and kernel memory management pieces if the rest of a graphics driver is a binary blob. Wayland might be a different matter, but as it stands the graphics driver binary blobs will never be part of the kernel.