BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
Providing an Opaque Control Interface to Your Driver: endIoctl( )
Your endIoctl( ) entry point should handle all requests for changes to the state of
the device, such as bringing it up, shutting it down, turning on promiscuous mode,
and so on. You can also use your endIoctl( ) is to provide access to MIB-II interface
statistics.
! WARNING: If you are porting a driver from the BSD 4.3 model, you might be
tempted to use the existing xxIoctl( ) entry point as your endIoctl( ) entry point,
skipping the creation of separate entry points for the MCastAddr entry points. Do
not do this! Your driver must implement all entry points shown in Table H-1.
Your endIoctl( ) must take the following form:
STATUS endIoctl
(
void* pCookie, /* pointer to device-identifying END_OBJ */
int cmd, /* value identifying command */
caddr_t data /* data needed to complete command */
)
This function should return OK or ERROR. If an error occurs, it should set errno.
The parameters are:
pCookie
Passes a pointer to the END_OBJ structure returned by endLoad( ).
cmd
Can pass any of the values shown in the first column of Table H-2. Your
endIoctl( ) must have an appropriate response to each.
data
Passes the data or a pointer to the data that your endIoctl( ) needs to carry out
the command specified in cmd.
Table H-2
Ioctl Commands and Data Types
Command Function Data Type
EIOCSFLAGS Set device flags. int; see description of
END_OBJ.flags (flags, p.284)
EIOCGFLAGS Get device flags. int
EIOCSADDR Set device address. char*
EIOCGADDR Get device address. char*
292