Subject: Re: MTRR vesafb and wrong X performance
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>
In-Reply-To: <20041129154006.GB3898@redhat.com>
References: <1101338139.1780.9.camel@PC3.dom.pl>
	 <20041124171805.0586a5a1.akpm@osdl.org>
	 <1101419803.1764.23.camel@PC3.dom.pl> <87is7ogb93.fsf@bytesex.org>
	 <20041129154006.GB3898@redhat.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-Id: <1101745468.20223.30.camel@localhost.localdomain>
Mime-Version: 1.0
Date: Mon, 29 Nov 2004 16:24:30 +0000
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 699
Lines: 16

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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/