All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Jamie Lokier <jamie@shareable.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@muc.de>,
	kraxel@suse.de, jsimmons@infradead.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Use MTRRs by default for vesafb on x86-64
Date: Mon, 19 May 2003 02:24:25 +0100	[thread overview]
Message-ID: <20030519012425.GB18507@suse.de> (raw)
In-Reply-To: <20030519002820.GA9048@mail.jlokier.co.uk>

On Mon, May 19, 2003 at 01:28:20AM +0100, Jamie Lokier wrote:

 > > It works just fine. Just you can't enable MTRRs for framebuffer memory.
 > > Losing a bit of performance for what is (by todays standards) a crap
 > > performing card anyways, is no big deal.
 > 
 > How do you know the blacklist is complete?

no-one complains that they see random crap on their screens any more.
 
		Dave


  reply	other threads:[~2003-05-19  1:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15 14:56 [PATCH] Use MTRRs by default for vesafb on x86-64 Andi Kleen
2003-05-15 15:16 ` Dave Jones
2003-05-15 15:20   ` Andi Kleen
2003-05-15 15:25     ` Dave Jones
2003-05-16 20:51   ` Alan Cox
2003-05-18  5:39     ` Andi Kleen
2003-05-18 16:11       ` Jamie Lokier
2003-05-18 20:40         ` Alan Cox
2003-05-18 22:34           ` Jamie Lokier
2003-05-18 22:52             ` Dave Jones
2003-05-18 23:33               ` Jamie Lokier
2003-05-19  0:02                 ` Dave Jones
2003-05-19  0:28                   ` Jamie Lokier
2003-05-19  1:24                     ` Dave Jones [this message]
2003-05-16 22:58 ` Eric W. Biederman
2003-05-19 10:37   ` Andi Kleen
2003-05-19 12:26     ` Eric W. Biederman
  -- strict thread matches above, loose matches on Subject: below --
2003-05-19  9:16 Etienne Lorrain

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=20030519012425.GB18507@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=ak@muc.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jamie@shareable.org \
    --cc=jsimmons@infradead.org \
    --cc=kraxel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.