From: Juan Quintela <quintela@trasno.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ladislav Michl <ladis@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH] kill prom_printf
Date: Tue, 17 Jun 2003 14:24:41 +0200 [thread overview]
Message-ID: <86d6hcriwm.fsf@trasno.mitica> (raw)
In-Reply-To: <Pine.GSO.3.96.1030617141524.22214C-100000@delta.ds2.pg.gda.pl> (Maciej W. Rozycki's message of "Tue, 17 Jun 2003 14:16:12 +0200 (MET DST)")
>>>>> "maciej" == Maciej W Rozycki <macro@ds2.pg.gda.pl> writes:
maciej> 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.
maciej> So you need to explicitly configure it? That's very bad.
You bet:
- you force everybody to use early_printk (you only want it for
debugging).
- you configure early_printk for everybody (never have to configure
it).
You can't have the cake and eat it :(
Why do you ever will want not to use early_printk?
when you are using a console that is not the prom console (why do you
want to do that on MIPS is a misterios to me), but for other
archs/machines it make sense:
think on a machine that you now it boots to use a network console.
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2003-06-17 12:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 14:33 [PATCH] kill prom_printf Ladislav Michl
2003-06-16 15:19 ` Maciej W. Rozycki
2003-06-16 23:31 ` Juan Quintela
2003-06-17 7:53 ` Ladislav Michl
2003-06-17 12:14 ` Maciej W. Rozycki
2003-06-17 12:45 ` Ladislav Michl
2003-06-17 14:17 ` Maciej W. Rozycki
2003-06-17 14:38 ` Geert Uytterhoeven
2003-06-17 14:49 ` Maciej W. Rozycki
2003-06-17 15:12 ` Geert Uytterhoeven
2003-06-17 16:05 ` Maciej W. Rozycki
2003-06-18 11:52 ` Maciej W. Rozycki
2003-06-17 11:47 ` Maciej W. Rozycki
2003-06-17 11:52 ` Ladislav Michl
2003-06-17 12:16 ` Maciej W. Rozycki
2003-06-17 12:18 ` Ladislav Michl
2003-06-17 12:32 ` Jan-Benedict Glaw
2003-06-17 12:43 ` Jan-Benedict Glaw
2003-06-17 13:57 ` Maciej W. Rozycki
2003-06-17 13:42 ` Maciej W. Rozycki
2003-06-17 12:24 ` Juan Quintela [this message]
2003-06-17 13:44 ` Maciej W. Rozycki
2003-06-17 15:03 ` Juan Quintela
2003-06-17 15:13 ` Geert Uytterhoeven
2003-06-17 15:26 ` Juan Quintela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86d6hcriwm.fsf@trasno.mitica \
--to=quintela@trasno.org \
--cc=ladis@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox