From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Gerd Hoffmann" <kraxel@redhat.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"Bjorn Helgaas" <bjorn.helgaas@hp.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 09:39:49 -0700 [thread overview]
Message-ID: <86802c440705210939x2b191a4dm170355b14578d3c@mail.gmail.com> (raw)
In-Reply-To: <465172EC.3010303@redhat.com>
On 5/21/07, Gerd Hoffmann <kraxel@redhat.com> wrote:
> What is the point in making that work on x86 additionally to serial
> support in early_printk? It might make sense to split away the serial
> bits from early_printk.c and move them out of arch/ into -- say --
> drivers/serial/, so other architectures can use that too and we have
> only one serial earlyprintk implementation in the kernel. Not sure it
> is worth the effort given the code size.
yes, we can drop serial bits from early_printk.c, and use
drivers/serial/8250_early.c and
with "earlycon=uart,io,0x3f8,9600n8", "early=ueart,mmio,0xfe000000,9600n8"
and we can extend other non 8250 compatitable uart to some *_early.c
in the same dir.
So other platform and other uart could be happy to get early console.
YH
next prev parent reply other threads:[~2007-05-21 16:40 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 [this message]
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=86802c440705210939x2b191a4dm170355b14578d3c@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®