diff options
author | Dandan Bi <dandan.bi@intel.com> | 2018-10-05 17:30:31 +0800 |
---|---|---|
committer | Liming Gao <liming.gao@intel.com> | 2018-10-12 14:46:01 +0800 |
commit | 9343d0a1cd09544686b14dba5b428d7bc811f6b9 (patch) | |
tree | 33f1ae99138d36cd10197c7e18b51badfe2c2df8 /BaseTools/Source/Python/Table/TableIdentifier.py | |
parent | b1df6c258249ae6cfaa5d0665a9cad99d9f22675 (diff) | |
download | edk2-9343d0a1cd09544686b14dba5b428d7bc811f6b9.tar.gz edk2-9343d0a1cd09544686b14dba5b428d7bc811f6b9.tar.bz2 edk2-9343d0a1cd09544686b14dba5b428d7bc811f6b9.zip |
MdePkg: Use VENDOR_DEVICE_PATH structure for Debug Port device path
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1229
When converting DebugPort device path from text,
current code use VENDOR_DEFINED_MESSAGING_DEVICE_PATH structure
for Debug port device node.
typedef struct {
EFI_DEVICE_PATH_PROTOCOL Header;
EFI_GUID Guid;
UINT8 VendorDefinedData[1];
} VENDOR_DEFINED_MESSAGING_DEVICE_PATH;
And Debugport Device Path is a vendor-defined messaging
device path with no data, only a GUID. So it's better to
use VENDOR_DEVICE_PATH to create the Debug port device node.
typedef struct {
EFI_DEVICE_PATH_PROTOCOL Header;
EFI_GUID Guid;
} VENDOR_DEVICE_PATH;
Cc: Ruiyu Ni <ruiyu.ni@intel.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Dandan Bi <dandan.bi@intel.com>
Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>
Diffstat (limited to 'BaseTools/Source/Python/Table/TableIdentifier.py')
0 files changed, 0 insertions, 0 deletions