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-next>] [day] [month] [year] [list]
Message-ID: <364e0ff5da091ed7faa0232302b6181ac30000de.camel@amazon.com>
Date:   Wed, 15 Apr 2020 06:04:02 +0000
From:   "Herrenschmidt, Benjamin" <benh@...zon.com>
To:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:     "x86@...nel.org" <x86@...nel.org>
Subject: SPCR and default serial port

Hi !

Today, arm64 allows the serial port specified in ACPI SPCR table to be
selected as a default console, but x86 doesn't (second argument to
acpi_parse_spcr).

I understand while we might have been worried of breaking existing
setups back then but should we re-think this, maybe via a CONFIG option
?

It makes a lot of sense to have firmware tell us which of the
potentially many serial port in a system is our active console, along
with its configuration...

This also shouldn't cause problem on systems that already specify a
console explicitly on the command line.

Any opinion ?

Cheers,
Ben.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ