BSP Developer's Guide

H
Implementing a MUX-Based Network Interface Driver
device was down but is now back on line. When such situations arise, the END
should call muxError( ). This routine passes error information up to the MUX,
which, in turn, passes the information on to all protocols that have registered a
routine to receive it. The muxError( ) routine is declared as follows:
void muxError
(
void* pCookie, /* pointer to END_OBJ */
END_ERR* pError /* pointer to END_ERR structure */
)
Among its input, this routine expects a pointer to an end_err structure, which is
declared in end.h as follows:
typedef struct end_err
{
INT32 errCode; /* error code, see above */
char* pMesg; /* NULL-terminated error message, can be NULL */
void* pSpare; /* pointer to user defined data, can be NULL */
} END_ERR;
The error-receive routine that the protocol registers with the MUX must be of the
following prototype:
void xxError
(
END_OBJ* pEnd, /* pointer to END_OBJ */
END_ERR* pError, /* pointer to END_ERR */
void* pSpare /* pointer to protocol private data passed in muxBind */
)
The errCode member of an end_err structure is 32 bits long. Wind River reserves
the lower 16 bits of errCode for its own error messages. However, the upper 16 bits
are available to user applications. Use these bits to encode whatever error
messages you need to pass between drivers and protocols. The currently defined
error codes are as follows:
H
#define END_ERR_INFO 1 /* information only */
#define END_ERR_WARN 2 /* warning */
#define END_ERR_RESET 3 /* device has reset */
#define END_ERR_DOWN 4 /* device has gone down */
#define END_ERR_UP 5 /* device has come back on line */
#define END_ERR_FLAGS 6 /* device flags have changed */
#define END_ERR_NO_BUF 7 /* device’s cluster pool is exhausted */
281