[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440705170954k4863d95ah16e1068e47983822@mail.gmail.com>
Date: Thu, 17 May 2007 09:54:44 -0700
From: "Yinghai Lu" <yhlu.kernel@...il.com>
To: "Maciej W. Rozycki" <macro@...ux-mips.org>
Cc: "Bjorn Helgaas" <bjorn.helgaas@...com>,
"Gerd Hoffmann" <kraxel@...e.de>, "Andi Kleen" <ak@...e.de>,
akpm@...ux-foundation.org,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"linux kernel mailing list" <linux-kernel@...r.kernel.org>
Subject: Re: [patch] early printk and boot console fixups.
On 5/17/07, Maciej W. Rozycki <macro@...ux-mips.org> wrote:
> On Wed, 16 May 2007, Bjorn Helgaas wrote:
>
> > > Given the generic name of "uart" I am assuming this will work with any
> > > UART driver making use of the serial_core.c core -- am I correct?
> >
> > I knew somebody would ask that eventually :-)
> >
> > Unfortunately, the answer is "no." "console=uart" only works with
> > 8250-compatible devices.
>
> But is it a design limitation or is it just that other UART drivers have
> to be modified to work with this option? My point is if the former, then
> the option should be something like "console=8250" (the right-hand side
> being the name of the driver involved; others may want to add support for
> other drivers). If the latter, then it's fine as is as other UART drivers
> may be wired to this code as a need arises.
>
> Maciej
>
Actually that early_uart is not real early one.
it is called via console_initcall.
for IA64, Bjom is calling that directly in setup_arch.
Please check my patch to make it to be called via early_param, that
will be good to other platform.
also you may extend to support other early_uart.
YH
View attachment "early_uart_early_param.patch" of type "text/x-patch" (5578 bytes)
Powered by blists - more mailing lists