Intel Extensible Firmware Interface Specification page 437

G.4.2.1 Issuing the Command
To issue a Get State command, create a CDB and fill it in as shows in the table below:
CDB Field How to initialize the CDB structure for a Get State command
OpCode
PXE_OPCODE_GET_STATE
OpFlags PXE_OPFLAGS_NOT_USED
CPBsize PXE_CPBSIZE_NOT_USED
DBsize PXE_DBSIZE_NOT_USED
CPBaddr PXE_CPBADDR_NOT_USED
DBaddr PXE_DBADDR_NOT_USED
StatCode PXE_STATCODE_INITIALIZE
StatFlags PXE_STATFLAGS_INITIALIZE
A valid interface number from zero to !PXE.IFcnt.
IFnum
Control Set as needed.
G.4.2.2 Waiting for the Command to Execute
Monitor the upper two bits (14 & 15) in the
report
PXE_STATFLAGS_COMMAND_COMPLETE
the command has not been executed by the UNDI.
StatFlags
COMMAND_COMPLETE
COMMAND_FAILED
COMMAND_QUEUED
INITIALIZE
G.4.2.3 Checking Command Execution Results
After command execution completes, either successfully or not, the
contains the result of the command execution.
StatCode
SUCCESS
INVALID_CDB
BUSY
QUEUE_FULL
If the command completes successfully, use
state of the UNDI.
StatFlags
STOPPED
STARTED
INITIALIZED
Version 1.02
CDB.StatFlags
or PXE_STATFLAGS_COMMAND_FAILED,
Reason
Command completed successfully. StatFlags contain operational state.
Command failed. StatCode field contains error code.
Command has been queued. All other fields are unchanged.
Command has not been executed or queued.
Reason
Command completed successfully. StatFlags contain operational state.
One of the CDB fields was not set correctly.
UNDI is already processing commands. Try again later.
Command queue is full. Try again later.
PXE_STATFLAGS_GET_STATE_MASK
Reason
The UNDI is stopped.
The UNDI is started, but not initialized.
The UNDI is initialized.
12/12/00
32/64-bit UNDI Specification
field. Until these bits change to
field
CDB.StatCode
to check the
419