From owner-freebsd-net  Thu Mar 30  8:13:47 2000
Delivered-To: freebsd-net@freebsd.org
Received: from irbs.irbs.com (irbs.irbs.com [209.36.62.129])
	by hub.freebsd.org (Postfix) with ESMTP id DCA4937BA5E
	for <freebsd-net@FreeBSD.ORG>; Thu, 30 Mar 2000 08:13:40 -0800 (PST)
	(envelope-from jc@irbs.com)
Received: (from jc@localhost)
	by irbs.irbs.com (8.8.5/8.8.5) id LAA11015;
	Thu, 30 Mar 2000 11:13:35 -0500 (EST)
Message-ID: <20000330111335.44210@irbs.com>
Date: Thu, 30 Mar 2000 11:13:35 -0500
From: John Capo <jc@irbs.com>
To: freebsd-net@FreeBSD.ORG
Subject: Re: Porting the (TCP/IP) net stack to another OS.
References: <20000329154527.58274.qmail@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89i
In-Reply-To: <20000329154527.58274.qmail@hotmail.com>; from Falsch Fillet on Wed, Mar 29, 2000 at 07:45:27AM -0800
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I wrapped the 1.X networking code including NFS around a real-time
tasker called Ucos that we were running on MIPS and 68K processors.
Both are big endian processors.  I spent less than 40 hours getting
the loopback and a PPP serial interface working.  Adding a file
descriptor mechanism for the tasks, a working select, and dealing
with variables in client/task side code from libc was much more of
a challenge. The kernel and task shared the same name/address space.

If I had to do it again I would budget at least 200 hours if a *nix
API is used, open/fopen/socket etc.

John Capo

Quoting Falsch Fillet (zak107@hotmail.com):
> Hello All,
> 
> I am interested in exploring the possibility of porting the FreeBSD 
> networking code to another OS (e.g. VxWorks, pSOS). What are the major 
> issues in porting the FreeBSD networking code to another OS? Where would one 
> start? Any help is greatly appreciated.
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message