Felix,
This is a very good question.
The UEFI Distribution Packaging Specification 1.0 (Errata B) available from
uefi.org and its associated XML schema has support to store localized Abstract
and localized Description. However, there is no XML schema support to store
the localized Module Name. We think it may be a good idea to separate the
content that is formally supported by the XML schema from the content that is
not formally supported by the XML schema, so the UPT tool that converts EDK II
Meta-Data files to XML and from XML back to EDK II Meta-Data files will be
straight forward. We were very concerned about the complexity of the UPT tool
if there was a single EDK II UNI file that contains some strings that would be
translated into XML and other strings that needed to be packaged up as pass
through. Then during package installation UTP would have to generate some UNI
strings from XML and mix those back together with the pass through content.
Thanks,
Mike
From: Felix Poludov [mailto:fel...@ami.com]
Sent: Thursday, August 07, 2014 8:57 AM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] INF/DEC file updates to EDK II packages
Mike,
Why localized module name and localized module abstract/description are in two
separate UNI files?
Thanks
Felix
From: Kinney, Michael D [mailto:michael.d.kin...@intel.com]
Sent: Wednesday, August 06, 2014 9:22 PM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: Re: [edk2] INF/DEC file updates to EDK II packages
Tim,
I should have put it in the original email. The spec changes will be shared
too. We welcome review comments on all spec changes and patches.
Thanks,
Mike
From: Tim Lewis [mailto:tim.le...@insyde.com]
Sent: Wednesday, August 06, 2014 2:58 PM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: Re: [edk2] INF/DEC file updates to EDK II packages
Mike --
Since there are dozens of tools in the industry that consume these files, don't
you think its better to put the specification changes out where the consumers
can read, evaluate and comment on them? I realize that "UserDefined" sections
should be skipped by tools (agreed) but that doesn't mean that other module
creators might have made similar or related extensions or want to understand
how these changes play into their tools.
Regards,
Tim
________________________________
From: Kinney, Michael D [michael.d.kin...@intel.com]
Sent: Wednesday, August 06, 2014 2:31 PM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: [edk2] INF/DEC file updates to EDK II packages
Hello,
I wanted to let everyone know about a number of patch reviews for EDK II
packages that will be sent out over the next couple of weeks. These patches
impact the order of content in INF/DEC files and comment blocks in INF/DEC
files, and should not have any build or functionality impacts. These patches
will address the following issues:
1) Usage information in INF file comment blocks are either incomplete or
incorrect. This includes usage information for
Protocols/PPIs/GUIDs/PCDs/HOBs/Events/BootModes. The syntax for usage
information in comment blocks is defined in the EDK II Module Information (INF)
Specification
2) Add MODULE_UNI_FILE to INF [Defines] section along with UNI file that
contains the localized Abstract and Description of a module.
a. Addresses an information gap between INF files and the UEFI
Distribution Packaging Specification XML schema
b. There will be an associated update to UPT in BaseTools to consume
MODULE_UNI_FILE and associated UNI file during UDP creation that performs the
INF -> XML conversion.
c. There will be an associated update to UPT in BaseTools to produce
MODULE_UNI_FILE and associated UNI file during UDP installation that performs
the XML -> INF conversion.
3) Add [UserExtensions.TianoCore."ExtraFiles"] section to INF files along
with associated UNI file that provides the localized Name of a module.
a. [UserExtensions.TianoCore."ExtraFiles"] provides an easy method for a
module to specify extra files not listed in [Sources] or [Binaries] sections to
be added to a UDP without having to list the files in the UPT package
information data file.
b. There will be an associated update to UPT in BaseTools to package up
files listed in [UserExtensions.TianoCore."ExtraFiles"] during UDP creation.
c. UNI file contains localized name of a module to go along with the
localized Abstract and Description from the MODULE_UNI_FILE.
4) PCD information in DEC file comment blocks are either incomplete or
incorrect. This includes detailed description, @Prompt, @ValidRange,
@ValidList, @Expression, and [Error.<TokenSpaceGuid>] validation error messages
5) Add PACKAGE_UNI_FILE to DEC [Defines] section along with UNI file that
contains the localized Abstract and Description of a package and localized
strings associated with PCDs.
a. Addresses an information gap between DEC files and the UEFI
Distribution Packaging Specification XML schema
b. There will be an associated update to UPT in BaseTools to consume
PACKAGE_UNI_FILE and associated UNI file during UDP creation that performs the
DEC -> XML conversion.
c. There will be an associated update to UPT in BaseTools to produce
PACKAGE_UNI_FILE and associated UNI file during UDP installation that performs
the XML -> DEC conversion.
6) Add [UserExtensions.TianoCore."ExtraFiles"] section to DEC files along
with associated UNI file that provides the localized Name of a package.
a. [UserExtensions.TianoCore."ExtraFiles"] provides an easy method for a
package to specify extra files to be added to a UDP without having to list the
files in the UPT package information data file.
b. There will be an associated update to UPT in BaseTools to package up
files listed in [UserExtensions.TianoCore."ExtraFiles"] during UDP creation.
c. UNI file contains localized name of a package to go along with the
localized Abstract and Description from the PACKAGE_UNI_FILE.
7) Make sure order of DEC/INF content matches the order that UPT generates
in the XML -> INF conversion
a. This allows UDP packages installed by UPT to be compared against EDK II
trunk/branches using standard diff utilities.
Patches for the following EDK II packages are being prepared
1) MdePkg
2) MdeModulePkg
3) IntelFrameworkPkg
4) IntelFrameworkModulePkg
5) FatPkg
6) ShellPkg
7) PcAtChipsetPkg
8) UefiCpuPkg
9) SourceLevelDebugPkg
10) CryptoPkg
11) SecurityPkg
12) NetworkPkg
Best regards,
Mike
The information contained in this message may be confidential and proprietary
to American Megatrends, Inc. This communication is intended to be read only by
the individual or entity to whom it is addressed or by their designee. If the
reader of this message is not the intended recipient, you are on notice that
any distribution of this message, in any form, is strictly prohibited. Please
promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and
then delete or destroy all copies of the transmission.
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel