From: David Wragg <dpw@doc.ic.ac.uk>
To: Steven Walter <srwalter@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.2.18pre25, S3, AMD K6-2, and MTRR....
Date: 11 Dec 2000 10:29:53 +0000 [thread overview]
Message-ID: <y7rn1e38d3y.fsf@sytry.doc.ic.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.21.0012092218280.877-100000@u> <14898.42117.34020.145433@critterling.garfield.home> <y7ru28cdtow.fsf@sytry.doc.ic.ac.uk> <20001210123438.A9659@hapablap.dyn.dhs.org>
In-Reply-To: Steven Walter's message of "Sun, 10 Dec 2000 12:34:38 -0600"
Steven Walter <srwalter@yahoo.com> writes:
> On Sun, Dec 10, 2000 at 06:20:31PM +0000, David Wragg wrote:
> > If I understood why the MTRR driver was doing something on the K6-2,
> > then model-specific differences might make some sense. But currently,
> > I don't see why there would be any difference between "MTRR disabled"
> > and "MTRR enabled, but not used".
>
> If I'm not mistaken, X /does/ touch the MTRR's, which would explain why
> it is X that crashes.
Only in XFree86-4.x (I never distributed my MTRR patches for
XFree86-3.x ;-). Which is why the XFree86 version was one of the
things I wanted to confirm.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-11 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-09 23:05 2.2.18pre25, S3, AMD K6-2, and MTRR Julian Anastasov
2000-12-09 21:30 ` Victor J. Orlikowski
2000-12-10 18:20 ` David Wragg
2000-12-10 18:34 ` Steven Walter
2000-12-11 10:29 ` David Wragg [this message]
2000-12-09 23:48 ` Victor J. Orlikowski
2000-12-10 22:32 ` Julian Anastasov
2000-12-11 0:58 ` Victor J. Orlikowski
2000-12-11 8:57 ` Julian Anastasov
-- strict thread matches above, loose matches on Subject: below --
2000-12-09 15:53 Victor J. Orlikowski
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=y7rn1e38d3y.fsf@sytry.doc.ic.ac.uk \
--to=dpw@doc.ic.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=srwalter@yahoo.com \
/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