From: Andrew de Quincey <adq_dvb@lidskialf.net>
To: Chris Wright <chrisw@osdl.org>, "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
acpi-devel@lists.sourceforge.net,
linux-acpi <linux-acpi@intel.com>
Subject: Re: [ACPI] Re: Fixing USB interrupt problems with ACPI enabled
Date: Thu, 4 Sep 2003 03:15:09 +0100 [thread overview]
Message-ID: <200309040315.09955.adq_dvb@lidskialf.net> (raw)
In-Reply-To: <20030903153746.A19323@osdlab.pdx.osdl.net>
On Wednesday 03 September 2003 23:37, Chris Wright wrote:
> * Nakajima, Jun (jun.nakajima@intel.com) wrote:
> > Doing this for Len, who is on vacation. We would like to thank the
> > people who provided debugging info such as acpidmp, dmidecode, and
> > demsg. This is one of our findings, and we believe this would fix some
> > interrupt problems (with USB, for example) with ACPI enabled, especially
> > when the dmesg reads like:
> >
> > ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 0
> > ACPI: PCI Interrupt Link [ALKB] enabled at IRQ 0
> > ACPI: PCI Interrupt Link [ALKC] enabled at IRQ 0
> > ACPI: PCI Interrupt Link [ALKD] enabled at IRQ 0
> >
> > Basically we assumed that _CRS returned the one we set with _SRS, when
> > setting up a PCI interrupt link device, but that's not the case with
> > some AML codes. Some of them always return 0.
> > Attached is a patch against 2.4.23-pre1. It should be easy to apply this
> > to 2.6.
Wow! This is exactly the idea I've just come up with for VIA boards!
prev parent reply other threads:[~2003-09-04 2:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-30 15:47 Nakajima, Jun
2003-09-03 22:37 ` Chris Wright
2003-09-04 2:15 ` Andrew de Quincey [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=200309040315.09955.adq_dvb@lidskialf.net \
--to=adq_dvb@lidskialf.net \
--cc=acpi-devel@lists.sourceforge.net \
--cc=chrisw@osdl.org \
--cc=jun.nakajima@intel.com \
--cc=linux-acpi@intel.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®