From: "Gao, Liming" <liming.gao@intel.com>
To: Andrew Fish <afish@apple.com>, edk2-devel <edk2-devel@lists.01.org>
Subject: Re: FDF Spec question?
Date: Wed, 21 Dec 2016 14:27:21 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D6C1D52@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <4B9E734E-C111-4CDB-AA8E-B3FA8B06D22B@apple.com>
Andrew:
Encapsulation section data is the section stream, not raw format. Then, Leaf section can be extracted from encapsulation section.
Thanks
Liming
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Andrew Fish
Sent: Wednesday, December 21, 2016 8:27 AM
To: edk2-devel <edk2-devel@lists.01.org>
Subject: [edk2] FDF Spec question?
Is it possible in the FDF syntax to make the payload of a EFI_SECTION_GUID_DEFINED (Encapsulating section) a raw binary file?
I can make the contents of the GUID'ed encapsulation section a section. But when I'm processing the GUID'ed section I just end up skipping over the extra 4 byte section header so it is unused space.
SECTION GUIDED 4C2B8C75-C6F6-11E6-B483-B8E8562CBAFA PROCESSING_REQUIRED = TRUE {
SECTION RAW = $(WORKSPACE)/MyPackage/MyNewType/Binary/newform.bin
}
There is a syntax to make a leaf section a binary file.
SECTION SUBTYPE_GUID AFC13561-9A65-4754-9C93-E133B3B8767C = $(WORKSPACE)/MyPackage/MyNewType/Binary/newform.bin
Thanks,
Andrew Fish
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2016-12-21 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 0:26 FDF Spec question? Andrew Fish
2016-12-21 14:27 ` Gao, Liming [this message]
2016-12-21 17:29 ` Andrew Fish
2016-12-22 1:18 ` Gao, Liming
2016-12-22 1:38 ` Andrew Fish
2016-12-23 4:59 ` Gao, Liming
[not found] ` <BC80BF3A-FE04-4BC5-BC23-341282A22EA1@apple.com>
2016-12-23 5:17 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14D6C1D52@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