From: jcm@redhat.com (Jon Masters)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ACPI: ARM64: support for ACPI_TABLE_UPGRADE
Date: Tue, 17 May 2016 12:48:53 -0400 [thread overview]
Message-ID: <b0933a59-239d-536f-4f63-a65e469f62a1@redhat.com> (raw)
In-Reply-To: <f0bf43ef-0be5-484c-5066-ab1929105b82@redhat.com>
On 05/17/2016 12:44 PM, Jon Masters wrote:
> 1). During development of a platform, it is much easier to debug
> problems with tables if you can test replacement ones without having to
> respin the firmware. In the server world, you usually don't have the
> firmware source code, so to get it respun could be days-weeks even if
> you are working with the authors closely. We have practically used this
> feature on a number of platforms already and it will continue.
For example, on one platform we were unable to fully boot RHEL(SA) due
to a bug in one of the ACPI tables. But I was able to boot the system to
a ramdisk containing a uuencode library and then write out the content
of the tables over the serial port, then decompile/patch/recompile, and
override replacement tables on the system. Then we beat the vendor up
with the fixes and the official firmware was corrected.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2016-05-17 16:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 12:06 [PATCH 0/3] ACPI: ARM64: support for ACPI_TABLE_UPGRADE Aleksey Makarov
2016-05-17 12:06 ` [PATCH 1/3] ACPI: table upgrade: use cacheable map for tables Aleksey Makarov
2016-05-18 3:06 ` Zheng, Lv
2016-05-17 12:06 ` [PATCH 2/3] ACPI: table upgrade: move early_initrd_acpi_init() to header file Aleksey Makarov
2016-05-18 1:08 ` Zheng, Lv
2016-05-17 12:06 ` [PATCH 3/3] ACPI: ARM64: support for ACPI_TABLE_UPGRADE Aleksey Makarov
2016-05-17 12:46 ` Mark Rutland
2016-05-17 16:44 ` Jon Masters
2016-05-17 16:48 ` Jon Masters [this message]
2016-05-23 17:56 ` Lorenzo Pieralisi
2016-05-23 18:29 ` Jon Masters
2016-05-23 16:49 ` Mark Rutland
2016-05-18 15:11 ` Aleksey Makarov
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=b0933a59-239d-536f-4f63-a65e469f62a1@redhat.com \
--to=jcm@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