From: prarit@redhat.com (Prarit Bhargava)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] acpi, spcr: Make SPCR available to x86
Date: Mon, 12 Feb 2018 08:47:57 -0500 [thread overview]
Message-ID: <1e69fffc-1c3b-8cc0-f1cb-695de5ccdcb5@redhat.com> (raw)
In-Reply-To: <20180212133429.GC25314@hirez.programming.kicks-ass.net>
On 02/12/2018 08:34 AM, Peter Zijlstra wrote:
> On Thu, Jan 18, 2018 at 10:09:51AM -0500, Prarit Bhargava wrote:
>> config ACPI_SPCR_TABLE
>> + bool "ACPI Serial Port Console Redirection Support"
>> + default y if X86
>> + help
>> + Enable support for Serial Port Console Redirection (SPCR) Table.
>> + This table provides information about the configuration of the
>> + earlycon console.
>
> I just got asked this by oldconfig, which left me rather puzzled, WTF
> does this do?
Odd -- I thought I had taken care of that :( My apologies Peter.
ACPI SPCR is used by a vendor to define the serial console for a system. If
SPCR exists a user can add kernel parameter "earlycon" (no extra kernel
parameters) and the console will work out-of-the-box.
The serial console configuration varies from vendor to vendor. This takes the
guess-work out of defining a serial console.
P.
>
next prev parent reply other threads:[~2018-02-12 13:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 15:09 [PATCH] acpi, spcr: Make SPCR available to x86 Prarit Bhargava
2018-01-20 14:33 ` Ingo Molnar
2018-01-21 23:21 ` Mark Salter
2018-01-22 21:49 ` Timur Tabi
2018-01-23 12:41 ` Prarit Bhargava
2018-02-12 13:34 ` Peter Zijlstra
2018-02-12 13:47 ` Prarit Bhargava [this message]
2018-02-12 14:43 ` Timur Tabi
2018-02-12 14:49 ` Prarit Bhargava
2018-02-12 15:10 ` Timur Tabi
2018-02-12 14:56 ` Peter Zijlstra
2018-02-12 15:18 ` Prarit Bhargava
2018-02-12 15:44 ` Peter Zijlstra
2018-02-12 15:54 ` Prarit Bhargava
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=1e69fffc-1c3b-8cc0-f1cb-695de5ccdcb5@redhat.com \
--to=prarit@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).