From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
Andrew Morton <akpm@osdl.org>,
Andreas Mohr <andi@rhlx01.fht-esslingen.de>,
florin@iucha.net, linux-kernel@vger.kernel.org,
linux@dominikbrodowski.net
Subject: Re: pcmcia oops on 2.6.17-rc[12]
Date: Tue, 16 May 2006 02:18:23 +0100 [thread overview]
Message-ID: <1147742303.31247.2.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0605151715290.3866@g5.osdl.org>
On Llu, 2006-05-15 at 17:18 -0700, Linus Torvalds wrote:
> The irq auto-detection should work with shared interrupts, but yes, it
> won't _detect_ them if they are already in use (but it's ok with them
> becoming shared later).
>
> That said, true ISA cards obviously won't ever have a shared irq, in any
> normal circumstances.
It really isn't that simple. ISAPnP and later ISA cards often allowed
the IRQ to be configured at runtime. Drivers doing this depend upon the
request_irq failing to decide which interrupt line to assign. The
resource management side of exclusive IRQ allocation is for better or
worse deeply embedded in the current interrupt design.
Alan
next prev parent reply other threads:[~2006-05-16 1:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 19:22 pcmcia oops on 2.6.17-rc[12] Florin Iucha
2006-04-23 22:02 ` Andrew Morton
2006-04-23 22:15 ` Randy.Dunlap
2006-04-24 0:46 ` Florin Iucha
2006-05-08 14:56 ` Andreas Mohr
2006-05-08 15:43 ` Andrew Morton
2006-05-08 16:34 ` Russell King
2006-05-15 22:07 ` Alan Cox
2006-05-15 22:00 ` Russell King
2006-05-18 11:10 ` Russell King
2006-05-15 22:02 ` Linus Torvalds
2006-05-15 23:00 ` Alan Cox
2006-05-15 23:37 ` Linus Torvalds
2006-05-15 23:52 ` Linus Torvalds
2006-05-16 0:17 ` Alan Cox
2006-05-16 0:18 ` Linus Torvalds
2006-05-16 1:18 ` Alan Cox [this message]
2006-05-16 15:16 ` Alan Cox
2006-05-22 11:50 ` Rogier Wolff
2006-05-22 12:10 ` Alan Cox
2006-05-22 21:27 ` Rogier Wolff
2006-05-22 22:38 ` Alan Cox
2006-06-02 19:09 ` Russell King
2006-05-22 15:06 ` Linus Torvalds
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=1147742303.31247.2.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=florin@iucha.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=torvalds@osdl.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