From: Yinghai Lu <yinghai@kernel.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: n0ano@n0ano.com, 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 09:23:39 -0700 [thread overview]
Message-ID: <48F76A8B.6050306@kernel.org> (raw)
In-Reply-To: <1224153822.3587.23.camel@test.thuisdomein>
Paul Bolle wrote:
> On Wed, 2008-10-15 at 14:48 -0600, n0ano@n0ano.com wrote:
>> On Wed, Oct 15, 2008 at 11:13:19AM +0200, Paul Bolle wrote:
>> As an aside, I would personally be in favor of removing the `earlycon'
>> kernel parameter entirely, it seems to be a strict subset of the
>> `console' parameter and anyone that wants `earlycon' probably wants
>> `console' anyway. Is there a strong argument for keeping that
>> parameter that I'm missing?
>
> The same thing puzzles me too. Note that earlyprintk=serial|ttyS?[...]
> also provides a similar feature.
>
>> earlycon= [KNL] Output early console device and options.
>> - uart[8250],io,<addr>[,options]
>> - uart[8250],mmio,<addr>[,options]
>> + uart[8250],io,<addr>[,options,[clkd]]
>> + uart[8250],mmio,<addr>[,options,[clkd]]
>
> clkd?
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.
YH
next prev parent reply other threads:[~2008-10-16 16:24 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 [this message]
2008-10-16 17:12 ` n0ano
2008-10-16 18:19 ` Yinghai Lu
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=48F76A8B.6050306@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.