From: Ralf Baechle <ralf@linux-mips.org>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: Early printk recent changes.
Date: Tue, 27 Mar 2007 18:57:33 +0100 [thread overview]
Message-ID: <20070327175733.GA26496@linux-mips.org> (raw)
In-Reply-To: <cda58cb80703270906j74d6bf6fsb6259f24427faff5@mail.gmail.com>
On Tue, Mar 27, 2007 at 06:06:10PM +0200, Franck Bui-Huu wrote:
> > In this case I gather this was a bulk change and some platforms have
> >benefited and the DECstation has lost. You seem to have problems as well.
> >These issues can be dealt with somehow and they do not mean the change was
> >bad as a whole.
>
> I think that's the reason why I started this thread: To see if this
> change is good and really woth...
>
> Making a new file 'early_printk' to gather 3 tiny functions. In the
> other way we lose the possibilty to register the console earlier, and
> we need to make some hacks to configure the console if it needs to be.
>
> I understand that such change is needed by x86 arch but for mips I'm
> skeptical.
I decieded to rush the whole early printk thing since we had several
copies of early printk in the MIPS code already. Add plenty of
variations of prom_putchar / prom_printf. We certainly now have less
loose ends in the code than before. And since we're always in the trade
of better mouse trap I certainly won't object if submits has one :-)
Ralf
next prev parent reply other threads:[~2007-03-27 17:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 14:16 Early printk recent changes Franck Bui-Huu
2007-03-27 14:31 ` Maciej W. Rozycki
2007-03-27 15:03 ` Franck Bui-Huu
2007-03-27 15:38 ` Maciej W. Rozycki
2007-03-27 16:06 ` Franck Bui-Huu
2007-03-27 17:57 ` Ralf Baechle [this message]
2007-03-28 6:51 ` [PATCH 1/2] early_printk: use init section Franck Bui-Huu
2007-03-28 6:51 ` [PATCH 2/2] early_printk: allow the early console to run earlier Franck Bui-Huu
2007-03-28 7:37 ` Early printk recent changes Franck Bui-Huu
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=20070327175733.GA26496@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=vagabon.xyz@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.