From: Li Shaohua <shaohua.li@intel.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Grzegorz Kulewski <kangur@polcom.net>,
Andrew Morton <akpm@osdl.org>,
ACPI List <acpi-devel@lists.sourceforge.net>,
lkml <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>
Subject: Re: [ACPI] Re: Fw: Anybody? 2.6.11 (stable and -rc) ACPI breaks USB
Date: Fri, 18 Mar 2005 09:09:10 +0800 [thread overview]
Message-ID: <1111108150.22239.6.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <1111082914.11380.30.camel@eeyore>
On Fri, 2005-03-18 at 02:08, Bjorn Helgaas wrote:
> On Thu, 2005-03-17 at 09:33 +0800, Li Shaohua wrote:
> > The comments in previous quirk said it's required only in PIC mode.
> ...
> > I feel we concerned too much. Changing the interrupt line isn't harmful,
> > right? Linux actually ignored interrupt line. Maybe just a
> > PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID, quirk_via_irq) is
> > sufficient.
>
> I think it's good to limit the scope of the quirk as much as
> possible because that makes it easier to do future restructuring,
> such as device-specific interrupt routers.
>
> The comment (before quirk_via_acpi(), nowhere near quirk_via_irqpic())
> says *on-chip devices* have this unusual behavior when the interrupt
> line is written. That makes sense to me.
>
> Writing the interrupt line on random plug-in Via PCI devices does
> not make sense to me, because for that to have any effect, an
> upstream bridge would have to be snooping the traffic going through
> it. That doesn't sound plausible to me.
>
> What about this:
Hmm, this looks like previous solution. We removed the specific via
quirk is because we don't know how many devices have such issue. Every
time we encounter an IRQ issue in a VIA PCI device, we will suspect it
requires quirk and keep try. This is a big overhead.
Thanks,
Shaohua
next prev parent reply other threads:[~2005-03-18 1:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050304234622.63e8a335.akpm@osdl.org>
2005-03-10 23:08 ` Grzegorz Kulewski
2005-03-11 16:48 ` [ACPI] " Bjorn Helgaas
2005-03-11 19:36 ` Grzegorz Kulewski
2005-03-11 20:56 ` Bjorn Helgaas
2005-03-11 21:47 ` Grzegorz Kulewski
2005-03-11 22:29 ` Bjorn Helgaas
2005-03-12 0:13 ` Grzegorz Kulewski
2005-03-13 15:14 ` Grzegorz Kulewski
2005-03-15 19:35 ` Bjorn Helgaas
2005-03-15 23:02 ` Zwane Mwaikambo
2005-03-16 16:10 ` Bjorn Helgaas
2005-03-17 1:33 ` Li Shaohua
2005-03-17 18:08 ` Bjorn Helgaas
2005-03-18 1:09 ` Li Shaohua [this message]
2005-03-18 18:07 ` Bjorn Helgaas
2005-03-21 16:33 ` Bjorn Helgaas
2005-03-21 23:33 ` Grzegorz Kulewski
2005-03-22 20:57 ` Bjorn Helgaas
2005-03-23 0:54 ` Li Shaohua
2005-03-23 3:57 ` Bjorn Helgaas
2005-03-23 18:40 ` Len Brown
2005-03-24 18:24 ` Bjorn Helgaas
2005-03-25 19:07 ` Len Brown
2005-03-14 9:30 Li, Shaohua
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=1111108150.22239.6.camel@sli10-desk.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=kangur@polcom.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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®