From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: johncavan@home.com (John Cavan)
Cc: VANDROVE@vc.cvut.cz (Petr Vandrovec),
pauly@enteract.com ( Paul C. Nendick),
linux-kernel@vger.kernel.org
Subject: Re: 2.2.16 SMP: mtrr errors
Date: Tue, 12 Dec 2000 21:23:30 +0000 (GMT) [thread overview]
Message-ID: <E145wtZ-0001pn-00@the-village.bc.nu> (raw)
In-Reply-To: <3A3693A8.E0BA83B7@home.com> from "John Cavan" at Dec 12, 2000 04:07:52 PM
> Petr, the Matrox card splits the memory between the two video screens
> when running in a multi-head configuration and "pretends" that it is two
> distinct cards. Thus, a 32 mb card will register an mtrr for 24mb and
> for 8mb seperately when in this mode.
That is a driver bug. The intel processors only support MTRR's on certain
power boundaries/sizes. The fall through is intended.
> to fall through, but is this correct? I've inserted a break at the end
> of the Intel switch before and have not had problems, but I left it out
Lucky
> in the latest couple of kernels because of all the mtrr work being done,
> waiting to see if there was resolution.
The Matrox driver needs to register a single 32Mb MTRR
-
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-12 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-12 21:43 Petr Vandrovec
2000-12-12 21:07 ` John Cavan
2000-12-12 21:23 ` Alan Cox [this message]
2000-12-11 21:58 ` Paul C. Nendick
2000-12-13 2:07 ` David Wragg
2000-12-12 21:36 ` John Cavan
2000-12-13 10:55 ` Jamie Lokier
-- strict thread matches above, loose matches on Subject: below --
2000-12-12 22:13 Petr Vandrovec
2000-12-13 7:33 ` Boszormenyi Zoltan
2000-12-11 20:00 Paul C. Nendick
[not found] ` <Pine.LNX.4.10.10012121511190.28197-100000@coffee.psychology.mcmaster.ca>
2000-12-11 20:23 ` Paul C. Nendick
2000-12-12 20:19 ` John Cavan
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=E145wtZ-0001pn-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=VANDROVE@vc.cvut.cz \
--cc=johncavan@home.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pauly@enteract.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
all inboxes | Powered by JetHome®