From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Paul Mackerras <paulus@samba.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Ingo Molnar <mingo@elte.hu>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
Anton Blanchard <anton@samba.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: New consolidate irqs vs . probe_irq_*()
Date: Wed, 20 Oct 2004 13:31:58 +0100 [thread overview]
Message-ID: <20041020133158.B14627@flint.arm.linux.org.uk> (raw)
In-Reply-To: <16758.20925.984734.83651@cargo.ozlabs.ibm.com>; from paulus@samba.org on Wed, Oct 20, 2004 at 09:53:33PM +1000
On Wed, Oct 20, 2004 at 09:53:33PM +1000, Paul Mackerras wrote:
> Russell King writes:
>
> > Remember that PCMCIA effectively has its own IRQ router which requires
> > the PCMCIA code to know which IRQs are physically connected and which
> > aren't. Unfortunately, there's no way to get that information as far
> > as I know except by the published method in the code.
>
> On my powerbook, the pcmcia/cardbus controller has one interrupt,
> which is used both for card status changes and for card functional
> interrupts. It doesn't have an ISA bus and it doesn't have an 8259
> interrupt controller, and interrupts 0-15 aren't anything like what
> they might be on a PC. This is why (as Ben says) there is no point
> probing for interrupts, and why on ppc (or at least on powermacs) the
> probe functions are no-ops.
Correct - and Ben's comments seem to imply that yenta is wrong for doing
so. I'm making the point that it isn't.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
prev parent reply other threads:[~2004-10-20 12:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 7:08 [PATCH] Fix PREEMPT_ACTIVE definition Paul Mackerras
2004-10-20 8:33 ` Ingo Molnar
2004-10-20 8:42 ` New consolidate irqs vs . probe_irq_*() Benjamin Herrenschmidt
2004-10-20 8:48 ` Ingo Molnar
2004-10-20 8:53 ` Benjamin Herrenschmidt
2004-10-20 9:20 ` Ingo Molnar
2004-10-20 10:56 ` Benjamin Herrenschmidt
2004-10-20 9:31 ` Chris Wedgwood
2004-10-20 9:01 ` Russell King
2004-10-20 10:50 ` Benjamin Herrenschmidt
2004-10-20 11:01 ` Russell King
2004-10-20 11:06 ` Benjamin Herrenschmidt
2004-10-20 11:53 ` Paul Mackerras
2004-10-20 12:31 ` Russell King [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=20041020133158.B14627@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--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 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.