linux-kernel - Re: [PATCH] serial: Use real irq on UART0 (IRQ = 0) on PPC4xx systems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 20 Nov 2006 13:04:56 +0000
From:	Russell King <rmk+lkml@....linux.org.uk>
To:	Alan <alan@...rguk.ukuu.org.uk>
Cc:	Stefan Roese <ml@...fan-roese.de>, linux-kernel@...r.kernel.org,
	linuxppc-embedded@...abs.org
Subject: Re: [PATCH] serial: Use real irq on UART0 (IRQ = 0) on PPC4xx systems

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@...fan-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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/