| 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
| ||
|
Message-Id: <1175922756.7407.46.camel@localhost.localdomain> Date: Sat, 07 Apr 2007 15:12:36 +1000 From: Benjamin Herrenschmidt <benh@...nel.crashing.org> To: Mikhail Zolotaryov <lebon@...st.net.ua> Cc: mporter@...nel.crashing.org, linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] PPC4xx UART0 (8250) problem On Sat, 2007-04-07 at 07:21 +0300, Mikhail Zolotaryov wrote: > On PPC4xx embedded we often have UART0 on IRQ0 but 8250 UART driver > uses IRQ0 as "no irq" hack. It's suggested that platforms with UART > on IRQ0 will redefine is_real_interrupt(irq) macro but 8250 code > anyway overrides that. As the result, serial line on UART0 works > on polling-way and we have character loss on high baud rates. > > In patch I added check if UART0 is on IRQ0, if so we define > is_real_interrupt macro to be 1 (true). Also, check if > is_real_interrupt macro is already defined added to 8250 UART > driver. This is an old problem. The proper fix is already implemented for arch/powerpc and consist of having virtual irq numbers (which helps for many other things anyway). Support for 4xx platforms in arch/powerpc is starting to get in, pop on linuxppc-dev@...abs.org where the patches are being posted and you are welcome to give a hand porting more platforms over :-) Ben. - 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/
Powered by blists - more mailing lists