Alan Cox wrote:
> > Petr, the Matrox card splits the memory between the two video screens
> > when running in a multi-head configuration and "pretends" that it is two
> > distinct cards. Thus, a 32 mb card will register an mtrr for 24mb and
> > for 8mb seperately when in this mode.
>
> That is a
On Tue, 12 Dec 2000, Petr Vandrovec wrote:
> That's wrong. They must first register MTRR and then split it to
> 24+8, as they cannot register 24MB range. They can split it
> 16+16, or (16+8)+8, but at cost of 1 (or 2) additional MTRR entries -
> and there is very limited number of possible MTRRs.
" Paul C. Nendick " <[EMAIL PROTECTED]> writes:
> Shall I submit this to Matrox as a bug then?
The "bug" is in the XFree86 core, so telling Matrox might not do a lot
of good.
The driver code just says "I want to map a framebuffer of this size at
this physical address" (or actually "with these PC
Shall I submit this to Matrox as a bug then?
/paul
Alan Cox ([EMAIL PROTECTED]) said:
> > Petr, the Matrox card splits the memory between the two video screens
> > when running in a multi-head configuration and "pretends" that it is two
> > distinct cards. Thus, a 32 mb card will register an mt
Alan Cox wrote:
> > to fall through, but is this correct? I've inserted a break at the end
> > of the Intel switch before and have not had problems, but I left it out
>
> Lucky
Wouldn't be the first time...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
> Petr, the Matrox card splits the memory between the two video screens
> when running in a multi-head configuration and "pretends" that it is two
> distinct cards. Thus, a 32 mb card will register an mtrr for 24mb and
> for 8mb seperately when in this mode.
That is a driver bug. The intel proces
On 12 Dec 00 at 16:07, John Cavan wrote:
> Petr Vandrovec wrote:
> > > kernel: mtrr: base(0xd400) is not aligned on a size(0x180) boundary
> > > last message repeated 2 times
> >
> > For some strange reason X thinks that you have 24MB of memory on the G450.
> > You can either create 32MB
Petr Vandrovec wrote:
> > kernel: mtrr: base(0xd400) is not aligned on a size(0x180) boundary
> > last message repeated 2 times
>
> For some strange reason X thinks that you have 24MB of memory on the G450.
> You can either create 32MB write-combining region at 0xd400, or
> teach X th
On 11 Dec 00 at 14:00, Paul C. Nendick wrote:
> -Matrox g450 32MB RAM dual-heal AGP video card w/ hand compiled X driver
> from matrox
Make sure you do not use either matroxfb or XFree's driver... Same chip
ID, but different ramdac :-(
> and immediately after starting X:
>
> kernel: mtrr: b
See my answers inline below. /paul
Mark Hahn ([EMAIL PROTECTED]) said:
> > kernel: mtrr: base(0xd400) is not aligned on a size(0x180) boundary
>
> X is trying to set an mtrr for the framebuffer. the odd thing
> is that its trying to set a 24M mtrr, which is pretty strange.
> what does
> kernel: mtrr: base(0xd400) is not aligned on a size(0x180) boundary
> last message repeated 2 times
>
> and finally:
>
> %cat /proc/mtrr
> reg00: base=0x ( 0MB), size= 256MB: write-back, count=1
> reg01: base=0xd000 (3328MB), size= 64MB: write-combining, count=1
> reg02:
Please cc: any responses to my email address <[EMAIL PROTECTED]>
My setup
-A standard install of RedHat 7.0 with the 2.2.16smp w/ hand compiled X
4.0.1 to support xinerama
-Tyan tiger 133 s1834 motherboard (VIA Apollo Pro133A Chipset)
-256mb PC133 RAM
-Two 800 Mhz PIII eb Slot-1 CPU's
-Matrox g4
12 matches
Mail list logo
