linux-kernel - Re: [PATCH] Enable console on PCI serial devices

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20081016171218.GD14490@xolotl.n0ano.com>
Date:	Thu, 16 Oct 2008 11:12:18 -0600
From:	n0ano@...no.com
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Paul Bolle <pebolle@...cali.nl>, n0ano@...no.com,
	donald.d.dugger@...el.com, linux-kernel@...r.kernel.org,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH] Enable console on PCI serial devices

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'.

-- 
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@...no.com
Ph: 303/443-3786
--
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/