1*5d5fbe79SDavid van MoolenbroekThis directory contains generic network interface device drivers that 2*5d5fbe79SDavid van Moolenbroekdo not contain any hardware or architecture specific code. The files 3*5d5fbe79SDavid van Moolenbroekare: 4*5d5fbe79SDavid van Moolenbroek 5*5d5fbe79SDavid van Moolenbroekethernet.c 6*5d5fbe79SDavid van Moolenbroek Shared code for Ethernet based interfaces. 7*5d5fbe79SDavid van Moolenbroek 8*5d5fbe79SDavid van Moolenbroekethernetif.c 9*5d5fbe79SDavid van Moolenbroek An example of how an Ethernet device driver could look. This 10*5d5fbe79SDavid van Moolenbroek file can be used as a "skeleton" for developing new Ethernet 11*5d5fbe79SDavid van Moolenbroek network device drivers. It uses the etharp.c ARP code. 12*5d5fbe79SDavid van Moolenbroek 13*5d5fbe79SDavid van Moolenbroeklowpan6.c 14*5d5fbe79SDavid van Moolenbroek A 6LoWPAN implementation as a netif. 15*5d5fbe79SDavid van Moolenbroek 16*5d5fbe79SDavid van Moolenbroekslipif.c 17*5d5fbe79SDavid van Moolenbroek A generic implementation of the SLIP (Serial Line IP) 18*5d5fbe79SDavid van Moolenbroek protocol. It requires a sio (serial I/O) module to work. 19*5d5fbe79SDavid van Moolenbroek 20*5d5fbe79SDavid van Moolenbroekppp/ Point-to-Point Protocol stack 21*5d5fbe79SDavid van Moolenbroek The lwIP PPP support is based from pppd (http://ppp.samba.org) with 22*5d5fbe79SDavid van Moolenbroek huge changes to match code size and memory requirements for embedded 23*5d5fbe79SDavid van Moolenbroek devices. Please read /doc/ppp.txt and ppp/PPPD_FOLLOWUP for a detailed 24*5d5fbe79SDavid van Moolenbroek explanation. 25