Intel Extensible Firmware Interface Specification page 483

G.4.19.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.19.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
INVALID_CPB
BUSY
QUEUE_FULL
NO_DATA
NOT_STARTED
NOT_INITIALIZED
Using the DB
If multiple frames per command are supported
DBs can be packed together.
#pragma pack(1)
typedef struct s_pxe_db_receive {
// Source and destination MAC addresses from media header.
PXE_MAC_ADDR SrcAddr;
PXE_MAC_ADDR DestAddr;
// Length of received frame.
// size. The receive buffer will not be overwritten.
// how to tell if data was lost because the receive buffer was
// too small.
PXE_UINT32 FrameLen;
Version 1.02
CDB.StatFlags
or PXE_STATFLAGS_COMMAND_FAILED,
Reason
Command completed successfully. Frames received and DB is written.
Command failed. StatCode field contains error code.
Command has been queued.
Command has been not executed or queued.
Reason
Command completed successfully. Frames received and DB is written.
One of the CDB fields was not set correctly.
One of the CPB fields was not set correctly.
UNDI is already processing commands. Try again later.
Command queue is full. Wait for queued commands to complete. Try again
later.
Receive buffers are empty.
The UNDI is not started.
The UNDI is not initialized.
(see!PXE.Implementation
May be larger than receive buffer
12/12/00
32/64-bit UNDI Specification
field. Until these bits change to
field
CDB.StatCode
flags), multiple
This is
465