linux-kernel - Re: [PATCH] x86: Setup early console as early as possible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100712211459.A0644107B09@mail-in-07.arcor-online.net>
Date:	Mon, 12 Jul 2010 22:57:18 +0200
From:	Bodo Eggert <7eggert@....de>
To:	"H.  Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: Setup early console as early as possible

H. Peter Anvin <hpa@...or.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).

¢¢
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/