From: Andi Kleen <ak@muc.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Dave Jones <davej@codemonkey.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: Sun, 18 May 2003 07:39:35 +0200 [thread overview]
Message-ID: <20030518053935.GA4112@averell> (raw)
In-Reply-To: <1053118296.5599.27.camel@dhcp22.swansea.linux.org.uk>
On Fri, May 16, 2003 at 10:51:36PM +0200, Alan Cox wrote:
> On Iau, 2003-05-15 at 16:16, Dave Jones wrote:
> > There are PCI ET4000's too. Though if we can get the PCI IDs for those,
> > we can work around them with a quirk. I have one *somewhere*, but it'll
> > take me a while to dig it out.
>
> Some older SiS cards have problems too. I have a 6326 that doesn't work
> with sisfb (too old) and vesafb with mtrr fails.
Can you provide PCI info for them to add a quirk ?
-Andi
next prev parent reply other threads:[~2003-05-18 5:26 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 [this message]
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
-- 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=20030518053935.GA4112@averell \
--to=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@codemonkey.org.uk \
--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.