All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: 7eggert@gmx.de
Cc: Bodo Eggert <7eggert@web.de>, Yinghai Lu <yinghai@kernel.org>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Setup early console as early as possible
Date: Mon, 12 Jul 2010 14:52:20 -0700	[thread overview]
Message-ID: <4C3B8E94.6040101@zytor.com> (raw)
In-Reply-To: <20100712211459.A0644107B09@mail-in-07.arcor-online.net>

On 07/12/2010 01:57 PM, Bodo Eggert wrote:
> H. Peter Anvin <hpa@zytor.com> wrote:
>> On 07/12/2010 09:21 AM, Yinghai Lu wrote:
> 
>>> earlycon=uart8250 or console=uart8250 should be better than earlyprintk.
>>> because it is shared between different archs already.
> 
>> console= is crap, because it makes the user keep track of items they
>> should not have to deal with directly (unless they want to override the
>> defaults), i.e. the specific I/O ports used by the serial ports.
> 
> Why does console= require these parameters, if earlyprintk does not?
> 
> IMO you should fix console= to not need these parameters unless they cannot
> be guessed (in which case earlyprintk cannot guess them, either).
> 

earlycon is basically a low-level interface where you can steer
everything.  This is what you have to do on most embedded architectures,
where the firmware doesn't tell you where the console is located.

On x86, either the firmware can tell you or you can rely on 20 years of
legacy, with very few divergences.

	-hpa


  reply	other threads:[~2010-07-12 21:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f5czp-42V-9@gated-at.bofh.it>
     [not found] ` <f5n1M-2lt-21@gated-at.bofh.it>
     [not found]   ` <f5tqz-3ll-37@gated-at.bofh.it>
     [not found]     ` <f5u3g-4mj-11@gated-at.bofh.it>
     [not found]       ` <f5v90-5Wo-7@gated-at.bofh.it>
2010-07-12 20:57         ` [PATCH] x86: Setup early console as early as possible Bodo Eggert
2010-07-12 21:52           ` H. Peter Anvin [this message]
2010-07-11 21:44 Yinghai Lu
2010-07-12  8:58 ` Pekka Enberg
2010-07-12 15:47   ` H. Peter Anvin
2010-07-12 16:21     ` Yinghai Lu
2010-07-12 17:30       ` H. Peter Anvin
2010-07-13 17:43       ` Pekka Enberg
2010-07-13 20:35         ` Yinghai Lu
2010-07-13 20:46           ` Pekka Enberg
2010-07-12 17:44     ` Cyrill Gorcunov
2010-07-12 18:09       ` H. Peter Anvin
2010-07-12 18:11         ` Yinghai Lu
2010-07-12 22:57           ` Jeremy Fitzhardinge
2010-07-12 23:37             ` 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=4C3B8E94.6040101@zytor.com \
    --to=hpa@zytor.com \
    --cc=7eggert@gmx.de \
    --cc=7eggert@web.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@cs.helsinki.fi \
    --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 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.