E.4.6.3 checking command execution results – Intel Extensible Firmware Interface User Manual
Page 920

Extensible Firmware Interface Specification
E-54
12/01/02
Version 1.10
E.4.6.3
Checking Command Execution Results
After command execution completes, either successfully or not, the
CDB.StatCode
field
contains the result of the command execution.
StatCode Reason
SUCCESS
Command completed successfully. DB has been written.
INVALID_CDB
One of the CDB fields was not set correctly.
BUSY
UNDI is already processing commands. Try again later.
QUEUE_FULL
Command queue is full. Try again later.
NOT_STARTED
The UNDI is not started.
DB
#pragma pack(1)
typedef struct s_pxe_pci_config_info {
// This is the flag field for the PXE_DB_GET_CONFIG_INFO union.
// For PCI bus devices, this field is set to PXE_BUSTYPE_PCI.
PXE_UINT32
BusType;
// This identifies the PCI network device that this UNDI
// interface is bound to.
PXE_UINT16
Bus;
PXE_UINT8
Device;
PXE_UINT8
Function;
// This is a copy of the PCI configuration space for this
// network device.
union {
PXE_UINT8
Byte[256];
PXE_UINT16
Word[128];
PXE_UINT32
Dword[64];
} Config;
} PXE_PCI_CONFIG_INFO;
#pragma pack()
#pragma pack(1)
typedef struct s_pxe_pcc_config_info {