Linked by Hadrien Grasland on Thu 13th Jan 2011 17:13 UTC, submitted by Michael
Linux "Now that the kernel mode-setting page-flipping for the ATI Radeon DRM kernel module has been merged into the Linux 2.6.38 kernel and the respective bits have been set in the xf86-video-ati DDX, we're in the process of running new open-source ATI graphics benchmarks under Linux. Our initial results (included in this article) show these latest improvements to cause some major performance boosts for the open-source ATI driver as it nears the level of performance of the proprietary Catalyst driver."
Thread beginning with comment 457844
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: great
by smitty on Fri 14th Jan 2011 08:47 UTC in reply to "RE: great"
smitty
Member since:
2005-10-13

won't ever run KMS or kernel memory management (because the kernel guys won't accept driver code which is only a part of a driver), and hence will never be able to run Wayland or rootless X.


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.

Reply Parent Score: 2

RE[3]: great
by lemur2 on Fri 14th Jan 2011 09:18 in reply to "RE[2]: great"
lemur2 Member since:
2007-02-17

"won't ever run KMS or kernel memory management (because the kernel guys won't accept driver code which is only a part of a driver), and hence will never be able to run Wayland or rootless X.


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.

Reply Parent Score: 2

RE[4]: great
by Gusar on Fri 14th Jan 2011 10:23 in reply to "RE[3]: great"
Gusar Member since:
2010-07-16

KMS and kernel memory management are dependencies for Wayland support.

No they're not. Modesetting in the kernel is a requirement, not specifically KMS. Same for memory management. Yes, *currently* Wayland is hardcoded to use DRI2, but like the other comment says, it's a simple adjustment to allow for non-DRI2 drivers and the Wayland people are willing to do it.

Reply Parent Score: 1

RE[4]: great
by sj87 on Fri 14th Jan 2011 10:49 in reply to "RE[3]: great"
sj87 Member since:
2007-12-16

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.

Nothing is demanding the drivers to be integrated in the kernel code. Afaik they can still be loaded as modules as is the situation now.

The downside of these external, closed, modules is that they need to be updated everytime the kernel changes. AMD's proprietary drivers are always usually one or two Xorg versions behind, because they are slow to add new support.

That prevents people from using the latest version, which again might introduce new limits for other software.

Edited 2011-01-14 10:50 UTC

Reply Parent Score: 2