From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Yinghai Lu <Yinghai.Lu@Sun.COM>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Gerd Hoffmann <kraxel@redhat.com>, Andi Kleen <ak@suse.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]serial: make early_uart to use early_prarm instead of console_initcall
Date: Mon, 21 May 2007 12:42:21 +0200 [thread overview]
Message-ID: <20070521104221.GU2012@bingen.suse.de> (raw)
In-Reply-To: <20070520202332.145d93a6.akpm@linux-foundation.org>
On Sun, May 20, 2007 at 08:23:32PM -0700, Andrew Morton wrote:
> On Fri, 18 May 2007 19:00:16 -0700 Yinghai Lu <Yinghai.Lu@Sun.COM> wrote:
>
> > [PATCH]serial: make early_uart to use early_prarm instead of console_initcall
> >
> > Make early_uart to use early_param, so uart console can be used earlier.
> > Make it to be bootconsole with CON_BOOT flag, so can use console handover
> > feature. and it will switch to corresponding normal serial console automatically.
> > new command line will be
> >
> > earlycon=uart,io,0x3f8,9600n8
> > earlycon=uart,io,0x3f8,9600n8 console=tty0
> >
> > it will print in very early stage
> > Early serial console at I/O port 0x3f8 (options '9600n8')
> > later for console it will print
> > console handover: boot [uart0] -> real [ttyS0]
>
> I'll queue this up for some testing, but I'd be a bit reluctant to send it
> into Linus due to my poor understanding of what it actually does. What
> _is_ an early console, and how does it differ from a non-early one?
It is someone's reimplemention of earlyprintk= for another architecture
that happens to mostly work on x86 too because the code is not ifdeffed.
I don't think it makes much sense on x86 though because earlyprintk exists.
-Andi
next prev parent reply other threads:[~2007-05-21 9:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 2:00 Yinghai Lu
2007-05-21 3:23 ` Andrew Morton
2007-05-21 4:29 ` Yinghai Lu
2007-05-21 4:46 ` Andrew Morton
2007-05-21 6:56 ` Yinghai Lu
2007-05-21 16:53 ` Bjorn Helgaas
2007-05-21 17:36 ` Yinghai Lu
2007-05-21 18:02 ` Bjorn Helgaas
2007-05-21 18:39 ` Yinghai Lu
2007-05-21 10:22 ` Gerd Hoffmann
2007-05-21 16:39 ` Yinghai Lu
2007-05-21 10:42 ` Andi Kleen [this message]
2007-05-21 16:27 ` Bjorn Helgaas
2007-05-21 16:27 ` Yinghai Lu
2007-05-21 16:27 ` Bjorn Helgaas
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=20070521104221.GU2012@bingen.suse.de \
--to=ak@suse.de \
--cc=Yinghai.Lu@Sun.COM \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome