From: Jes Sorensen <jes@trained-monkey.org>
To: "Charles Martin" <martinc@ucar.edu>
Cc: <linux-kernel@vger.kernel.org>, <martinc@atd.ucar.edu>
Subject: Re: interrupts across PCI bridge(s) not handled
Date: 04 Nov 2003 04:51:53 -0500 [thread overview]
Message-ID: <yq0vfq0jwau.fsf@trained-monkey.org> (raw)
In-Reply-To: <000001c3a254$043d88c0$c3507580@atdsputnik>
>>>>> "Charles" == Charles Martin <martinc@ucar.edu> writes:
Charles> They are now getting handled properly, i.e. I am receiveing
Charles> interrupts from the boards located in the backplane extender.
Charles> This is with 2.4.22.
Charles> I didn't realize that ACPI is related to interrupt management
Charles> as well as power control. Is there any downside to using
Charles> ACPI?
Yep it does ;-( IA64 relies exclusively on ACPI for irq routing and on
x86 you are seeing more and more hardware that requires it as well,
notably Sony laptops such as the R505 series will not see interrupts
assigned to their cardbus bridge without ACPI interrupt routing.
As for downsides, take a look at the ACPI spec and judge for
yourself. I'll refrain from commenting ;-)
Cheers,
Jes
next prev parent reply other threads:[~2003-11-04 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 16:08 interrupts across PCI bridge(s) not handled Charles Martin
2003-11-03 17:04 ` Linus Torvalds
2003-11-03 19:50 ` Charles Martin
2003-11-03 20:23 ` Linus Torvalds
2003-11-03 20:29 ` Charles Martin
2003-11-03 21:51 ` Linus Torvalds
2003-11-03 21:46 ` Charles Martin
2003-11-04 0:31 ` Linus Torvalds
2003-11-04 9:51 ` Jes Sorensen [this message]
2003-11-04 2:47 ` Zwane Mwaikambo
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=yq0vfq0jwau.fsf@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martinc@atd.ucar.edu \
--cc=martinc@ucar.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.