From: "Måns Rullgård" <mans@mansr.com>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: Joe Perches <joe@perches.com>,
linux-arch <linux-arch@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k <linux-m68k@vger.kernel.org>,
Steven Miao <realmz6@gmail.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips <linux-mips@linux-mips.org>
Subject: Re: rfc: remove early_printk from a few arches? (blackfin, m68k, mips)
Date: Wed, 17 Dec 2014 22:30:16 +0000 [thread overview]
Message-ID: <yw1xk31phptz.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <CAJiQ=7DE1ojVRW6LqZg2LiqTQ0cgDY_a0nMGn=_Rs1mkuEgwoA@mail.gmail.com> (Kevin Cernekee's message of "Wed, 17 Dec 2014 13:30:02 -0800")
Kevin Cernekee <cernekee@gmail.com> writes:
> On Wed, Dec 17, 2014 at 12:58 PM, Joe Perches <joe@perches.com> wrote:
>> It seems like early_printk can be configured into
>> a few architectures but also appear not to be used.
>>
>> $ git grep -w "early_printk"
> [snip]
>> arch/mips/kernel/Makefile:obj-$(CONFIG_EARLY_PRINTK) += early_printk.o
>
> Nowadays I try to use OF_EARLYCON whenever possible, but when that has
> been unavailable, I have used arch/mips/kernel/early_printk.c to get
> console output before the serial driver is initialized. It runs very
> early in the boot sequence and has very few dependencies, which makes
> it useful for board bringup.
EARLY_PRINTK on MIPS is enabled just after prom_init(), well before
OF_EARLYCON is usable. I'd prefer if it stayed that way.
--
Måns Rullgård
mans@mansr.com
next prev parent reply other threads:[~2014-12-17 22:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 20:58 rfc: remove early_printk from a few arches? (blackfin, m68k, mips) Joe Perches
2014-12-17 21:30 ` Kevin Cernekee
2014-12-17 22:30 ` Måns Rullgård [this message]
2014-12-18 23:33 ` Thomas Gleixner
2014-12-19 1:14 ` Joe Perches
2014-12-19 1:43 ` Måns Rullgård
2014-12-19 2:08 ` Joe Perches
2014-12-19 10:33 ` Måns Rullgård
2014-12-19 22:49 ` Joe Perches
2014-12-28 18:36 ` Pavel Machek
2014-12-19 8:03 ` Geert Uytterhoeven
2014-12-28 18:33 ` Pavel Machek
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=yw1xk31phptz.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=cernekee@gmail.com \
--cc=geert@linux-m68k.org \
--cc=joe@perches.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=realmz6@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).