Intel Extensible Firmware Interface Specification page 456

Extensible Firmware Interface Specification
G.4.10.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.10.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
NOT_STARTED
NOT_INITIALIZED
StatFlags
If the command was successful, the
enable types are currently set. Possible
•
PXE_STATFLAGS_INTERRUPT_RECEIVE
•
PXE_STATFLAGS_INTERRUPT_TRANSMIT
•
PXE_STATFLAGS_INTERRUPT_COMMAND
The bits set in
CDB.StatFlags
CDB.OpFlags. For example: If transmit and receive share an external interrupt line, setting
either the transmit or receive interrupt will always enable both transmit and receive interrupts. In
this case both transmit and receive interrupts will be reported in CDB.StatFlags. Always
expect to get more than you ask for!
438
CDB.StatFlags
or PXE_STATFLAGS_COMMAND_FAILED,
Reason
Command completed successfully. Check StatFlags.
Command failed. StatCode field contains error code.
Command has been queued.
Command has been not executed or queued.
Reason
Command completed successfully. Check StatFlags.
One of the CDB fields was not set correctly.
UNDI is already processing commands. Try again later.
Command queue is full. Try again later.
The UNDI is not started.
The UNDI is not initialized.
CDB.StatFlags
CDB.StatFlags
may be different than those that were requested in
12/12/00
field. Until these bits change to
CDB.StatCode
field reports which external interrupt
bit settings are:
Version 1.02
field