02.03.2014 Views

BSP Developer's Guide

BSP Developer's Guide

BSP Developer's Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

H<br />

Implementing a MUX-Based<br />

Network Interface Driver<br />

H.1 Introduction<br />

A network interface driver written especially for use with the network stack is<br />

known as an Enhanced Network Driver (END). This chapter describes how to<br />

write an END as well as how to write a protocol that knows how to use an END.<br />

This chapter assumes that you are a software developer familiar with general<br />

networking principles—including protocol layering. Familiarity with 4.4 BSD<br />

networking internals is also helpful. This chapter is not a tutorial on writing<br />

network interface drivers. Instead, you should use this chapter as a guide to the<br />

specifics of writing a network interface driver that runs under VxWorks.<br />

If this is the first time you have written a network interface driver, consider taking<br />

an existing driver and modifying it to meet your needs. For more information on<br />

TCP/IP, Wind River recommends the following Addison Wesley publications:<br />

■<br />

■<br />

TCP/IP Illustrated, Volume 1, The Protocols, by W. Richard Stevens<br />

TCP/IP Illustrated, Volume 2, The Implementation,<br />

by Gary R. Wright and W. Richard Stevens<br />

NOTE: If you are using IPv6, you should also consult the WindNet IPv6<br />

Programmer’s <strong>Guide</strong>, 1.0 or a future version of the VxWorks Network Programmer’s<br />

<strong>Guide</strong> (that is, a version released after WindNet IPv6 1.0).<br />

NOTE: The src/drv/end directory contains templateEnd.c as well as ln7990End.c,<br />

a sample END driver for use with the Lance chip.<br />

267

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!