From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jim Paris <jim@jtan.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PCI IRQ problems -- update
Date: Sat, 11 Dec 2004 16:45:57 +0000 [thread overview]
Message-ID: <1102783555.7267.37.camel@localhost.localdomain> (raw)
In-Reply-To: <20041211173538.GA21216@jim.sh>
On Sad, 2004-12-11 at 17:35, Jim Paris wrote:
> In short, all PCI IRQs are routed via ACPI to PIC IRQ 9. When the
> PIIX IDE device is enabled, it pulls on that interrupt until it gets
> disabled ("nobody cared"). ide0 then continues to work on IRQ 14, but
> all other devices are broken since IRQ 9 is disabled.
The PIIX should be in legacy mode by default in which case it would be
on
IRQ 14/15 only. Can you post boot messages ?
> I'm not sure how to get to the root cause of the problem, though. For
> starters: where _should_ the INTA of the IDE card go, if anywhere? If
Quite possibly nowhere. IDE controllers have two modes one in which they
are normal PCI devices (and use INTA) and one in which they are "legacy"
compatible and use IRQ14/15 directly so they work with pre-PCI operating
systems.
> my laptop's IDE is routed to and pulling on IRQ 9, how can it still be
> functioning on IRQ 14? Or, if the routing doesn't matter, is there
> anything I can do to prevent it from pulling on 9?
In legacy mode (the mode I would expect at boot) it shouldn't be using
INTA at all.
next prev parent reply other threads:[~2004-12-11 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 17:35 PCI IRQ problems -- update Jim Paris
2004-12-11 16:45 ` Alan Cox [this message]
2004-12-11 20:02 ` Jim Paris
2004-12-12 11:32 ` Alan Cox
2004-12-11 20:23 ` Jim Paris
2004-12-11 22:03 ` [PATCH] " Jim Paris
2004-12-12 11:43 ` Alan Cox
2004-12-12 11:29 ` Alan Cox
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=1102783555.7267.37.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jim@jtan.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