From: Levente Kurusa <levex@linux.com>
To: Len Brown <lenb@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Robert Hancock <hancockrwd@gmail.com>
Cc: Aaron Lu <aaron.lu@intel.com>,
ACPI List <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH RESEND] ACPI: Add Toshiba NB100 to Vista _OSI blacklist
Date: Tue, 29 Oct 2013 17:52:56 +0100 [thread overview]
Message-ID: <526FE7E8.80806@linux.com> (raw)
This patch adds Toshiba NB100 to the Vista _OSI blacklist.
The _OSI(Windows 2006) method is bugged on the netbook resulting in messed up
PCI IRQ Routing information. This was observed on a netbook,
whose SATA controller mode was set to Compatibility mode.
The driver would then register itself to IRQ#16, but the device
was in fact issuing interrupts to IRQ#20.
No side-effects were found during testing, everything is
working as it did before.
See thread:
http://marc.info/?t=137862230200001&r=1&w=2
http://www.spinics.net/lists/linux-ide/msg46173.html
Signed-off-by: Levente Kurusa <levex@linux.com>
Reviewed-by: Robert Hancock <hancockrwd@gmail.com>
---
diff --git a/drivers/acpi/blacklist.c b/drivers/acpi/blacklist.c
index cb96296..34d4d1a 100644
--- a/drivers/acpi/blacklist.c
+++ b/drivers/acpi/blacklist.c
@@ -267,6 +267,14 @@ static struct dmi_system_id acpi_osi_dmi_table[] __initdata = {
DMI_MATCH(DMI_PRODUCT_NAME, "Satellite P305D"),
},
},
+ {
+ .callback = dmi_disable_osi_vista,
+ .ident = "Toshiba NB100",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "TOSHIBA"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "NB100"),
+ },
+ },
/*
* BIOS invocation of _OSI(Linux) is almost always a BIOS bug.
next reply other threads:[~2013-10-29 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 16:52 Levente Kurusa [this message]
2013-10-29 22:44 ` [PATCH RESEND] ACPI: Add Toshiba NB100 to Vista _OSI blacklist Rafael J. Wysocki
2013-10-30 6:11 ` Levente Kurusa
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=526FE7E8.80806@linux.com \
--to=levex@linux.com \
--cc=aaron.lu@intel.com \
--cc=hancockrwd@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).