From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] serial: Use real irq on UART0 (IRQ = 0) on PPC4xx systems
Date: Mon, 20 Nov 2006 13:04:56 +0000 [thread overview]
Message-ID: <20061120130455.GB22330@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20061120121015.2fb667d0@localhost.localdomain>
On Mon, Nov 20, 2006 at 12:10:15PM +0000, Alan wrote:
> On Mon, 20 Nov 2006 12:54:32 +0100 (MET)
> Stefan Roese <ml@stefan-roese.de> wrote:
> > Let's see, if I got this right. You mean that on such a platform, where 0 is a
> > valid physical IRQ, we should assign another value as virtual IRQ number (not
> > 0 and not -1 of course). And then the platform "pic" implementation should
> > take care of the remapping of these virtual IRQ numbers to the physical
> > numbers.
> >
> > Correct?
>
> Absolutely correct in all the detail.
Since IRQ0 is not valid, can we arrange for the generic interrupt
infrastructure to always fail it's allocation, and then remove the
utterly unused bloatful irq_desc[0] ?
Didn't think so since x86 folk would scream. Wait a moment, x86 can
map IRQ0 to some other number for the timer interrupt, just like
other architectures are being forced to map their UART interrupts.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-11-20 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 11:00 [PATCH] serial: Use real irq on UART0 (IRQ = 0) on PPC4xx systems Stefan Roese
2006-11-20 11:24 ` Peter Korsgaard
2006-11-20 11:42 ` Alan
2006-11-20 11:54 ` Stefan Roese
2006-11-20 12:10 ` Alan
2006-11-20 13:04 ` Russell King [this message]
2006-11-20 21:21 ` Guennadi Liakhovetski
2006-11-20 13:28 ` Sergei Shtylyov
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=20061120130455.GB22330@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).