1 <!-- Copyright (C) 2003 Red Hat, Inc. -->
2 <!-- This material may be distributed only subject to the terms -->
3 <!-- and conditions set forth in the Open Publication License, v1.0 -->
4 <!-- or later (the latest version is presently available at -->
5 <!-- http://www.opencontent.org/openpub/). -->
6 <!-- Distribution of the work or derivative of the work in any -->
7 <!-- standard (paper) book form is prohibited unless prior -->
8 <!-- permission is obtained from the copyright holder. -->
12 >Network Device for the eCos TCP/IP Stack</TITLE
13 ><meta name="MSSmartTagsPreventParsing" content="TRUE">
16 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
19 TITLE="eCos Reference Manual"
20 HREF="ecos-ref.html"><LINK
22 TITLE="eCos Support for Developing USB-ethernet Peripherals"
23 HREF="io-usb-slave-eth.html"><LINK
25 TITLE="USB-ethernet State Handling"
26 HREF="usbseth-control.html"><LINK
28 TITLE="Example Host-side Device Driver"
29 HREF="usbseth-host.html"></HEAD
40 SUMMARY="Header navigation table"
49 >eCos Reference Manual</TH
57 HREF="usbseth-control.html"
71 HREF="usbseth-host.html"
82 NAME="USBSETH-NETDEV">Network Device for the eCos TCP/IP Stack</H1
90 >Network Device -- USB-ethernet support for the eCos TCP/IP Stack</DIV
99 >If the USB peripheral involves running the eCos TCP/IP stack and that
100 stack needs to use USB-ethernet as a transport layer (or as one of the
101 transports), then the USB-ethernet package can provide a suitable
102 network device driver. It is still necessary for higher-level code to
103 perform appropriate initialization by calling <A
104 HREF="usbseth-init.html"
110 after that it will be the TCP/IP stack rather than application code
111 that transmits or receives ethernet frames.</P
113 >Not all peripherals involving the USB-ethernet package will require a
114 TCP/IP stack. Hence the provision of the network device is controlled
115 by a configuration option <TT
117 >CYGPKG_USBS_ETHDRV</TT
119 default this will be enabled if the TCP/IP package
123 > is loaded, and disabled otherwise. </P
125 >There are a number of other configuration options related to the
128 >CYGFUN_USBS_ETHDRV_STATISTICS</TT
130 determines whether or not the package will maintain statistics, mainly
131 intended for SNMP: by default this will be enabled if the SNMP support
134 >CYGPKG_SNMPAGENT</TT
135 > is loaded, and disabled
136 otherwise. The name of the ethernet device is controlled by
139 >CYGDATA_USBS_ETHDRV_NAME</TT
140 >, and has a default value
148 depending on whether or not there is another network device driver
149 present in the configuration.</P
151 >Usually eCos network device drivers default to using DHCP for
152 obtaining necessary information such as IP addresses. This is not
153 appropriate for USB-ethernet devices. On the host-side the
154 USB-ethernet network device will not exist until the USB peripheral
155 has been plugged in and communication has been established. Therefore
156 any DHCP daemon on the host would not be listening on that network
157 device at the point that eCos requests its IP and other information. A
158 related issue is that the use of DHCP would imply the presence of a
159 DHCP daemon on every affected host machine, as opposed to a single
160 daemon (plus backups) for the network as a whole. For these reasons
161 the USB-ethernet package precludes the use of DHCP as a way of setting
162 the IP address, instead requiring alternatives such as manual
170 SUMMARY="Footer navigation table"
181 HREF="usbseth-control.html"
199 HREF="usbseth-host.html"
209 >USB-ethernet State Handling</TD
215 HREF="io-usb-slave-eth.html"
223 >Example Host-side Device Driver</TD