📄 nicevbend.html
字号:
<html><head><!-- /vobs/wpwr/docs/vxworks/ref/nicEvbEnd.html - generated by refgen from nicEvbEnd.c --> <title> nicEvbEnd </title></head><body bgcolor="#FFFFFF"> <hr><a name="top"></a><p align=right><a href="libIndex.html"><i>VxWorks Reference Manual : Libraries</i></a></p></blockquote><h1>nicEvbEnd</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote> <p><strong>nicEvbEnd</strong> - National Semiconductor ST-NIC Chip network interface driver </p></blockquote><h4>ROUTINES</h4><blockquote><p><p><b><i><a href="./nicEvbEnd.html#nicEndLoad">nicEndLoad</a></i>( )</b> - initialize the driver and device<br><b><i><a href="./nicEvbEnd.html#nicEvbInitParse">nicEvbInitParse</a></i>( )</b> - parse the initialization string<br><p></blockquote><h4>DESCRIPTION</h4><blockquote><p>This module implements the National Semiconductor 83902A ST-NIC Ethernetnetwork interface driver.<p>This driver is non-generic and is for use on the IBM EVB403 board. The driver must be given several target-specific parameters. Theseparameters, and the mechanisms used to communicate them to the driver, aredetailed below.<p></blockquote><h4>BOARD LAYOUT</h4><blockquote><p>This device is on-board. No jumpering diagram is necessary.<p></blockquote><h4>EXTERNAL INTERFACE</h4><blockquote><p>The only external interface is the <b><i>nicEvbEndLoad</i>( )</b> routine, which expectsthe <i>initString</i> parameter as input. This parameter passes in a colon-delimited string of the format:<p><i>unit</i>:<i>nic_addr</i>:<i>int_vector</i>:<i>int_level</i><p>The <b><i>nicEvbEndLoad</i>( )</b> function uses <b><i><a href="./ansiString.html#strtok">strtok</a></i>( )</b> to parse the string.<p></blockquote><h4>TARGET-SPECIFIC PARAMETERS</h4><blockquote><p><dl><dt><i>unit</i><dd>A convenient holdover from the former model. This parameter is used onlyin the string name for the driver.<p><dt><i>nic_addr</i><dd>Base address for NIC chip<p><dt><i>int_vector</i><dd>Configures the NIC device to generate hardware interrupts for various eventswithin the device. Thus, it contains an interrupt handler routine. The drivercalls <b><i>sysIntConnect</i>( )</b> to connect its interrupt handler to the interrupt vector.<p><dt><i>int_level</i><dd>This parameter is passed to an external support routine, <b><i><a href="../bsp/brutus/sysLib.html#sysLanIntEnable" >sysLanIntEnable</a></i>( )</b>,which is described below in "External Support Requirements." This routine is called during as part of driver's initialization. It handles any board-specific operations required to allow the servicing of a NIC interrupt on targets that use additional interrupt controller devices to help organize and service the various interrupt sources. This parameter makes it possible for this driver to avoid all board-specific knowledge of such devices. <p><dt>device restart/reset delay<dd>The global variable nicRestartDelay (UINT32), defined in this file, should be initialized in the BSP <b><i><a href="./sysLib.html#sysHwInit">sysHwInit</a></i>( )</b> routine. nicRestartDelay is used only with PowerPC platform and is equal to the number of time base increments which makes for 1.6 msec. This corresponds to the delay necessary to respect when restarting or resetting the device. </dl><p></blockquote><h4>EXTERNAL SUPPORT REQUIREMENTS</h4><blockquote><p>This driver requires several external support functions, defined as macros:<pre> SYS_INT_CONNECT(pDrvCtrl, routine, arg) SYS_INT_DISCONNECT (pDrvCtrl, routine, arg) SYS_INT_ENABLE(pDrvCtrl)</pre>There are default values in the source code for these macros. They presumememory-mapped accesses to the device registers and the normal <b><i><a href="./intArchLib.html#intConnect">intConnect</a></i>( )</b>,and <b><i><a href="./intArchLib.html#intEnable">intEnable</a></i>( )</b> BSP functions. The first argument to each is the devicecontroller structure. Thus, each has access back to all the device-specificinformation. Having the pointer in the macro facilitates the addition of new features to this driver.<p></blockquote><h4>SYSTEM RESOURCE USAGE</h4><blockquote><p>When implemented, this driver requires the following system resources:<p> - one mutual exclusion semaphore<br> - one interrupt vector<p></blockquote><h4>SEE ALSO</h4><blockquote><p><b><a href="./nicEvbEnd.html#top">nicEvbEnd</a></b>, <b><a href="./muxLib.html#top">muxLib</a></b><hr><a name="nicEndLoad"></a><p align=right><a href="rtnIndex.html"><i>Libraries : Routines</i></a></p></blockquote><h1><i>nicEndLoad</i>( )</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote> <p><strong><i>nicEndLoad</i>( )</strong> - initialize the driver and device</p></blockquote><h4>SYNOPSIS</h4><blockquote><p><pre>END_OBJ* nicEvbEndLoad ( char* initString /* string to be parse by the driver */ )</pre></blockquote><h4>DESCRIPTION</h4><blockquote><p>This routine initializes the driver and the device to the operational state.All of the device-specific parameters are passed in <i>initString</i>, whichexpects a string of the following format:<p><i>unit</i>:<i>base_addr</i>:<i>int_vector</i>:<i>int_level</i><p>This routine can be called in two modes. If it is called with an empty butallocated string, it places the name of this device (that is, "ln") into the <i>initString</i> and returns 0.<p>If the string is allocated and not empty, the routine attempts to loadthe driver using the values specified in the string.<p></blockquote><h4>RETURNS</h4><blockquote><p>An END object pointer, or NULL on error, or 0 and the name of thedevice if the <i>initString</i> was NULL.</blockquote><h4>SEE ALSO</h4><blockquote><p><b><a href="./nicEvbEnd.html#top">nicEvbEnd</a></b><hr><a name="nicEvbInitParse"></a><p align=right><a href="rtnIndex.html"><i>Libraries : Routines</i></a></p></blockquote><h1><i>nicEvbInitParse</i>( )</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote> <p><strong><i>nicEvbInitParse</i>( )</strong> - parse the initialization string</p></blockquote><h4>SYNOPSIS</h4><blockquote><p><pre>STATUS nicEvbInitParse ( NICEVB_END_DEVICE * pDrvCtrl, char * initString )</pre></blockquote><h4>DESCRIPTION</h4><blockquote><p>Parse the input string. Fill in values in the driver control structure.The initialization string format is:<i>unit</i>:<i>base_adrs</i>:<i>vecnum</i>:<i>intLvl</i><p><dl><dt><i>unit</i><dd>Device unit number, a small integer.<p><dt><i>base_adrs</i><dd>Base address for NIC device<p><dt><i>vecNum</i><dd>Interrupt vector number (used with <b><i>sysIntConnect</i>( )</b> ).<p><dt><i>intLvl</i><dd> Interrupt level.<p></dl></blockquote><h4>RETURNS</h4><blockquote><p><p> OK, or ERROR if any arguments are invalid.</blockquote><h4>SEE ALSO</h4><blockquote><p><b><a href="./nicEvbEnd.html#top">nicEvbEnd</a></b></body></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -