From: Ladislav Michl <ladis@linux-mips.org>
To: Juan Quintela <quintela@trasno.org>
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>, linux-mips@linux-mips.org
Subject: Re: [PATCH] kill prom_printf
Date: Tue, 17 Jun 2003 08:53:46 +0100 [thread overview]
Message-ID: <20030617085346.A27590@ftp.linux-mips.org> (raw)
In-Reply-To: <867k7lsiq1.fsf@trasno.mitica>; from quintela@trasno.org on Tue, Jun 17, 2003 at 01:31:02AM +0200
On Tue, Jun 17, 2003 at 01:31:02AM +0200, Juan Quintela wrote:
> >>>>> "maciej" == Maciej W Rozycki <macro@ds2.pg.gda.pl> writes:
[snip]
> maciej> Hmm, strange idea -- I guess that originates from systems that have no
> maciej> suitable firmware to perform such an operation at the console. Currently
> maciej> only x86_64 implements early_printk() -- if we have an implementation for
> maciej> MIPS, we may consider removing the alternative. Also prom_printf() comes
> maciej> almost for free and works very early and as I see in the x86_64 version
> maciej> early_printk() requires initialization of a console driver, which may be
> maciej> unfortunate if debugging a problem within the driver.
>
> There is at least one implementation for x86 that uses the VGA
> directly (as the BIOS left it), getting it very soon.
>
> But you are right, PC's speciality is not to have a nice console.
> Anyways, you can use early_printk() in MIPS. You only need to put the
> setup of the early console sooner, as for you the setup is basically a NOP.
(I'm only implementing it and I don't care how good idea it is :-) Anyway
I still think that firmware should be used directly to print message before
kernel halts in situations like arch/mips/arc/init.c at line 30)
Maciej, i'll try to make some conclusion from what I was told (and Juan is
welcome to correct me if I missunderstood something)
Idea is to have only one way for printing kernel messages. In case of Indy,
O2 and SNI RM200 "arc" console will do it. Here you can find where should
be early console initialized:
http://marc.theaimsgroup.com/?l=linux-kernel&m=105519188505235&w=2
As Juan pointed out setup for such console is actually a nop and one is
supposed to enable this feature only when debugging kernel. DEC prom console
however needs some setup to determine REX entry points. early console is
currently used on sh, alpha, x86_64 and ia64 architectures. Btw, see comment
at the top of arch/sparc/prom/printf.c
Regards, ladis
next prev parent reply other threads:[~2003-06-17 7:53 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 [this message]
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
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=20030617085346.A27590@ftp.linux-mips.org \
--to=ladis@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@ds2.pg.gda.pl \
--cc=quintela@trasno.org \
/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