From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.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:02:59 -0600 [thread overview]
Message-ID: <200705211202.59817.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <86802c440705211036r19be100pa2d2ed13780f6316@mail.gmail.com>
On Monday 21 May 2007 11:36:58 am Yinghai Lu wrote:
> On 5/21/07, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> > > earlycon=uart,io,0x3f8,9600n8
> > > earlycon=uart,io,0x3f8,9600n8 console=tty0
> > > earlycon=uart,mmio,0xff5e0000,115200n8
> >
> > Why do we have to have a new "earlycon" argument? Why can't we just
> > parse "console=uart" early?
>
> with console=uart, you need to call early_serial_console_init
> explictly in your arch setup_arch to get early console.
Can't we just do:
early_param("console", setup_early_console);
and have setup_early_console() ignore everything except "uart"?
> with console_initcall(early_uart_console_init), the early_uart_console
> will be called via console_init in start_kernel, init/main.c that is
> not real early console.
I agree that's too late.
Bjorn
next prev parent reply other threads:[~2007-05-21 18:03 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 [this message]
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
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=200705211202.59817.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yhlu.kernel@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
all inboxes | Powered by JetHome®