From: tip-bot for Simon Kagstrom <simon.kagstrom@netinsight.net>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
simon.kagstrom@netinsight.net, tglx@linutronix.de
Subject: [tip:x86/urgent] x86: Add Phoenix/MSC BIOSes to lowmem corruption list
Date: Fri, 6 Nov 2009 22:51:47 GMT [thread overview]
Message-ID: <tip-f1b291d4c47440cbfc1a478e88800e2742d60a80@git.kernel.org> (raw)
In-Reply-To: <20091106154404.002648d9@marrow.netinsight.se>
Commit-ID: f1b291d4c47440cbfc1a478e88800e2742d60a80
Gitweb: http://git.kernel.org/tip/f1b291d4c47440cbfc1a478e88800e2742d60a80
Author: Simon Kagstrom <simon.kagstrom@netinsight.net>
AuthorDate: Fri, 6 Nov 2009 15:44:04 +0100
Committer: H. Peter Anvin <hpa@zytor.com>
CommitDate: Fri, 6 Nov 2009 14:49:39 -0800
x86: Add Phoenix/MSC BIOSes to lowmem corruption list
We have a board with a Phoenix/MSC BIOS which also corrupts the low
64KB of RAM, so add an entry to the table.
Signed-off-by: Simon Kagstrom <simon.kagstrom@netinsight.net>
LKML-Reference: <20091106154404.002648d9@marrow.netinsight.se>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
---
arch/x86/kernel/setup.c | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index e09f0e2..2a34f9c 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -660,6 +660,13 @@ static struct dmi_system_id __initdata bad_bios_dmi_table[] = {
},
},
{
+ .callback = dmi_low_memory_corruption,
+ .ident = "Phoenix/MSC BIOS",
+ .matches = {
+ DMI_MATCH(DMI_BIOS_VENDOR, "Phoenix/MSC"),
+ },
+ },
+ {
/*
* AMI BIOS with low memory corruption was found on Intel DG45ID board.
* It hase different DMI_BIOS_VENDOR = "Intel Corp.", for now we will
prev parent reply other threads:[~2009-11-06 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 14:44 [PATCH] x86: Workaround low-memory corruption by Phoenix/MSC BIOSes Simon Kagstrom
2009-11-06 22:51 ` tip-bot for Simon Kagstrom [this message]
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=tip-f1b291d4c47440cbfc1a478e88800e2742d60a80@git.kernel.org \
--to=simon.kagstrom@netinsight.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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®