From: Al Stone <ahs3 at redhat.com>
To: devel@acpica.org
Subject: Re: [Devel] [PATCH] ACPICA: acpidump -- provide initial implementation for Linux
Date: Wed, 05 Jun 2013 16:12:06 -0600 [thread overview]
Message-ID: <51AFB7B6.1010109@redhat.com> (raw)
In-Reply-To: 94F2FBAB4432B54E8AACC7DFDE6C92E36FE7A3FD@ORSMSX103.amr.corp.intel.com
[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]
On 06/04/2013 06:56 PM, Moore, Robert wrote:
>
>
>> -----Original Message-----
>> From: devel-bounces(a)acpica.org [mailto:devel-bounces(a)acpica.org] On Behalf
>> Of Al Stone
>> Sent: Sunday, June 02, 2013 1:04 PM
>> To: devel(a)acpica.org
>> Subject: Re: [Devel] [PATCH] ACPICA: acpidump -- provide initial
>> implementation for Linux
>>
[snip...]
>>
>> 2) I've seen at least a few systems with more than one UEFI
>> table instance. Whether allowed or not, it looks like
>> the acpidump code will only allow this for SSDTs.
>>
>
> If you find such a system, we would like to see the acpidump.
> Thanks,
> Bob
Sure. It's my Lenovo T420s laptop -- my daily driver. I see
three UEFI tables in /sys/firmware/acpi/tables: UEFI1, UEFI2
and UEFI3. It seemed a bit odd, but I have not investigated
it any further. The tables are attached.
--
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3(a)redhat.com
-----------------------------------
[-- Attachment #2: uefi.tar.gz --]
[-- Type: application/gzip, Size: 971 bytes --]
next reply other threads:[~2013-06-05 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 22:12 Al Stone [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-05 0:56 [Devel] [PATCH] ACPICA: acpidump -- provide initial implementation for Linux Moore, Robert
2013-06-02 20:04 Al Stone
2013-06-01 4:22 Al Stone
2013-06-01 0:46 Moore, Robert
2013-06-01 0:20 Al Stone
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=51AFB7B6.1010109@redhat.com \
--to=devel@acpica.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.