linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: kraxel@suse.de, jsimmons@infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Use MTRRs by default for vesafb on x86-64
Date: Thu, 15 May 2003 16:56:40 +0200	[thread overview]
Message-ID: <20030515145640.GA19152@averell> (raw)


x86-64 cannot call the 32bit VESA BIOS. This means when vesafb is active
it does software copying in the vesa frame buffer. This is insanely slow
when the frame buffer is not marked for write combining. 

Some discussion showed that the use_mtrr flag was only off for some 
old broken ET4000 ISA card. x86-64 has no ISA, so this is no concern.
Make the default depend on CONFIG_ISA. 

Patch for 2.5.69.  Originally suggested by Gerd Knorr.

-Andi

--- linux/drivers/video/vesafb.c	2003-05-08 04:52:58.000000000 +0200
+++ linux-2.5.69-amd64/drivers/video/vesafb.c	2003-05-15 16:55:51.000000000 +0200
@@ -51,7 +51,11 @@
 static u32 pseudo_palette[17];
 
 static int             inverse   = 0;
+#ifndef CONFIG_ISA 
+static int 	      mtrr	 = 1;
+#else
 static int             mtrr      = 0;
+#endif
 
 static int             pmi_setpal = 0;	/* pmi for palette changes ??? */
 static int             ypan       = 0;  /* 0..nothing, 1..ypan, 2..ywrap */





             reply	other threads:[~2003-05-15 14:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-15 14:56 Andi Kleen [this message]
2003-05-15 15:16 ` [PATCH] Use MTRRs by default for vesafb on x86-64 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
2003-05-16 22:58 ` Eric W. Biederman
2003-05-19 10:37   ` Andi Kleen
2003-05-19 12:26     ` Eric W. Biederman
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=20030515145640.GA19152@averell \
    --to=ak@muc.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).