From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 192.55.52.115, mailfrom: liming.gao@intel.com) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by groups.io with SMTP; Tue, 28 May 2019 08:24:30 -0700 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 May 2019 08:24:29 -0700 X-ExtLoop1: 1 Received: from lgao4-mobl1.ccr.corp.intel.com ([10.255.28.59]) by orsmga002.jf.intel.com with ESMTP; 28 May 2019 08:24:29 -0700 From: "Liming Gao" To: devel@edk2.groups.io Subject: [FdfSpecification Patch] FDF spec: Fix the issue in Rule section for RAW Type File Date: Tue, 28 May 2019 23:24:26 +0800 Message-Id: <20190528152426.17988-1-liming.gao@intel.com> X-Mailer: git-send-email 2.16.2.windows.1 BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=1765 FV File Statement clarifies RAW File type with file name only. But, FFS Rule section doesn't support this syntax. This is an issue in FDF spec. Per PI spec, RAW File has no section. It directly includes file data. So, FFS Rule section should support this usage. Signed-off-by: Liming Gao --- 3_edk_ii_fdf_file_format/39_[rule]_sections.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/3_edk_ii_fdf_file_format/39_[rule]_sections.md b/3_edk_ii_fdf_file_format/39_[rule]_sections.md index 34e767f..d5ec895 100644 --- a/3_edk_ii_fdf_file_format/39_[rule]_sections.md +++ b/3_edk_ii_fdf_file_format/39_[rule]_sections.md @@ -125,7 +125,8 @@ Conditional statements may be used anywhere within this section. ::= ["Fixed" ] ["Checksum" ] [] ::= "Align" - ::= {} {} {} + ::= {} {} {} {} + ::= "{" "}" ::= [] ::= {"COMPAT16"} {"PE32"} {"PIC"} {"TE"} {"FV_IMAGE"} {"RAW"} {"DXE_DEPEX"} {"UI"} -- 2.13.0.windows.1