Has anyone any objections to me removing the MTRR code from the DRM.

It doesn't have the intimate knowledge needed to properly configure
MTRR's and fails in many cases.

There are two cases currently, one for the framebuffer and a second for
the entire AGP space.

Certainly in Intel hardware this is the same memory space and you always
get bogus error messages in your kernel logs as things fail due to lack
of boundary checks.

I'm more of the opinion that it should be left up to userspace to
configure MTRR's if it indeed wants them and we shouldn't force them
within the DRM.

Additionally, the Xserver (for user-space) already sets up the MTRR's,
as should Xgl (Xegl) or other user space apps.

What makes the situation a little worse is that vesafb (and other *fb
drivers) also setup an mtrr which frequently stops subsequent processes
from adding a new one that overlaps an existing write-combining range.
But the *fb drivers do provide a nomtrr option in many cases. (But I'd
like to remove it from them too :-) or at least default those to off)

Comments ??

Alan.


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to