IXB28504XGBEFS Intel, IXB28504XGBEFS Datasheet - Page 301

• Manufacturer Part Number: IXB28504XGBEFS
• Manufacturer: Intel

Specifications of IXB28504XGBEFS

• Lead Free Status / Rohs Status: Compliant

Driver API Reference—IXB2850
E.2.2
January 2007
Document Number: 05-2443-006
Returns
Note
The application can register to receive link state change notifications by calling
GbEMAC_Callback(
callback, arg_pCallback, called by the driver each time the link state changes on ports
specified by argHandle. The handle must be a valid handle (one received by the
application at port opening).
The third argument of the registration function, arg_pUserContext, is a variable that
is returned by the driver after the
application. This is useful when the same callback function is registered by multiple
applications.
Gigabit Ethernet Media Driver API Structures
The Gigabit Ethernet Media driver API uses following structures to present some of its
internal attributes to the user:
/* These structures are used in GbEMAC_Ioctl() function to carry value */
/* that user whishes to write or read to/from internal driver structures */
/* This structure is used for 32-bit values */
typedef struct gbe_mac_s_ioctl_ptr
{
} gbe_mac_ioctl_ptr;
/* This structure is used for 64-bit values (addresses and counters) */
typedef struct gbe_mac_s_ioctl_ptr_64 {
} gbe_mac_ioctl_ptr_64;
Return Code
SUCCESS (=0)
ERROR_INVALID_HANDLE
NO_MORE_CALLBACK_FOR_GBIC_INTERRUPT
uint32 portIndex;/* Port Number */
uint32
uint32 portIndex;/* Port Number */
uint32 valueHigh;/* High 47:32 bits of the address */
uint32 valueLow;/* Low 31:0 bits of the address */
value;/* Buffer which hold the value to be set/get */
). When
GbEMAC_Callback( )
GbEMAC_Callback( )
Description
Success
Invalid argHandle parameter
Callback array is full – no more applications can be
registered to use the driver
Intel NetStructure
is called, it registers the user
function is called to identify the
®
IXB2850 Packet Processing Boards
TPS
301