From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
mingo@redhat.com, linux-kernel@vger.kernel.org,
yinghai@kernel.org, just.for.lkml@googlemail.com,
tglx@linutronix.de, Feng Tang <feng.tang@intel.com>,
Alan Cox <alan@linux.intel.com>,
greg@kroah.com
Subject: Re: Early console confusion
Date: Wed, 22 Sep 2010 11:26:23 -0700 [thread overview]
Message-ID: <4C9A4A4F.3060909@linux.intel.com> (raw)
In-Reply-To: <201009221222.00475.bjorn.helgaas@hp.com>
On 09/22/2010 11:21 AM, Bjorn Helgaas wrote:
>
> I think earlycon and earlyprintk have minimal backwards compatibility
> problems, since they're mostly for developers. And if we decided
> we did need to keep them, they could be undocumented and implemented
> on top of "console=" with the appropriate explicit device.
>
The problem is that they're actually hard-coded into the firmware of
some embedded devices.
-hpa
next prev parent reply other threads:[~2010-09-22 18:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 17:25 Linux 2.6.36-rc3 Linus Torvalds
2010-08-29 19:24 ` Chris Ball
2010-08-29 19:24 ` Torsten Kaiser
2010-08-29 22:27 ` Yinghai Lu
2010-08-29 22:36 ` Yinghai Lu
2010-08-29 22:53 ` Yinghai Lu
2010-08-30 4:50 ` Torsten Kaiser
2010-08-30 1:12 ` [PATCH] x86, setup: fix earlyprintk=serial,ttyS0,115200 Yinghai Lu
2010-08-30 1:13 ` [PATCH] x86, setup: fix earlyprintk=serial,0x3f8,115200 Yinghai Lu
2010-09-08 21:28 ` H. Peter Anvin
2010-09-09 7:23 ` Yinghai Lu
2010-09-21 19:58 ` [tip:x86/urgent] x86, setup: Fix earlyprintk=serial,0x3f8,115200 tip-bot for Yinghai Lu
2010-09-21 19:58 ` [tip:x86/urgent] x86, setup: Fix earlyprintk=serial,ttyS0,115200 tip-bot for Yinghai Lu
2010-09-22 15:12 ` Early console confusion Bjorn Helgaas
2010-09-22 15:56 ` H. Peter Anvin
2010-09-22 16:44 ` Bjorn Helgaas
2010-09-22 16:53 ` H. Peter Anvin
2010-09-22 18:21 ` Bjorn Helgaas
2010-09-22 18:26 ` H. Peter Anvin [this message]
2010-08-29 22:40 ` Linux 2.6.36-rc3 Jean-Denis Girard
2010-08-30 5:23 ` Borislav Petkov
2010-08-30 8:00 ` Jean-Denis Girard
2010-08-30 8:47 ` Miguel Calleja
2010-08-30 17:00 ` Suresh Jayaraman
2010-08-30 17:14 ` Shirish Pargaonkar
2010-08-30 17:25 ` Randy Dunlap
2010-08-30 21:27 ` Steve French
2010-08-30 19:28 ` Piotr Hosowicz
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=4C9A4A4F.3060909@linux.intel.com \
--to=hpa@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=bjorn.helgaas@hp.com \
--cc=feng.tang@intel.com \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=just.for.lkml@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).