From: Robert Hancock <hancockrwd@gmail.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: lenb@kernel.org, linux-pci@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
jirislaby@gmail.com, Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH 1/1] ACPI: pci_irq, add PRT_ quirk for IBM Bartolo
Date: Sun, 27 Jun 2010 18:14:29 -0600 [thread overview]
Message-ID: <4C27E965.80508@gmail.com> (raw)
In-Reply-To: <1277673679-21458-1-git-send-email-jslaby@suse.cz>
On 06/27/2010 03:21 PM, Jiri Slaby wrote:
> On IBM Bartolo machines, cards in 00:09.0 are defunct (if use
> interrupts). DSDT says that this slot (with function 0, i.e. pin A) is
> routed to \_SB_.PCI0.PIB_.LNKB. But it's not, it's wired to LNKC, so
> interrupts are misrouted. Add a quirk for this to workaround the
> issue.
That seems a rather serious DSDT flaw. Do devices in that slot work in
Windows?
>
> This error was reported in suse bugzilla at:
> https://bugzilla.novell.com/show_bug.cgi?id=595683
Apparently that bugzilla requires a login to even view the bug, seems
bizarre to me..
>
> Signed-off-by: Jiri Slaby<jslaby@suse.cz>
> Cc: Len Brown<lenb@kernel.org>
> Cc: Jesse Barnes<jbarnes@virtuousgeek.org>
> ---
> drivers/acpi/pci_irq.c | 15 +++++++++++++++
> 1 files changed, 15 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/acpi/pci_irq.c b/drivers/acpi/pci_irq.c
> index e4804fb..8e054a4 100644
> --- a/drivers/acpi/pci_irq.c
> +++ b/drivers/acpi/pci_irq.c
> @@ -125,6 +125,18 @@ static const struct dmi_system_id hp_t5710[] = {
> { }
> };
>
> +/* https://bugzilla.novell.com/show_bug.cgi?id=595683 */
> +static const struct dmi_system_id ibm_bartolo[] = {
> + {
> + .ident = "IBM Bartolo",
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "IBM CORPORATION"),
> + DMI_MATCH(DMI_PRODUCT_NAME, "4810320"),
> + },
> + },
> + { }
> +};
> +
> struct prt_quirk {
> const struct dmi_system_id *system;
> unsigned int segment;
> @@ -152,6 +164,9 @@ static const struct prt_quirk prt_quirks[] = {
> { hp_t5710, 0, 0, 1, PCI_INTX_PIN('A'),
> "\\_SB_.PCI0.LNK1",
> "\\_SB_.PCI0.LNK3"},
> + { ibm_bartolo, 0, 0, 9, PCI_INTX_PIN('A'),
> + "\\_SB_.PCI0.PIB_.LNKB",
> + "\\_SB_.PCI0.PIB_.LNKC"},
> };
>
> static void do_prt_fixups(struct acpi_prt_entry *entry,
next prev parent reply other threads:[~2010-06-28 0:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-27 21:21 [PATCH 1/1] ACPI: pci_irq, add PRT_ quirk for IBM Bartolo Jiri Slaby
2010-06-28 0:14 ` Robert Hancock [this message]
2010-06-28 6:13 ` Jiri Slaby
2010-06-28 17:14 ` Matthew Garrett
2010-06-28 20:12 ` Jiri Slaby
2010-06-28 20:48 ` Matthew Garrett
2010-06-28 21:37 ` Robert Hancock
2010-06-29 18:40 ` Jiri Slaby
2010-06-29 23:23 ` Robert Hancock
2010-06-30 9:20 ` Jiri Slaby
2010-06-30 9:40 ` Jiri Slaby
2010-07-06 0:28 ` Robert Hancock
2010-07-19 16:29 ` Jiri Slaby
2010-07-19 19:19 ` Robert Hancock
2010-07-20 9:29 ` Jiri Slaby
2010-08-24 8:11 ` Jiri Slaby
2010-08-24 23:25 ` Robert Hancock
2010-08-30 7:36 ` Jiri Slaby
2010-09-07 11:02 ` Jiri Slaby
2010-09-07 14:40 ` Robert Hancock
2010-09-08 15:05 ` Jiri Slaby
2011-04-12 8:48 ` [RFC " Jiri Slaby
2011-04-12 8:58 ` Jiri Slaby
2011-04-12 15:56 ` Jesse Barnes
2011-04-12 15:59 ` Matthew Garrett
2011-04-14 9:40 ` Jiri Slaby
2011-05-13 7:18 ` Jiri Slaby
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=4C27E965.80508@gmail.com \
--to=hancockrwd@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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).