On 05/04/16 03:10, Dong, Eric wrote:
On a separate but related note: The ConfigHdr portion of Request and
Response seems to contain absolutely zero information by the time it
reaches EFI_HII_CONFIG_ACCESS_PROTOCOL. As far as I can tell, it is
meaningful only to EFI_HII_CONFIG_ROUTING_PROTOCOL and a sensible API
design would never have exposed it to EFI_HII_CONFIG_ACCESS_PROTOCOL
instances.
Does the ConfigHdr have any meaning for EFI_HII_CONFIG_ACCESS_PROTOCOL,
or is it just a pointless blob of noise?
The GUID/NAME value in the ConfigHdr is get from the storage used in this
driver. If one driver has more than one storage, the Guid + Name specify which
storage info will be return.
Surely the EFI_HII_CONFIG_ACCESS_PROTOCOL's *This pointer already
uniquely identifies the storage.
(If not, then why not?)
Thanks,
Michael
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
