From: Jim Belton <jhb@microplex.com>
To: eCos Discuss <ecos-discuss@sourceware.cygnus.com>,
Ramana <ramanabv@danlawinc.com>
Subject: [ECOS] Re: Effort for TCP/IP Stack
Date: Fri, 24 Sep 1999 15:25:00 -0000 [thread overview]
Message-ID: <37EBFA9D.1C652291@microplex.com> (raw)
Ramana:
> Can anyone give me an estimate in terms of weeks for the effort
involved in
> porting the netBSD to Ecos. I may be able to do it if it is not too
much.
It really depends what you need. Many years ago, I ported UDP/IP to
Coherent (a UNIX like OS) at user level to support TFTP file transfers.
It took me about 2 months. I already had a working Ethernet driver, and
I didn't worry about porting all of the features of the IP stack.
If you want an estimate for a more fully blown TCP/IP stack, why not
post a question on the Linux Kernel mailing list? It would definitely
be in the man years to do everything that they've done from scratch, but
I recall at one time, someone ported the BSD stack to Linux, so if that
person is still monitoring the LKML, they might give you a good idea.
If you get a good response, please cross post it back here.
Good luck - Jim.
reply other threads:[~1999-09-24 15:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37EBFA9D.1C652291@microplex.com \
--to=jhb@microplex.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=ramanabv@danlawinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).