| To: | Geert Uytterhoeven <geert@linux-m68k.org> |
|---|---|
| Subject: | Re: [PATCH] kill prom_printf |
| From: | "Maciej W. Rozycki" <macro@ds2.pg.gda.pl> |
| Date: | Tue, 17 Jun 2003 16:49:17 +0200 (MET DST) |
| Cc: | Ladislav Michl <ladis@linux-mips.org>, Juan Quintela <quintela@trasno.org>, Linux/MIPS Development <linux-mips@linux-mips.org> |
| In-reply-to: | <Pine.GSO.4.21.0306171637390.17930-100000@vervain.sonytel.be> |
| Organization: | Technical University of Gdansk |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| Sender: | linux-mips-bounce@linux-mips.org |
On Tue, 17 Jun 2003, Geert Uytterhoeven wrote:
> > Hmm, calling the firmware for each character separately will certainly be
> > terribly slow, though it may be negligible as normally few messages will
> > be output this way. And since the call to prom_printf() is so cheap for
> > the DECstation, I'm going to retain the function for real low-level
> > debugging, whether otherwise used or not.
>
> kernel/printk.c doesn't call the low-level output routine for each character
> separately, but passes complete strings of characters.
So I can just call prom_printf("%s", string), right? This would solve
this shortcoming.
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] kill prom_printf, Geert Uytterhoeven |
|---|---|
| Next by Date: | Re: [PATCH] kill prom_printf, Juan Quintela |
| Previous by Thread: | Re: [PATCH] kill prom_printf, Geert Uytterhoeven |
| Next by Thread: | Re: [PATCH] kill prom_printf, Geert Uytterhoeven |
| Indexes: | [Date] [Thread] [Top] [All Lists] |