Vincent ETIENNE <[EMAIL PROTECTED]> posted
[EMAIL PROTECTED], excerpted below, on  Wed, 29 Aug 2007
23:10:45 +0200:

> I own a gigabyte motherboard ( G33-DS3 ) with intel G33 chipset and i 'm
> unable to made drm working. The problem is (as far as i have understood
> it) that due to having 4G ram my mtrr is full so X11 can't succeed in
> adding a new entry to made it write-combining.

This probably won't help you directly, but here, running 8 gig memory on 
a dual Opteron Tyan (s2885) mobo, original AMD 8000 chipset, with a 
Radeon 9200SE, with the native kernel and xorg drivers, DRM works fine, 
even tho it /does/ protest about running out of MTRRs.

So running out of MTRRs shouldn't be an absolutely critical error to 
getting DRM running, or at least it isn't on some chipsets/cards/drivers.

However, why I /really/ posted is to ask if anyone has any solid info on 
getting MTRRs setup correctly, when one is obviously running out.  How 
does one find out what each one is for and figure out how to prioritize 
them?  I understand that they can overlap if necessary, a larger one with 
a smaller one superseding it for a specific area of memory.  If that's 
so, in theory, it may be possible to optimize placement to use fewer, 
thus freeing a few for other usage.  Or as I said, maybe prioritize them, 
so something legacy isn't given its own MTRR (if the larger one 
underneath it is suitably configured) thus allowing it to be used for 
video or other high(er) priority applications.

So basically I'm seconding your request.  Point me at some really 
practical usable info on these things, so I can either optimize my usage, 
or be fully satisfied that it's not possible to do so, instead of 
thinking it /probably/ is based on very spotty and incomplete knowledge 
some of which is of doubtful validity or general application, but not 
knowing so or knowing how.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
[EMAIL PROTECTED] mailing list

Reply via email to