linux-kernel - Re: SPCR table parsing

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

Date:	Fri, 16 Jan 2015 10:58:04 +0000
From:	Mark Rutland <mark.rutland@....com>
To:	Jon Masters <jcm@...hat.com>
Cc:	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>, leif.lindholm@...aro.org
Subject: Re: SPCR table parsing

On Fri, Jan 16, 2015 at 03:08:37AM +0000, Jon Masters wrote:
> Hi Folks,
> 
> We're implementing support for SPCR table parsing shortly[0], since it
> will allow to deprecate supplying a "console=" (and eventually, also
> "earlycon=") on 64-bit ARM servers, where it's not always the case that
> we can assume a 16550 at a specific address. SPCR has been provided on
> x86 systems since 2000 but is not (yet) supported by Linux.

For anyone using DT rather than ACPI, the same can be achieved in
mainline with /chosen/stdout-path as of:

7914a7c5651a5161 "of: support passing console options with stdout-path"

Documented in:

2a9d832cc9aae21e "of: Add bindings for chosen node, stdout-path"

e.g.

uart: serial@f00 {
	reg = <0xf00 0x200>;
	compatible = "vendor,some-serial-device";
};

chosen {
	stdout-path = "/serial@f00:115200n8";
};

This will be used for both the console and earlycon. Please make use of
this where possible.

Thanks,
Mark.
--
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/