1) Use 0xFFEE as the VarId the reason is as follows:

[mirror_edk2.git] / EdkCompatibilityPkg / Compatibility / FrameworkHiiToUefiHiiThunk / FrameworkHiiToUefiHiiThunk.inf

diff --git a/EdkCompatibilityPkg/Compatibility/FrameworkHiiToUefiHiiThunk/FrameworkHiiToUefiHiiThunk.inf b/EdkCompatibilityPkg/Compatibility/FrameworkHiiToUefiHiiThunk/FrameworkHiiToUefiHiiThunk.inf
index 5ccb1d64c786378bd8cff8a883d4395585209411..d0483c76bfd33a75434382ab9368e76b1231e52c 100644 (file)
--- a/EdkCompatibilityPkg/Compatibility/FrameworkHiiToUefiHiiThunk/FrameworkHiiToUefiHiiThunk.inf
+++ b/EdkCompatibilityPkg/Compatibility/FrameworkHiiToUefiHiiThunk/FrameworkHiiToUefiHiiThunk.inf
@@ -1,6 +1,10 @@
 #/** @file\r
-# Component description file for HiiDatabase module which produce a Framework HII instance\r
-#  based on the avaliable UEFI HII protocol found in the platform.\r
+# Component description file for HiiDatabase module which produce a Framework HII Protocol instance\r
+# based on the avaliable UEFI HII protocol found in the platform. This modules enables modules complying\r
+# to Framework HII specification to able to run on a UEFI HII platform with only a rebuild. This is\r
+# to ensure that all HII packages are generated by UEFI HII package generation tools (UEFI VfrCompiler and\r
+# String Gather Tools). This thunk layer only produces the Frameowork HII protocol interface. The binary package\r
+# data format complying to UEFI HII specification.\r
 #\r
 # This module inits HII database and installs HII protocol based on the avaliable UEFI HII protocol found in the platform..\r
 # Copyright (c) 2006 - 2008, Intel Corporation\r