linux-kernel - Re: [PATCH]serial: make early_uart to use early_prarm instead of console

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]

Date:	Mon, 21 May 2007 09:39:49 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Gerd Hoffmann" <kraxel@...hat.com>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"Bjorn Helgaas" <bjorn.helgaas@...com>, "Andi Kleen" <ak@...e.de>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"linux kernel mailing list" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH]serial: make early_uart to use early_prarm instead of console_initcall

On 5/21/07, Gerd Hoffmann <kraxel@...hat.com> wrote:
> What is the point in making that work on x86 additionally to serial
> support in early_printk?  It might make sense to split away the serial
> bits from early_printk.c and move them out of arch/ into -- say --
> drivers/serial/, so other architectures can use that too and we have
> only one serial earlyprintk implementation in the kernel.  Not sure it
> is worth the effort given the code size.

yes, we can drop serial bits from early_printk.c, and use
drivers/serial/8250_early.c and
with "earlycon=uart,io,0x3f8,9600n8", "early=ueart,mmio,0xfe000000,9600n8"

and we can extend other non 8250 compatitable uart to some *_early.c
in the same dir.
So other platform and other uart could be happy to get early console.

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