linux-kernel - Re: [patch] early printk and boot console fixups.

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64N.0705171038050.11098@blysk.ds.pg.gda.pl>
Date:	Thu, 17 May 2007 10:45:36 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
cc:	Yinghai Lu <yhlu.kernel@...il.com>, Gerd Hoffmann <kraxel@...e.de>,
	Andi Kleen <ak@...e.de>, akpm@...ux-foundation.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux kernel mailing list <linux-kernel@...r.kernel.org>
Subject: Re: [patch] early printk and boot console fixups.

On Wed, 16 May 2007, Bjorn Helgaas wrote:

> >  Given the generic name of "uart" I am assuming this will work with any 
> > UART driver making use of the serial_core.c core -- am I correct?
> 
> I knew somebody would ask that eventually :-)
> 
> Unfortunately, the answer is "no."  "console=uart" only works with
> 8250-compatible devices.

 But is it a design limitation or is it just that other UART drivers have 
to be modified to work with this option?  My point is if the former, then 
the option should be something like "console=8250" (the right-hand side 
being the name of the driver involved; others may want to add support for 
other drivers).  If the latter, then it's fine as is as other UART drivers 
may be wired to this code as a need arises.

  Maciej
-
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/