From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Bjorn Helgaas" <bjorn.helgaas@hp.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_param instead of console_initcall
Date: Mon, 21 May 2007 16:29:36 -0700 [thread overview]
Message-ID: <86802c440705211629u3dce49cak59b69d6b00531e83@mail.gmail.com> (raw)
In-Reply-To: <200705211642.05620.bjorn.helgaas@hp.com>
On 5/21/07, Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
>
> How about just plain "console=8250,io,..."?
then the
__setup("console", setup_console);
setup_console will think their is one ttyS8, and then ...
How about console=uart8250,...?
> I don't want to add asm-ia64/fixmap.h with dummy definitions
> just for this.
>
> Can we add this:
>
> asm-ia64/io.h: #define bt_ioremap ioremap
> asm-x86_64/io.h: #define bt_ioremap early_ioremap
>
> and use bt_ioremap instead?
I will try it.
>
> > new command line will be
> >
> > earlycon=early8250,io,0x3f8,9600n8
> > earlycon=early8250,mmio,0xff5e0000,115200n8
> > or
> > console=early8250,io,0x3f8,9600n8
> > console=early8250,mmio,0xff5e0000,115200n8
>
> If you can make "console=early8250" work, we don't need
> "earlycon=early8250", do we?
actually I modify init/main.c
diff --git a/init/main.c b/init/main.c
index 1940fa7..07dad53 100644
--- a/init/main.c
+++ b/init/main.c
@@ -452,7 +452,9 @@ static int __init do_early_param(char *param, char *val)
struct obs_kernel_param *p;
for (p = __setup_start; p < __setup_end; p++) {
- if (p->early && strcmp(param, p->str) == 0) {
+ if ((p->early && strcmp(param, p->str) == 0) ||
+ (strcmp(param,"console")==0 && strcmp(p->str, "earlycon")==0)
+ ) {
if (p->setup_func(val) != 0)
printk(KERN_WARNING
"Malformed early option '%s'\n", param);
so make earlycon early_param setup will check console command line.
>
> Your patch adds trailing whitespace and a few cases of"<space><tab>".
> I use this in my .vimrc to catch these:
>
> highlight WhitespaceEOL ctermbg=red guibg=red
> match WhitespaceEOL /\s\+$\| \+\ze\t/
>
I will check it.
YH
next prev parent reply other threads:[~2007-05-21 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 20:36 Yinghai Lu
2007-05-21 22:42 ` Bjorn Helgaas
2007-05-21 23:29 ` Yinghai Lu [this message]
2007-05-22 0:05 ` Yinghai Lu
2007-05-22 1:44 ` Yinghai Lu
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=86802c440705211629u3dce49cak59b69d6b00531e83@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=ebiederm@xmission.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
all inboxes | Powered by JetHome®