From: Yinghai Lu <yinghai@kernel.org>
To: n0ano@n0ano.com
Cc: Paul Bolle <pebolle@tiscali.nl>,
donald.d.dugger@intel.com, linux-kernel@vger.kernel.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] Enable console on PCI serial devices
Date: Thu, 16 Oct 2008 11:19:28 -0700 [thread overview]
Message-ID: <48F785B0.7000008@kernel.org> (raw)
In-Reply-To: <20081016171218.GD14490@xolotl.n0ano.com>
n0ano@n0ano.com wrote:
> On Thu, Oct 16, 2008 at 09:23:39AM -0700, Yinghai Lu wrote:
>> ...
>> earlycon= and conole= share uart[8250]...
>>
>> the difference console= will start from early console and switch normal console automatically if the ttyS come out with same io/mmio address etc.
>>
>
> But there is no advantage to `earlycon' given that you can accomplish
> the same thing with `console'. The only use that I can see is if
> you specify `earlycon' without specifying `console' and then all
> you get are the initial kernel messages, after the serial drivers
> intializes all further messages go to the VGA. If makes much more
> sense to me to just use the `console' parameter to get all kernel
> messages on the serial port, and then there is no need for
> `earlycon'.
>
/* Check for early params. */
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) ||
(strcmp(param, "console") == 0 &&
strcmp(p->str, "earlycon") == 0)
) {
if (p->setup_func(val) != 0)
printk(KERN_WARNING
"Malformed early option '%s'\n", param);
}
}
/* We accept everything at this stage. */
return 0;
}
we need that holder in console sections to compare with console and earlycon.
YH
next prev parent reply other threads:[~2008-10-16 18:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 22:31 [PATCH] Enable console on PCI serial devices donald.d.dugger
2008-10-14 22:39 ` Yinghai Lu
2008-10-14 23:30 ` n0ano
2008-10-15 9:13 ` Paul Bolle
2008-10-15 20:48 ` n0ano
2008-10-16 10:43 ` Paul Bolle
2008-10-16 16:23 ` Yinghai Lu
2008-10-16 17:12 ` n0ano
2008-10-16 18:19 ` Yinghai Lu [this message]
2008-10-16 18:25 ` n0ano
2008-10-16 18:30 ` Yinghai Lu
2008-10-16 18:57 ` n0ano
2008-10-17 2:45 ` n0ano
2008-10-17 3:32 ` Yinghai Lu
2008-10-17 16:05 ` n0ano
2008-10-17 17:01 ` Yinghai Lu
2008-10-14 22:53 ` Alan Cox
2008-10-14 23:04 ` n0ano
2008-10-16 23:16 ` Bjorn Helgaas
2008-10-17 2:39 ` n0ano
2008-10-17 9:28 ` Alan Cox
2008-10-17 14:11 ` n0ano
2008-10-17 14:46 ` Bjorn Helgaas
2008-10-17 15:36 ` n0ano
2008-10-17 16:39 ` Bjorn Helgaas
2008-10-17 17:06 ` n0ano
2008-10-20 16:44 ` Lennart Sorensen
2008-10-20 17:11 ` Bjorn Helgaas
2008-10-20 17:43 ` n0ano
2008-10-20 19:11 ` Bjorn Helgaas
2008-10-21 20:08 ` n0ano
2008-10-21 22:08 ` Bjorn Helgaas
2008-10-21 22:33 ` n0ano
2008-10-17 14:44 ` 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=48F785B0.7000008@kernel.org \
--to=yinghai@kernel.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=donald.d.dugger@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=n0ano@n0ano.com \
--cc=pebolle@tiscali.nl \
/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