On Tue, 2003-06-17 13:18:59 +0100, Ladislav Michl <firstname.lastname@example.org>
wrote in message <20030617131859.A32079@ftp.linux-mips.org>:
> 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.
If we constantly add (new) kernel arguments, we may at some time face
the problem that the calling PROM/firmware/whatever cannot handle a
command line which is *that* long. IIRC DECstations have a quite limited
prompt length. This hurts for "3/tftp():vmecoff root=/dev/ram
nfsroot=/nfsroot/decxxxx ip=bootp console=ttyS2 console=tty0
I'm just thinking about numerizing all __setup() calls so that you maybe
can use something C99 style like: .15=/dev/ttyS0 (where .15 is the
fiveteenth variable which is "console".
All that needs to be done are some lines at command line parsing and a
small tool/script to extract correct values and their corresponding
Jan-Benedict Glaw email@example.com . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
Description: PGP signature