From: Dave Jones <davej@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: adaplas@gmail.com, adaplas@pol.net, linux-kernel@vger.kernel.org,
ak@suse.de
Subject: Re: vesafb-fix-mtrr-bugs.patch added to -mm tree
Date: Fri, 29 Jul 2005 14:58:48 -0400 [thread overview]
Message-ID: <20050729185848.GP17003@redhat.com> (raw)
In-Reply-To: <200507291825.j6TIParH012406@shell0.pdx.osdl.net>
On Fri, Jul 29, 2005 at 11:24:37AM -0700, Andrew Morton wrote:
> From: "Antonino A. Daplas" <adaplas@gmail.com>
>
> >> vesafb: mode is 800x600x16, linelength=1600, pages=16
> >> vesafb: scrolling: redraw
> >> vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
> >> mtrr: type mismatch for fc000000,1000000 old: write-back new: write-
> >> combining
>
> Range is already set to write-back, vesafb attempts to add a write-combining
> mtrr (default for vesafb).
>
> >> mtrr: size and base must be multiples of 4 kiB
>
> This is a bug, vesafb attempts to add a size < PAGE_SIZE triggering
> the messages below.
I fixed this a few weeks back. It's this line which your patch removes..
- while (temp_size > PAGE_SIZE &&
> To eliminate the warning messages, you can add the option mtrr:2 to add a
> write-back mtrr for vesafb. Or just use nomtrr option.
If we need users to pass extra command line args to make warnings go
away, we may as well not bother. Because 99% of users will be completely
unaware that option even exists. They'll still see the same message,
and still report the same bugs.
The pains of MTRR strike again. This stuff is just screaming for
a usable PAT implementation. Andi, you were working on that, any news ?
Or should I resurrect Terrence's patch again ?
Dave
next parent reply other threads:[~2005-07-29 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200507291825.j6TIParH012406@shell0.pdx.osdl.net>
2005-07-29 18:58 ` Dave Jones [this message]
2005-07-30 1:08 ` vesafb-fix-mtrr-bugs.patch added to -mm tree Andrew Morton
2005-07-30 1:40 ` Antonino A. Daplas
2005-08-03 14:25 ` Andi Kleen
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=20050729185848.GP17003@redhat.com \
--to=davej@redhat.com \
--cc=adaplas@gmail.com \
--cc=adaplas@pol.net \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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