From: Jon Masters <jcm@redhat.com>
To: Duc Dang <dhdang@apm.com>
Cc: Aleksey Makarov <aleksey.makarov@linaro.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
linux-acpi@vger.kernel.org, linux-serial@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Russell King <linux@arm.linux.org.uk>,
Peter Hurley <peter@hurleysoftware.com>,
Mark Salter <msalter@redhat.com>,
Graeme Gregory <graeme.gregory@linaro.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] SPCR: check bit width for the 16550 UART
Date: Mon, 5 Dec 2016 19:05:01 -0500 [thread overview]
Message-ID: <7dc247ac-e557-a750-d23d-92c55630cb1d@redhat.com> (raw)
In-Reply-To: <CADaLNDn9ZVaZNc0B6_gJ7wBUBPne4qNpYeiPmUO7_SBzsW+srA@mail.gmail.com>
On 12/05/2016 06:52 PM, Duc Dang wrote:
> But I am still curious why setting subtype to '0' does not work on
> your board. Are you using Mustang or m400?
m400 with updated tables (that are correctly overriding not appending)
provided via INITRD override. I am looking at why it's not working.
[ 0.000000] ACPI: Table Upgrade: override [SPCR-HPE -ProLiant]
[ 0.000000] ACPI: SPCR 0x0000004FF7F30000 Physical table override, new table: 0x0000004FFFFF0000
[ 0.000000] ACPI: SPCR 0x0000004FFFFF0000 000050 (v02 HPE ProLiant 00001337 INTL 20160527)
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2016-12-06 0:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 13:05 [PATCH] SPCR: check bit width for the 16550 UART Aleksey Makarov
2016-12-05 18:51 ` Duc Dang
2016-12-05 23:27 ` Jon Masters
2016-12-05 23:52 ` Duc Dang
2016-12-06 0:03 ` Jon Masters
2016-12-06 0:05 ` Jon Masters [this message]
2016-12-06 0:31 ` Duc Dang
2016-12-06 2:27 ` Jon Masters
2016-12-06 3:55 ` Duc Dang
2016-12-06 6:34 ` Jon Masters
2016-12-06 6:53 ` Jon Masters
2016-12-06 7:13 ` Jon Masters
2016-12-06 8:40 ` Aleksey Makarov
2016-12-07 15:23 ` Mark Salter
2016-12-13 6:20 ` Jon Masters
2017-04-30 21:39 ` Jon Masters
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=7dc247ac-e557-a750-d23d-92c55630cb1d@redhat.com \
--to=jcm@redhat.com \
--cc=aleksey.makarov@linaro.org \
--cc=dhdang@apm.com \
--cc=graeme.gregory@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=msalter@redhat.com \
--cc=peter@hurleysoftware.com \
--cc=rjw@rjwysocki.net \
/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).