From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-os@analogic.com
Cc: aryix <aryix@softhome.net>,
lug-list@lugmen.org.ar, linux-kernel@vger.kernel.org
Subject: Re: dmesg: PCI interrupts are no longer routed automatically.........
Date: Tue, 04 Jan 2005 12:41:18 -0700 [thread overview]
Message-ID: <1104867678.1846.80.camel@eeyore> (raw)
In-Reply-To: <Pine.LNX.4.61.0501041342070.5445@chaos.analogic.com>
On Tue, 2005-01-04 at 13:53 -0500, linux-os wrote:
> I note that pci_enable_device() needs to be executed __before__
> the IRQ is obtained on 2.6.10, otherwise you get the wrong IRQ
> (IRQ10 on this system)B.
Right.
> This doesn't seem to be correct since the IRQ connection was set
> by the BIOS and certainly shouldn't be changed. On this system,
> interrupts that were not shared on 2.4.n and early 2.6.n end
> up being shared... See IRQ18 below.
It's not that we are changing the IRQ, it's just that we now
do the ACPI routing at the time the driver claims the device,
rather than doing all the ACPI routing at boot-time. The
old strategy messed with IRQs that might never be used (which
broke some things), and also didn't work for hot-plug PCI
root bridges.
Back to my original question, do you have a device that
only works when you use "pci=routeirq"? If so, what is
it and what driver does it use?
next prev parent reply other threads:[~2005-01-04 19:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 9:55 dmesg: PCI interrupts are no longer routed automatically aryix
2005-01-04 18:18 ` Bjorn Helgaas
2005-01-04 18:53 ` linux-os
2005-01-04 19:41 ` Bjorn Helgaas [this message]
2005-01-04 19:55 ` linux-os
2005-01-05 9:40 ` David Vrabel
2005-01-05 12:06 ` linux-os
2005-01-05 17:13 ` Bjorn Helgaas
2005-01-05 18:15 ` linux-os
2005-01-10 21:38 ` Bjorn Helgaas
2005-01-10 22:03 ` linux-os
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=1104867678.1846.80.camel@eeyore \
--to=bjorn.helgaas@hp.com \
--cc=aryix@softhome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=lug-list@lugmen.org.ar \
/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).