linux-kernel - Re: [PATCH] PPC4xx UART0 (8250) problem

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <46175942.7080707@faust.net.ua>
Date:	Sat, 07 Apr 2007 11:41:38 +0300
From:	Mikhail Zolotaryov <lebon@...st.net.ua>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
CC:	mporter@...nel.crashing.org, linux-serial@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] PPC4xx UART0 (8250) problem

Benjamin Herrenschmidt wrote: 
> 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 :-)

First, thanks for response.

Ok, I see IRQ0 mapping to virtual number is good solution but I know the
problem from the times of 2.4 kernel. It was very surprising while moving to
2.6 kernel - serial driver was changed, but we have the same problem there.

Maybe it's good idea to create unofficial ppc linux branch repository
(or it already exists ?) where we can put patches that work (as above) but
not in pretty good way linux community expects.
-
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/