From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: John Cavan <johncavan@home.com>
Cc: " Paul C. Nendick" <pauly@enteract.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.2.16 SMP: mtrr errors
Date: Tue, 12 Dec 2000 22:13:21 MET-1 [thread overview]
Message-ID: <F7CD5C16569@vcnet.vc.cvut.cz> (raw)
On 12 Dec 00 at 16:07, John Cavan wrote:
> Petr Vandrovec wrote:
> > > kernel: mtrr: base(0xd4000000) is not aligned on a size(0x1800000) 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 0xd4000000, or
> > teach X that your device occupies 32MB and not 24 (you should do it anyway,
> > region size can be only power of two)...
>
> 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'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.
Matroxfb also splits Matrox memory in 24:8, but it registers only one
region in mtrr. Of course, in X, as mtrr registration is done by map
videomemory, you must tell this function to not register mtrr...
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-12 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-12 22:13 Petr Vandrovec [this message]
2000-12-13 7:33 ` 2.2.16 SMP: mtrr errors Boszormenyi Zoltan
-- strict thread matches above, loose matches on Subject: below --
2000-12-12 21:43 Petr Vandrovec
2000-12-12 21:07 ` John Cavan
2000-12-12 21:23 ` Alan Cox
2000-12-11 21:58 ` Paul C. Nendick
2000-12-13 2:07 ` David Wragg
2000-12-12 21:36 ` John Cavan
2000-12-13 10:55 ` Jamie Lokier
2000-12-11 20:00 Paul C. Nendick
[not found] ` <Pine.LNX.4.10.10012121511190.28197-100000@coffee.psychology.mcmaster.ca>
2000-12-11 20:23 ` Paul C. Nendick
2000-12-12 20:19 ` John Cavan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F7CD5C16569@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=johncavan@home.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pauly@enteract.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox