Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!usenet.ins.cwru.edu!gatech!swrinde!elroy.jpl.nasa.gov!decwrl!netcomsv!netcom.com!bakul From: bakul@netcom.com (Bakul Shah) Subject: Re: extracting tcp/ip code to an embedded system Message-ID: <bakulCttpEC.Bsz@netcom.com> Organization: NETCOM On-line Communication Services (408 261-4700 guest) References: <31c2nb$7nn@senator-bedfellow.MIT.EDU> Date: Sun, 31 Jul 1994 21:08:36 GMT Lines: 19 janie@athena.mit.edu (Don Raines) writes: >Does anyone have experience extracting the tcp/ip code from >*BSD? (Or from Linux?) Specifically, I want ethernet support >for an embedded system. Obviously, part of the problem will be >a driver, although I'm flexible as to what ethernet chip I >will be using. Assuming you want tcp/ip to run *over* ethernet, start with sys/net and sys/netinet directories + socket bits from the sys/kern dir. Attempt to compile & link them. This will give you an idea of what pieces are missing. Start filling in missing bits. If you make the right ``cut'', a surprisingly small amount of code will need to be added. On the user side you will need to put together some sort of a socket library; presumaly your system call interface is very different (or non existent). The driver code is independent of the tcp/ip stack. Bakul Shah <bvs@BitBlocks.com>