public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dave Jones <davej@redhat.com>
Cc: Gerd Knorr <kraxel@bytesex.org>,
	pawfen@wp.pl, Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: MTRR vesafb and wrong X performance
Date: Mon, 29 Nov 2004 16:24:30 +0000	[thread overview]
Message-ID: <1101745468.20223.30.camel@localhost.localdomain> (raw)
In-Reply-To: <20041129154006.GB3898@redhat.com>

On Llu, 2004-11-29 at 15:40, Dave Jones wrote:
> which is an ugly hack for the above problem imo.
> vesafb:nomtrr also fixes the problem, and leaves X free
> to set things up correctly in my experience.
> 
> If vesafb can't get it right, maybe it shouldn't be
> attempted to do it in the half-assed way it currently does.

The problem is not vesafb its X. If someone would go fix the Xorg code
to handle extending existing maps the problem will go away.


  parent reply	other threads:[~2004-11-29 17:28 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
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 [this message]
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=1101745468.20223.30.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=kraxel@bytesex.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