linux-mips
[Top] [All Lists]

Re: [PATCH] kill prom_printf

To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Subject: Re: [PATCH] kill prom_printf
From: Ladislav Michl <ladis@linux-mips.org>
Date: Tue, 17 Jun 2003 13:18:59 +0100
Cc: Juan Quintela <quintela@trasno.org>, linux-mips@linux-mips.org
In-reply-to: <Pine.GSO.3.96.1030617141524.22214C-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Tue, Jun 17, 2003 at 02:16:12PM +0200
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20030617125216.E27590@ftp.linux-mips.org> <Pine.GSO.3.96.1030617141524.22214C-100000@delta.ds2.pg.gda.pl>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.2.5.1i
On Tue, Jun 17, 2003 at 02:16:12PM +0200, Maciej W. Rozycki wrote:
> On Tue, 17 Jun 2003, Ladislav Michl wrote:
> 
> > >  Well, I would see early_printk() as advantageous if it was also capable
> > > to leave messages in the kernel ring buffer for dmesg or klogd to fetch. 
> > 
> > Ah, we probably don't understand each other. I should type EARLY_PRINTK
> > instead of early_printk (sorry for my lazyness, I'm usually typing in
> > lowercase). CONFIG_EARLY_PRINTK enables early console, you are supposed to
> > use printk everywhere and that way you achieve such functionality.
> 
>  So you need to explicitly configure it?  That's very bad.

I think we can leave it enabled by default, since it doesn't hurt too much.
Kernel cmdline argument could control usage of early console.

        ladis

<Prev in Thread] Current Thread [Next in Thread>