From: Jon Masters <jcm@redhat.com>
To: "linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: SPCR table parsing
Date: Thu, 15 Jan 2015 22:08:37 -0500 [thread overview]
Message-ID: <54B880B5.6010907@redhat.com> (raw)
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.
If anyone knows of existing efforts on e.g. x86 or IA64, please get in
touch. I expect the initial implementation to require revision 2+ modern
server systems and possibly be limited to ARM initially.
Thanks,
Jon.
[0] This table is now published under a non-restrictive implementation
license and is linked from the UEFI ACPI documents webpage.
next reply other threads:[~2015-01-16 3:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 3:08 Jon Masters [this message]
2015-01-16 3:18 ` SPCR table parsing Jon Masters
2015-01-16 10:58 ` Mark Rutland
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=54B880B5.6010907@redhat.com \
--to=jcm@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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 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).