From: Len Brown <lenb@kernel.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-acpi@vger.kernel.org,
"Pierre Ossman" <drzeus-bugzilla@drzeus.cx>,
"Michael Fu" <michael.fu@intel.com>,
"Martin Kirst" <martin.kirst@s1998.tu-chemnitz.de>,
"Hadmut Danisch" <hadmut@danisch.de>,
"Johann-Nikolaus Andreae" <johann-nikolaus.andreae@nacs.de>,
"Dominik Schäfer" <schaedpq2@gmx.de>,
"Alex Williamson" <alex.williamson@hp.com>,
"Aron Griffis" <aron@hp.com>
Subject: Re: [PATCH] ACPI: add _PRT quirks to work around broken firmware
Date: Wed, 12 Mar 2008 15:50:20 -0400 [thread overview]
Message-ID: <200803121550.21397.lenb@kernel.org> (raw)
In-Reply-To: <200803121155.13321.bjorn.helgaas@hp.com>
On Wednesday 12 March 2008, Bjorn Helgaas wrote:
> On Tuesday 11 March 2008 09:40:04 pm Len Brown wrote:
> > Is it true that simply enabling pci=routeirq on these boxes
> > is an insufficient workaround?
>
> I'm told that pci=routeirq is a sufficient workaround for the
> first two issues, but I verified that it is not sufficient on
> the t5710.
>
> On the t5710, even with pci=routeirq, as soon as we turn on the
> radeon interrupt, it starts generating interrupts on LNK3. Since
> the radeon driver isn't listening there, we eventually turn off
> that IRQ, killing other other devices sharing it as a side-effect.
>
> I don't know why pci=routeirq works on the other two boxes. Maybe
> because of your guess below.
okay, then lets go with the precise workaround you proposed.
thanks,
-Len
> > I suspect the answer is yes, because when pci=routeirq works
> > we may just be lucky -- eg. we happen to assign the real
> > and the fake link to the same IRQ and thus the driver
> > actually registers for the correct IRQ, but by accident.
> >
next prev parent reply other threads:[~2008-03-12 19:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 20:45 [PATCH] ACPI: add _PRT quirks to work around broken firmware Bjorn Helgaas
2008-03-12 3:40 ` Len Brown
2008-03-12 17:55 ` Bjorn Helgaas
2008-03-12 19:50 ` Len Brown [this message]
2008-03-12 22:00 ` Bjorn Helgaas
2008-03-12 22:04 ` Len Brown
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=200803121550.21397.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@hp.com \
--cc=aron@hp.com \
--cc=bjorn.helgaas@hp.com \
--cc=drzeus-bugzilla@drzeus.cx \
--cc=hadmut@danisch.de \
--cc=johann-nikolaus.andreae@nacs.de \
--cc=linux-acpi@vger.kernel.org \
--cc=martin.kirst@s1998.tu-chemnitz.de \
--cc=michael.fu@intel.com \
--cc=schaedpq2@gmx.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