Matteo Giani writes:
> Hi all.
> I know this has probably been asked a million times, I just couldn't
> find a clear answer. I apologize in advance for this...
> As I read on usenet, it is a known issue that xfree86 4.2.0 tries to
> split the framebuffer into tiny regions and setup hundreds of write
> combining ranges on savages with shared memory. Sadly, I ran into this
> issue just tonight when my apt upgraded X to 4.2.1 (it used to work on
> 4.1.0). I was just wondering if anyone has come up with a workaround/fix
> for it.
> Sorry if this has been asked just too many times...
> Best regards.
>
It is very surprising that this still happens.
I've reworked the mtrr code to try its best to avoid this.
Please send me the relevant part of your log file.
In principle the driver should make sure that the condition
(<framebuffer start address> & size == 0)
is met as the CPU has this requirement for the ranges.
Regards,
Egbert.
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
