From: Laszlo Ersek <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>,
Liming Gao <liming.gao@intel.com>
Subject: Re: [PATCH] BaseTools/EfiRom: supply missing machine type lookup strings
Date: Thu, 8 Sep 2016 23:30:29 +0200 [thread overview]
Message-ID: <d2985cd0-6068-a5d0-1263-476acd6048cf@redhat.com> (raw)
In-Reply-To: <CAKv+Gu98YrqCHwpGEJyyR-mzOfw1SmbDDbJtL+trYQaG25HfSQ@mail.gmail.com>
On 09/08/16 22:39, Ard Biesheuvel wrote:
> On 8 September 2016 at 20:55, Laszlo Ersek <lersek@redhat.com> wrote:
>> "EfiRom --dump" does not recognize the 0x8664 machine type:
>>
>>> EFI ROM header contents
>>> EFI Signature 0x0EF1
>>> Compression Type 0x0001 (compressed)
>>> Machine type 0x8664 (unknown)
>>> Subsystem 0x000B (EFI boot service driver)
>>> EFI image offset 0x0050 (@0xF650)
>>
>> Add lookup strings for the remaining EFI_IMAGE_MACHINE_* numeric macros
>> that can be found in
>> "BaseTools/Source/C/Include/IndustryStandard/PeImage.h".
>>
>> Cc: Liming Gao <liming.gao@intel.com>
>> Cc: Yonghong Zhu <yonghong.zhu@intel.com>
>> Contributed-under: TianoCore Contribution Agreement 1.0
>> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
>> ---
>> BaseTools/Source/C/EfiRom/EfiRom.h | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/BaseTools/Source/C/EfiRom/EfiRom.h b/BaseTools/Source/C/EfiRom/EfiRom.h
>> index 1214700826de..461963b4a701 100644
>> --- a/BaseTools/Source/C/EfiRom/EfiRom.h
>> +++ b/BaseTools/Source/C/EfiRom/EfiRom.h
>> @@ -117,6 +117,9 @@ static STRING_LOOKUP mMachineTypes[] = {
>> { EFI_IMAGE_MACHINE_IA32, "IA32" },
>> { EFI_IMAGE_MACHINE_IA64, "IA64" },
>> { EFI_IMAGE_MACHINE_EBC, "EBC" },
>> + { EFI_IMAGE_MACHINE_X64, "X64" },
>> + { EFI_IMAGE_MACHINE_ARMT, "ARMT" },
>
> Just 'ARM', please? PE/COFF has multiple machine types for ARM, but
> EFI only uses this one for ARM (0x1c2)
>
> With that change,
>
> Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
I wasn't sure if we wanted to use the edk2 architecture identifiers
here, or the last _FOO substrings from the macro names verbatim.
One fact that supported just picking _FOO is:
"BaseTools/Source/C/Include/IndustryStandard/PeImage.h" has two mappings
for Itanium (different macro name, same replacement text):
#define EFI_IMAGE_MACHINE_IA64 IMAGE_FILE_MACHINE_IA64
#define EFI_IMAGE_MACHINE_IPF IMAGE_FILE_MACHINE_IA64
The identifier that you can find in the edk2 INF files is IPF, not IA64,
but the above lookup strings include IA64, not IPF. This suggested that
the _FOO suffixes were authoritative, not the arch identifiers that we
use in the DSC / INF etc files.
I'm fine either way, but I would like to hear back from the BaseTools
maintainers too. Because, if we go with ARM, but keep IA64 (rather than
IPF), then that's a (differently) inconsistent situation. And if we
change IA64 to IPF as well, then downstream scripts that presumably
parse the output might break... Fun...
For now I prefer ARMT. Ugly but self-consistent (within the tool). If
Liming / Yonghong agree with you, I'll be happy to repost.
Thanks!
Laszlo
next prev parent reply other threads:[~2016-09-08 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 19:55 [PATCH] BaseTools/EfiRom: supply missing machine type lookup strings Laszlo Ersek
2016-09-08 20:39 ` Ard Biesheuvel
2016-09-08 21:30 ` Laszlo Ersek [this message]
2016-09-09 2:54 ` Gao, Liming
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-list 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=d2985cd0-6068-a5d0-1263-476acd6048cf@redhat.com \
--to=devel@edk2.groups.io \
/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