URL https://opencores.org/ocsvn/openrisc_me/openrisc_me/trunk

Subversion Repositories openrisc_me

[/] [openrisc/] [trunk/] [rtos/] [ecos-2.0/] [packages/] [io/] [usb/] [eth/] [slave/] [v2_0/] [doc/] [usbseth-netdev.html] - Blame information for rev 174

Details | Compare with Previous | View Log


<!-- Copyright (C) 2001 Red Hat, Inc.                                -->
<!-- This material may be distributed only subject to the terms      -->
<!-- and conditions set forth in the Open Publication License, v1.0  -->
<!-- or later (the latest version is presently available at          -->
<!-- http://www.opencontent.org/openpub/).                           -->
<!-- Distribution of substantively modified versions of this         -->
<!-- document is prohibited without the explicit permission of the   -->
<!-- copyright holder.                                               -->
<!-- Distribution of the work or derivative of the work in any       -->
<!-- standard (paper) book form is prohibited unless prior           -->
<!-- permission is obtained from the copyright holder.               -->
<HTML
><HEAD
><TITLE
>Network Device for the eCos TCP/IP Stack</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="eCos Support for Developing USB-ethernet Peripherals"
HREF="io-usb-slave-eth.html"><LINK
REL="PREVIOUS"
TITLE="USB-ethernet State Handling"
HREF="usbseth-control.html"><LINK
REL="NEXT"
TITLE="Example Host-side Device Driver"
HREF="usbseth-host.html"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>eCos Support for Developing USB-ethernet Peripherals</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="usbseth-control.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="usbseth-host.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><H1
><A
NAME="USBSETH-NETDEV"
>Network Device for the eCos TCP/IP Stack</A
></H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN221"
></A
><H2
>Name</H2
>Network Device&nbsp;--&nbsp;USB-ethernet support for the eCos TCP/IP Stack</DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN224"
></A
><H2
>Description</H2
><P
>If the USB peripheral involves running the eCos TCP/IP stack and that
stack needs to use USB-ethernet as a transport layer (or as one of the
transports), then the USB-ethernet package can provide a suitable
network device driver. It is still necessary for higher-level code to
perform appropriate initialization by calling <A
HREF="usbseth-init.html"
><TT
CLASS="FUNCTION"
>usbs_eth_init</TT
></A
>, but
after that it will be the TCP/IP stack rather than application code
that transmits or receives ethernet frames.</P
><P
>Not all peripherals involving the USB-ethernet package will require a
TCP/IP stack. Hence the provision of the network device is controlled
by a configuration option <TT
CLASS="LITERAL"
>CYGPKG_USBS_ETHDRV</TT
>. By
default this will be enabled if the TCP/IP package
<TT
CLASS="LITERAL"
>CYGPKG_NET</TT
> is loaded, and disabled otherwise. </P
><P
>There are a number of other configuration options related to the
network device. <TT
CLASS="LITERAL"
>CYGFUN_USBS_ETHDRV_STATISTICS</TT
>
determines whether or not the package will maintain statistics, mainly
intended for SNMP: by default this will be enabled if the SNMP support
package <TT
CLASS="LITERAL"
>CYGPKG_SNMPAGENT</TT
> is loaded, and disabled
otherwise. The name of the ethernet device is controlled by
<TT
CLASS="LITERAL"
>CYGDATA_USBS_ETHDRV_NAME</TT
>, and has a default value
of either <TT
CLASS="LITERAL"
>eth0</TT
> or <TT
CLASS="LITERAL"
>eth1</TT
>
depending on whether or not there is another network device driver
present in the configuration.</P
><P
>Usually eCos network device drivers default to using DHCP for
obtaining necessary information such as IP addresses. This is not
appropriate for USB-ethernet devices. On the host-side the
USB-ethernet network device will not exist until the USB peripheral
has been plugged in and communication has been established. Therefore
any DHCP daemon on the host would not be listening on that network
device at the point that eCos requests its IP and other information. A
related issue is that the use of DHCP would imply the presence of a
DHCP daemon on every affected host machine, as opposed to a single
daemon (plus backups) for the network as a whole. For these reasons
the USB-ethernet package precludes the use of DHCP as a way of setting
the IP address, instead requiring alternatives such as manual
configuration.</P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="usbseth-control.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="io-usb-slave-eth.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="usbseth-host.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>USB-ethernet State Handling</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Example Host-side Device Driver</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

Line No.	Rev	Author	Line
1	27	unneback	`<!-- Copyright (C) 2001 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 substantively modified versions of this -->`
7			`<!-- document is prohibited without the explicit permission of the -->`
8			`<!-- copyright holder. -->`
9			`<!-- Distribution of the work or derivative of the work in any -->`
10			`<!-- standard (paper) book form is prohibited unless prior -->`
11			`<!-- permission is obtained from the copyright holder. -->`
12			`<HTML`
13			`><HEAD`
14			`><TITLE`
15			`>Network Device for the eCos TCP/IP Stack</TITLE`
16			`><META`
17			`NAME="GENERATOR"`
18			`CONTENT="Modular DocBook HTML Stylesheet Version 1.64`
19			`"><LINK`
20			`REL="HOME"`
21			`TITLE="eCos Support for Developing USB-ethernet Peripherals"`
22			`HREF="io-usb-slave-eth.html"><LINK`
23			`REL="PREVIOUS"`
24			`TITLE="USB-ethernet State Handling"`
25			`HREF="usbseth-control.html"><LINK`
26			`REL="NEXT"`
27			`TITLE="Example Host-side Device Driver"`
28			`HREF="usbseth-host.html"></HEAD`
29			`><BODY`
30			`CLASS="REFENTRY"`
31			`BGCOLOR="#FFFFFF"`
32			`TEXT="#000000"`
33			`LINK="#0000FF"`
34			`VLINK="#840084"`
35			`ALINK="#0000FF"`
36			`><DIV`
37			`CLASS="NAVHEADER"`
38			`><TABLE`
39			`WIDTH="100%"`
40			`BORDER="0"`
41			`CELLPADDING="0"`
42			`CELLSPACING="0"`
43			`><TR`
44			`><TH`
45			`COLSPAN="3"`
46			`ALIGN="center"`
47			`>eCos Support for Developing USB-ethernet Peripherals</TH`
48			`></TR`
49			`><TR`
50			`><TD`
51			`WIDTH="10%"`
52			`ALIGN="left"`
53			`VALIGN="bottom"`
54			`><A`
55			`HREF="usbseth-control.html"`
56			`>Prev</A`
57			`></TD`
58			`><TD`
59			`WIDTH="80%"`
60			`ALIGN="center"`
61			`VALIGN="bottom"`
62			`></TD`
63			`><TD`
64			`WIDTH="10%"`
65			`ALIGN="right"`
66			`VALIGN="bottom"`
67			`><A`
68			`HREF="usbseth-host.html"`
69			`>Next</A`
70			`></TD`
71			`></TR`
72			`></TABLE`
73			`><HR`
74			`ALIGN="LEFT"`
75			`WIDTH="100%"></DIV`
76			`><H1`
77			`><A`
78			`NAME="USBSETH-NETDEV"`
79			`>Network Device for the eCos TCP/IP Stack</A`
80			`></H1`
81			`><DIV`
82			`CLASS="REFNAMEDIV"`
83			`><A`
84			`NAME="AEN221"`
85			`></A`
86			`><H2`
87			`>Name</H2`
88			`>Network Device -- USB-ethernet support for the eCos TCP/IP Stack</DIV`
89			`><DIV`
90			`CLASS="REFSECT1"`
91			`><A`
92			`NAME="AEN224"`
93			`></A`
94			`><H2`
95			`>Description</H2`
96			`><P`
97			`>If the USB peripheral involves running the eCos TCP/IP stack and that`
98			`stack needs to use USB-ethernet as a transport layer (or as one of the`
99			`transports), then the USB-ethernet package can provide a suitable`
100			`network device driver. It is still necessary for higher-level code to`
101			`perform appropriate initialization by calling <A`
102			`HREF="usbseth-init.html"`
103			`><TT`
104			`CLASS="FUNCTION"`
105			`>usbs_eth_init</TT`
106			`></A`
107			`>, but`
108			`after that it will be the TCP/IP stack rather than application code`
109			`that transmits or receives ethernet frames.</P`
110			`><P`
111			`>Not all peripherals involving the USB-ethernet package will require a`
112			`TCP/IP stack. Hence the provision of the network device is controlled`
113			`by a configuration option <TT`
114			`CLASS="LITERAL"`
115			`>CYGPKG_USBS_ETHDRV</TT`
116			`>. By`
117			`default this will be enabled if the TCP/IP package`
118			`<TT`
119			`CLASS="LITERAL"`
120			`>CYGPKG_NET</TT`
121			`> is loaded, and disabled otherwise. </P`
122			`><P`
123			`>There are a number of other configuration options related to the`
124			`network device. <TT`
125			`CLASS="LITERAL"`
126			`>CYGFUN_USBS_ETHDRV_STATISTICS</TT`
127			`>`
128			`determines whether or not the package will maintain statistics, mainly`
129			`intended for SNMP: by default this will be enabled if the SNMP support`
130			`package <TT`
131			`CLASS="LITERAL"`
132			`>CYGPKG_SNMPAGENT</TT`
133			`> is loaded, and disabled`
134			`otherwise. The name of the ethernet device is controlled by`
135			`<TT`
136			`CLASS="LITERAL"`
137			`>CYGDATA_USBS_ETHDRV_NAME</TT`
138			`>, and has a default value`
139			`of either <TT`
140			`CLASS="LITERAL"`
141			`>eth0</TT`
142			`> or <TT`
143			`CLASS="LITERAL"`
144			`>eth1</TT`
145			`>`
146			`depending on whether or not there is another network device driver`
147			`present in the configuration.</P`
148			`><P`
149			`>Usually eCos network device drivers default to using DHCP for`
150			`obtaining necessary information such as IP addresses. This is not`
151			`appropriate for USB-ethernet devices. On the host-side the`
152			`USB-ethernet network device will not exist until the USB peripheral`
153			`has been plugged in and communication has been established. Therefore`
154			`any DHCP daemon on the host would not be listening on that network`
155			`device at the point that eCos requests its IP and other information. A`
156			`related issue is that the use of DHCP would imply the presence of a`
157			`DHCP daemon on every affected host machine, as opposed to a single`
158			`daemon (plus backups) for the network as a whole. For these reasons`
159			`the USB-ethernet package precludes the use of DHCP as a way of setting`
160			`the IP address, instead requiring alternatives such as manual`
161			`configuration.</P`
162			`></DIV`
163			`><DIV`
164			`CLASS="NAVFOOTER"`
165			`><HR`
166			`ALIGN="LEFT"`
167			`WIDTH="100%"><TABLE`
168			`WIDTH="100%"`
169			`BORDER="0"`
170			`CELLPADDING="0"`
171			`CELLSPACING="0"`
172			`><TR`
173			`><TD`
174			`WIDTH="33%"`
175			`ALIGN="left"`
176			`VALIGN="top"`
177			`><A`
178			`HREF="usbseth-control.html"`
179			`>Prev</A`
180			`></TD`
181			`><TD`
182			`WIDTH="34%"`
183			`ALIGN="center"`
184			`VALIGN="top"`
185			`><A`
186			`HREF="io-usb-slave-eth.html"`
187			`>Home</A`
188			`></TD`
189			`><TD`
190			`WIDTH="33%"`
191			`ALIGN="right"`
192			`VALIGN="top"`
193			`><A`
194			`HREF="usbseth-host.html"`
195			`>Next</A`
196			`></TD`
197			`></TR`
198			`><TR`
199			`><TD`
200			`WIDTH="33%"`
201			`ALIGN="left"`
202			`VALIGN="top"`
203			`>USB-ethernet State Handling</TD`
204			`><TD`
205			`WIDTH="34%"`
206			`ALIGN="center"`
207			`VALIGN="top"`
208			`> </TD`
209			`><TD`
210			`WIDTH="33%"`
211			`ALIGN="right"`
212			`VALIGN="top"`
213			`>Example Host-side Device Driver</TD`
214			`></TR`
215			`></TABLE`
216			`></DIV`
217			`></BODY`
218			`></HTML`
219			`>`

Browse

Tools

Subversion Repositories openrisc_me

[/] [openrisc/] [trunk/] [rtos/] [ecos-2.0/] [packages/] [io/] [usb/] [eth/] [slave/] [v2_0/] [doc/] [usbseth-netdev.html] - Blame information for rev 174