From: Bjorn Helgaas <bhelgaas@google.com>
To: "Malte Schröder" <maltesch@gmx.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Galen Seitz <galens@seitzassoc.com>,
bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 43238] Re: PCI ACPI/IRQ-routing broken on H77 chipset + Ivy Bridge (kernel 3.5-rc7 and earlier)
Date: Mon, 30 Jul 2012 11:12:48 -0600 [thread overview]
Message-ID: <CAErSpo5SCa0NdZUtLpLDma+i6+L7NH7pOFvUzOAD4TougvqMQg@mail.gmail.com> (raw)
In-Reply-To: <50084E8B.3070508@gmx.de>
> I was pointed to https://bugzilla.kernel.org/show_bug.cgi?id=43238.
> I tried the modifications to the DSDT that where proposed there and
> voilŕ, the 3c905c started to work :)
I don't know where to go with this. We do have some _PRT quirks in
drivers/acpi/pci_irq.c, but since Windows 7 works fine without any
quirks, adding a quirk to Linux doesn't seem like the "right" fix.
Lubos, would it be possible for you to collect a Windows system report
using AIDA64? I think there's a free trial version here:
http://www.aida64.com/
Maybe somebody can compare what Windows does with what Linux does and
figure out the difference.
prev parent reply other threads:[~2012-07-30 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 12:49 PCI ACPI/IRQ-routing broken on H77 chipset + Ivy Bridge (kernel 3.5-rc7 and earlier) Malte Schröder
2012-07-15 20:25 ` Rafael J. Wysocki
2012-07-16 16:14 ` Bjorn Helgaas
2012-07-19 18:14 ` Malte Schröder
2012-07-30 17:12 ` Bjorn Helgaas [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=CAErSpo5SCa0NdZUtLpLDma+i6+L7NH7pOFvUzOAD4TougvqMQg@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=galens@seitzassoc.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maltesch@gmx.de \
--cc=rjw@sisk.pl \
--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;
as well as URLs for NNTP newsgroup(s).