From: Gerd Knorr <kraxel@bytesex.org>
To: pawfen@wp.pl
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: MTRR vesafb and wrong X performance
Date: 29 Nov 2004 12:12:08 +0100 [thread overview]
Message-ID: <87is7ogb93.fsf@bytesex.org> (raw)
In-Reply-To: <1101419803.1764.23.camel@PC3.dom.pl>
Pawel Fengler <pawfen@wp.pl> writes:
> > Please send the full dmesg output and the contents of /proc/mtrr for
> > 2.6.10-rc2.
> reg02: base=0xe3000000 (3632MB), size= 4MB: write-combining, count=1
> vesafb: framebuffer at 0xe3000000, mapped to 0xcc880000, using 1875k,
> total 4096k
The BIOS reports 4MB video memory, and vesafb adds an mtrr entry for
that. Looks ok, with the exception that the reported 4MB are probably
not correct, otherwise the X-Server wouldn't complain. vesafb in
2.6.10-rc2 has a option to overwrite the BIOS-reported value
(vtotal=n, with n in megabytes), that should fix it.
The reason that you don't see this with old kernels probably is just
that vesafb doesn't create mtrr entries by default in 2.4.x
Gerd
--
#define printk(args...) fprintf(stderr, ## args)
next prev parent reply other threads:[~2004-11-29 11:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 23:15 MTRR vesafb and wrong X performance Pawel Fengler
2004-11-25 1:18 ` Andrew Morton
2004-11-25 21:56 ` Pawel Fengler
2004-11-29 11:12 ` Gerd Knorr [this message]
2004-11-29 15:40 ` Dave Jones
2004-11-29 16:22 ` Gerd Knorr
2004-11-29 16:57 ` Dave Jones
2004-11-29 17:34 ` Gerd Knorr
2004-11-29 17:22 ` Alan Cox
2004-11-29 18:17 ` Dave Jones
2004-11-29 17:23 ` Alan Cox
2004-11-29 16:24 ` Alan Cox
2004-11-25 8:49 ` Gerd Knorr
-- strict thread matches above, loose matches on Subject: below --
2004-11-26 16:48 Pawel Fengler
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=87is7ogb93.fsf@bytesex.org \
--to=kraxel@bytesex.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawfen@wp.pl \
/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