Specifications

64
The second invocation has LegacySegment and LegacyOffset set to the location
in the 0xF0000 or 0xE0000 block to which the table is to be copied. The second
invocation allows any table address fix-ups to occur in the EFI memory copy of the
table. The caller, not EfiGetPlatformBinaryOem32Data, copies the modified
table to the allocated region in 0xF0000 or 0xE0000 block after the second invocation..
There are two generic mechanisms by which this mode can be
used.
Mechanism 1: This mode returns the data and the Legacy BIOS Protocol copies
the data into the F0000 or E0000 block in the Compatibility16 code. The
EFI_COMPATIBILITY16_TABLE entries Oem32Segment and Oem32Offset can
be viewed as two UINT16 entries.
Mechanism 2: This mode directly fills in the EFI_COMPATIBILITY16_TABLE with
a pointer to the INT15 E820 region containing the 32-bit code. It returns
EFI_UNSUPPORTED. The EFI_COMPATIBILITY16_TABLE entries,
Oem32Segment and Oem32Offset, can be viewed as two UINT16 entries or
as a single UINT32 entry as determined by the IBV.
Status Codes Returned
EFI_SUCCESS The data was returned successfully.
EFI_UNSUPPORTED Oem32 is not supported on this platform.