From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: Alexei Fedorov <Alexei.Fedorov@arm.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Mitch Ishihara <Mitch.Ishihara@arm.com>
Subject: Re: ACPI IO Remapping Table Signature
Date: Fri, 18 Nov 2016 15:28:32 +0000 [thread overview]
Message-ID: <74D8A39837DF1E4DA445A8C0B3885C50386D7796@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <AM5PR0801MB1955773D3A91757BCAC5BDF69AB00@AM5PR0801MB1955.eurprd08.prod.outlook.com>
You are right.
I think it should be EFI_ACPI_6_0_IO_REMAPPING_TABLE_SIGNATURE.
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Alexei Fedorov
> Sent: Friday, November 18, 2016 11:00 PM
> To: edk2-devel@lists.01.org
> Cc: Mitch Ishihara <Mitch.Ishihara@arm.com>
> Subject: [edk2] ACPI IO Remapping Table Signature
>
> Is there any specific reason why ACPI IO Remapping Table is called "IORT"
> Interrupt Source Override" with its signature named as below:
>
> ///
> /// "IORT" Interrupt Source Override
> ///
> #define EFI_ACPI_6_0_INTERRUPT_SOURCE_OVERRIDE_SIGNATURE
> SIGNATURE_32('I', 'O', 'R', 'T')
> ...
> #define EFI_ACPI_6_1_INTERRUPT_SOURCE_OVERRIDE_SIGNATURE
> SIGNATURE_32('I', 'O', 'R', 'T')
>
> In Acpi60.h & Acpi61.h?
>
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended recipient,
> please notify the sender immediately and do not disclose the contents to any
> other person, use it for any purpose, or store or copy the information in any
> medium. Thank you.
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2016-11-18 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 15:00 ACPI IO Remapping Table Signature Alexei Fedorov
2016-11-18 15:28 ` Yao, Jiewen [this message]
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=74D8A39837DF1E4DA445A8C0B3885C50386D7796@shsmsx102.ccr.corp.intel.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