All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zheng, Lv <lv.zheng at intel.com>
To: devel@acpica.org
Subject: Re: [Devel] AcpiDump.efi tool for uefi shell
Date: Tue, 12 May 2015 05:28:51 +0000	[thread overview]
Message-ID: <1AE640813FDE7649BE1B193DEA596E8802714513@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: 1AE640813FDE7649BE1B193DEA596E8802713BFE@SHSMSX101.ccr.corp.intel.com

[-- Attachment #1: Type: text/plain, Size: 1693 bytes --]

Hi,

I’ve prepared the patch here:
https://github.com/acpica/acpica/pull/73
You can try it:
https://github.com/zetalog/acpica/commit/5d00e67
The new code base no longer “includes” GNU EFI headers.
And we can now clearly see what’s actually linked by our ACPI EFI tools.

I’ve tested it:

1.       Built an x86_64 version acpidump.efi with gcc 4.7.1

2.       Executed it in UEFI shell
Everything seems to be still working.

Under another EFI implementation, you may want to:

1.       Implement startup code and invoke efi_main()

2.       Implement ACPI_DIV_64_BY_32, ACPI_SHIFT_RIGHT_64

3.       Modify the Makefiles to link the new EFI implementation
This should be the minimal requirement to port the ACPI tools to various EFI implementations.

Thanks and best regards
-Lv


From: Zheng, Lv
Sent: Friday, May 08, 2015 4:51 PM
To: Anteja Vuk Macek; Moore, Robert
Cc: devel(a)acpica.org; dsd(a)acpica.org
Subject: RE: [Devel] AcpiDump.efi tool for uefi shell

Hi,

This patch is wrong.
Let me offer one for you.

Thanks and best regards
-Lv

From: Anteja Vuk Macek [mailto:anteja.vm(a)dolotron.com]
Sent: Friday, May 08, 2015 3:45 PM
To: Moore, Robert
Cc: Zheng, Lv; devel(a)acpica.org<mailto:devel(a)acpica.org>; dsd(a)acpica.org<mailto:dsd(a)acpica.org>
Subject: Re: [Devel] AcpiDump.efi tool for uefi shell

Hi,

In Attacment is new acefi.h  . Is this ok?

Best regards,
Anteja Vuk - Maček
Software Engineer

Dolotron d.o.o.
Ziskovec 141
HR-40000 Cakovec
Croatia
Tel: ++385 (40) 865 205
Fax: ++385 (40) 865 732
mailto: anteja.vm(a)dolotron.com<mailto:anteja.vm(a)dolotron.com>
_________________________________

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 44072 bytes --]

             reply	other threads:[~2015-05-12  5:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12  5:28 Zheng, Lv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-05-08  8:50 [Devel] AcpiDump.efi tool for uefi shell Zheng, Lv
2015-05-08  7:45 Anteja Vuk Macek
2015-04-24 19:09 Moore, Robert
2015-04-24  6:21 Zheng, Lv
2015-04-24  3:42 Moore, Robert
2015-04-24  2:36 Zheng, Lv
2015-04-23  7:37 Anteja Vuk Macek

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=1AE640813FDE7649BE1B193DEA596E8802714513@SHSMSX101.ccr.corp.intel.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.