From: Boszormenyi Zoltan <zboszor@externet.hu>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Cyrix ARR problem in split MTRR code
Date: Wed, 11 Jun 2003 12:11:17 +0200 [thread overview]
Message-ID: <3EE70045.8000609@externet.hu> (raw)
[-- Attachment #1: Type: text/plain, Size: 363 bytes --]
Hi,
I noticed a problem in the split MTRR code that is special casing
ARR #3 on Cyrix 6x86(MX) / MII CPUs. I wrote the code for the
original (monolithic) mtrr.c, but I don't have my old Cyrix 6x86MX
mainboard anymore. The problem is obvious though, one liner fix is
attached. Patrick Mochel should have been more careful. :-)
Best regards,
Zoltán Böszörményi
[-- Attachment #2: mtrr.diff --]
[-- Type: text/plain, Size: 387 bytes --]
--- arch/i386/kernel/cpu/mtrr/main.c.old 2003-06-11 11:09:43.000000000 +0200
+++ arch/i386/kernel/cpu/mtrr/main.c 2003-06-11 12:03:48.000000000 +0200
@@ -64,7 +64,7 @@
static void set_mtrr(unsigned int reg, unsigned long base,
unsigned long size, mtrr_type type);
-static unsigned int arr3_protected;
+extern int arr3_protected;
void set_mtrr_ops(struct mtrr_ops * ops)
{
reply other threads:[~2003-06-11 9:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3EE70045.8000609@externet.hu \
--to=zboszor@externet.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).