X-Git-Url: https://git.proxmox.com/?p=mirror_edk2.git;a=blobdiff_plain;f=Tools%2FXMLSchema%2FFrameworkDataElements.xsd;h=67fd6a893d191d14dc34dd6b6729b9ec605a0284;hp=e5b5dc1ee7e362fcd8a4771138bb7fa85b282638;hb=0675decb4f05fb9b8bc7ef60ba85dd3d2836160c;hpb=0df1e610850bf1d0f5192f952a9bf5c360de3146 diff --git a/Tools/XMLSchema/FrameworkDataElements.xsd b/Tools/XMLSchema/FrameworkDataElements.xsd index e5b5dc1ee7..67fd6a893d 100644 --- a/Tools/XMLSchema/FrameworkDataElements.xsd +++ b/Tools/XMLSchema/FrameworkDataElements.xsd @@ -17,6 +17,7 @@ + Abstract is valid for all Description Files @@ -25,7 +26,7 @@ - + @@ -172,6 +173,7 @@ + @@ -320,8 +322,9 @@ This is a list of Extern statements, right now, only Driver Binding information is provided. - - + + + @@ -626,6 +629,7 @@ + @@ -640,19 +644,20 @@ - Different Instances of Libraries + Different (Module) Instances of Libraries used ONLY in FPD Files. - + + @@ -669,17 +674,20 @@ + - Define in the MSA and/or SPD, what class of library is being produced by a library module - for components, it can also specify what class of library is consumed. + Used in MSA files. This defines what class of library is being supported = produced (library module) or consumed by a module. - + + + @@ -690,7 +698,19 @@ - + + + Used in MSA and SPD files. This defines what class of library is being supported = produced (library module) or consumed by a module. + + + + + + + + + + @@ -719,7 +739,7 @@ - + @@ -759,7 +779,7 @@ - + @@ -776,7 +796,7 @@ - Describe the valid content of a Surface Area Package Description (SPD) file + Surface Area Package Description (SPD) list of Module Surface Area files @@ -808,6 +828,24 @@ + + + Surface Area Package Description (SPD) list of Module Surface Area files + + + + + + + + + + + + + + + Define where we want our output to go. The Attribute, IntermediateDirectories, default MODULE, says that intermediate files will be local to the module, versus a unified directory structure. @@ -844,6 +882,7 @@ + @@ -871,6 +910,7 @@ + @@ -899,7 +939,7 @@ - This tag is used in the Framework Package Database File to track all packages installed in a workspace. + This tag is used in the Framework Package Database File to track all packages installed in a workspace. (Database) @@ -910,8 +950,15 @@ - - + + + + + + + + + @@ -923,7 +970,7 @@ - This tag is used in the Package Surface Area Description File to track package dependencies for a module + This tag is used in the Package Surface Area Description File to track package dependencies for a module (SPD) @@ -976,6 +1023,7 @@ + This specifies the size of the Pcd Datum. It is either 8, 16, 32 or 64 bits for values, 1 bit for BOOLEAN and variable length for elements defined as VOID* @@ -1064,128 +1112,130 @@ - - - - This is an enumerated data type that will be used for DYNAMIC_EX, PEIM or DXE only - - - - - - - + + + + This is an enumerated data type that will be used for DYNAMIC_EX, PEIM or DXE only + + + + + + + - - - - Child of Framework Platform Description (FPD) - We permit the FPD to use an external XML file for PCD information or else the information must be contained within the XML data element, PcdBuildData. - - - - - - Child of PcdBuildDeclarations - This is date element is used in the platform build description file and contains valid data for a Platform Build - There is ONE required Attribute, ItemType - - - - - - - - This as a unique identifier defined for either this name space. - The Target Attribute may be used to define a Target name space, such as PCI. - - - - - - - - - - - - This specifies the size of the Pcd Datum. It is either 8, 16, 32 or 64 bits for values, 1 bit for BOOLEAN and variable length for elements defined as VOID* - - - - - This Bit means that the Variable data is associated with HII - - - - - This bit enables the Vital Product Data area within flash for maintaining PCD information - - - - - This is only applicable to ItemType DYNAMIC_EX - - - - - - - - This element is a list of two entries per line, the first should be an integer, while the second entry should be a string value - - - - - - - - This section is for a list of SkuData Elements, ID and Value - - - - - - - - - - - - This value comes from a production line database, and has nothing to do with the number of SkuData IDs that have been defined. - - - - - This is the specific Sku ID for this build. - - - - - Max Number of Bytes of the data. - - - - - - - - - - - This is the Variable's GUID if and only if HII is enabled. - - - - - This is the C Name for the Variable, and is valid if and only HII is enabled. - - - - + + + + + Child of Framework Platform Description (FPD) + We permit the FPD to use an external XML file for PCD information or else the information must be contained within the XML data element, PcdBuildData. + + + + + + Child of PcdBuildDeclarations + This is date element is used in the platform build description file and contains valid data for a Platform Build + There is ONE required Attribute, ItemType + + + + + + + + This as a unique identifier defined for either this name space. + The Target Attribute may be used to define a Target name space, such as PCI. + + + + + + + + + + + + + This specifies the size of the Pcd Datum. It is either 8, 16, 32 or 64 bits for values, 1 bit for BOOLEAN and variable length for elements defined as VOID* + + + + + This Bit means that the Variable data is associated with HII + + + + + This bit enables the Vital Product Data area within flash for maintaining PCD information + + + + + This is only applicable to ItemType DYNAMIC_EX + + + + + + + + This element is a list of two entries per line, the first should be an integer, while the second entry should be a string value + + + + + + + + This section is for a list of SkuData Elements, ID and Value + + + + + + + + + + + + This value comes from a production line database, and has nothing to do with the number of SkuData IDs that have been defined. + + + + + This is the specific Sku ID for this build. + + + + + Max Number of Bytes of the data. + + + + + + + + + + + This is the Variable's GUID if and only if HII is enabled. + + + + + This is the C Name for the Variable, and is valid if and only HII is enabled. + + + + If HII is enabled, This is the offset into the variable data entry, If Vpd is enabled, then it's the Offset into the VPD area of the image defined by platform manufacturer, if neither HII nor Vpd are enabled, it's the offset into the PCD Data Area. HII and VPD can never be enabled at the same time (as of the date of this document.) @@ -1198,22 +1248,23 @@ - - - - This is an enumerated data type that will be used for DYNAMIC_EX, PEIM or DXE only - - - - - - - + + + + This is an enumerated data type that will be used for DYNAMIC_EX, PEIM or DXE only + + + + + + + - + + Child of Package Surface Area Description (SPD) @@ -1231,6 +1282,7 @@ + @@ -1281,7 +1333,9 @@ + @@ -1518,6 +1572,7 @@ +