From: Bart Veer <bartv@cygnus.co.uk>
To: rprakash@cdotb.ernet.in, tgi@netgem.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] Re: TCP/IP Stack for eCos.
Date: Mon, 04 Oct 1999 09:34:00 -0000 [thread overview]
Message-ID: <199910041633.RAA06030@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <37F1EC1D.49308949@cdotb.ernet.in>
>>>>> "Prakash" == Prakash R <rprakash@cdotb.ernet.in> writes:
Prakash> We plan to port BSD-4.4lite's TCP/IP stack on eCos.
Prakash> Currently we are trying to get the eCos to run on our
Prakash> MPC860 based board. Once we are through with that we
Prakash> would be porting TCP/IP stack on eCos. I request the
Prakash> people interested to get in touch, so that we can share
Prakash> our expertise/experience.
A port of a free TCP/IP stack to eCos is something that Cygnus would
very much like to see, but so far we have not had the time to work on
this ourselves. However we can provide some assistance. Several
members of the eCos team have prior experience with the BSD stacks and
can provide advise on integrating them with eCos. We can also provide
facilities on sourceware.cygnus.com, for example ftp space, to
make collaboration easier.
Bart Veer // eCos net maintainer
next prev parent reply other threads:[~1999-10-04 9:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-28 22:04 [ECOS] " Prakash R
1999-10-04 9:34 ` Bart Veer [this message]
1999-10-04 14:59 ` [ECOS] " Ramana
1999-10-04 15:23 ` Andrew Over
-- strict thread matches above, loose matches on Subject: below --
1999-10-04 9:50 Gordy Perkins
1999-10-04 11:53 ` William Gatliff
1999-09-24 11:29 Jim Belton
1999-09-28 8:38 ` Tristan Gingold
1999-05-04 13:51 [ECOS] " Jay Lepreau
1999-05-04 17:06 ` Fred Fierling
1999-05-05 5:15 ` [ECOS] " Bart Veer
1999-05-04 4:36 [ECOS] " Jay Lepreau
1999-05-05 5:12 ` [ECOS] " Bart Veer
1999-04-26 7:04 [ECOS] " Leonard, Niall
1999-04-26 7:39 ` [ECOS] " Bart Veer
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=199910041633.RAA06030@sheesh.cygnus.co.uk \
--to=bartv@cygnus.co.uk \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=rprakash@cdotb.ernet.in \
--cc=tgi@netgem.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).