All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Masters <jcm@jonmasters.org>
To: "Herrenschmidt, Benjamin" <benh@amazon.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "x86@kernel.org" <x86@kernel.org>
Subject: Re: SPCR and default serial port
Date: Thu, 16 Apr 2020 23:29:41 -0400	[thread overview]
Message-ID: <2e2fe044-251d-eca9-3692-8f3182db3905@jonmasters.org> (raw)
In-Reply-To: <364e0ff5da091ed7faa0232302b6181ac30000de.camel@amazon.com>

On 4/15/20 2:04 AM, Herrenschmidt, Benjamin wrote:
> 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 ?

I think it would be /great/ if x86 followed Arm. A config option would 
allow it to be easily ignored by those who don't want it, but you'll 
want to get data from e.g. distros on how many systems have weird BIOSes 
that provide a non-useful table today.

Jon.

-- 
Computer Architect

      reply	other threads:[~2020-04-17  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15  6:04 SPCR and default serial port Herrenschmidt, Benjamin
2020-04-17  3:29 ` Jon Masters [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2e2fe044-251d-eca9-3692-8f3182db3905@jonmasters.org \
    --to=jcm@jonmasters.org \
    --cc=benh@amazon.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.