linux-kernel - Re: [RFC PATCH] always probe UART HW when options are not specified

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: <5694C94B.3090405@free.fr>
Date:	Tue, 12 Jan 2016 10:37:15 +0100
From:	Mason <slash.tmp@...e.fr>
To:	Peter Hurley <peter@...leysoftware.com>,
	Sebastian Frias <sf84@...oste.net>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-serial@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Mans Rullgard <mans@...sr.com>
Subject: Re: [RFC PATCH] always probe UART HW when options are not specified

On 11/01/2016 20:06, Peter Hurley wrote:

> I don't have enough information to suggest what you "should" use
> here.
> 
> Is this going to be a shipping product?
> Is it single-core?
> etc.
> 
> And what is your purpose for outputting early boot information
> before loading the serial driver which does provide console output?

I'm not sure exactly which board Sebastian has in mind, but I've been
using the SERIAL_8250_RT288X driver on my Tango4 board.

Note: calling the UART driver "Au1x00/RT288x" is a bit of a misnomer,
as these are names of SoCs using that distinct register layout.
The actual IP is probably the 16550-compatible Palmchip BK-3103.
https://sites.google.com/a/palmchiptech.com/palmchiptech/product-services/hardware-services/ip-cores/bk-3103
(Not sure that this website is legitimate, though.)

When I need earlyprintk support, I use this patch from Mans:
http://thread.gmane.org/gmane.linux.kernel/2081016

Regards.