From owner-freebsd-questions Sat Jul 24 9: 3: 6 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 7794B14D53 for ; Sat, 24 Jul 1999 09:03:02 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id MAA03573; Sat, 24 Jul 1999 12:01:37 -0400 (EDT) Date: Sat, 24 Jul 1999 12:01:35 -0400 (EDT) From: Alfred Perlstein To: Bob Wirka Cc: freebsd-questions@FreeBSD.ORG Subject: Re: TCP/IP Stack In-Reply-To: <3799D42D.EF9BDFC3@inwave.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Jul 1999, Bob Wirka wrote: > Hello, > Is the TCP/IP stack supplied with FreeBSD suitable for porting to an > embedded system? This seems like a back-door approach to getting a > TCP/IP stack, but I'm doing a project that involves implementing TCP/IP > on a single board embedded computer. Is the stack tighly linked to the > OS? Can the stack be implemented by itself (with suitable glue code and > packet drivers)? > Any help you can give would be appreciated. The BSD TCP/IP stack has been ported extensively to other platforms, there are some issues you'll come across but it's definetly a better start than rolling your own. About the packet drivers concept, the freebsd ethernet device drivers are not overly complex, why not take a look: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/if_fxp.c?rev=1.70 -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message