From: bob@lintilla.demon.co.uk (Bob Cousins)
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] TCP/IP Stack for eCos
Date: Fri, 23 Apr 1999 12:10:00 -0000 [thread overview]
Message-ID: <3720c0d0.32189806@post.demon.co.uk> (raw)
In-Reply-To: <3720ABE2.7672F6C0@microplex.com>
Hi Fred Fierling,
>Is anyone interested in working on an open TCP/IP stack
>for eCos?
I'm certainly interested, but I I don't think eCos is ported to any of the
targets I'm interested in, so my first task is to do or wait for such ports. I
would primarily be interested in using an OS like eCos for network applications,
so it's chicken and egg!
I recently worked on a TCP/IP stack for Hitachi processors using HI-OS (ITRON
based OS), and got quite far developing it on a PC under Windows. The few OS
calls the stack makes were handling by a library which made calls into Windows.
There was no hardware emulation or pre-emptive tasking, but this was not a great
problem. I wrote a PPP driver for it which could have used the PC serial port,
but I ended up using an internal loopback.
I studied various stacks around and although Unix stacks like BSD would be more
robust and mature, if I was picking a free stack I'd take a close look at the
Xinu stack. It has several bugs (which are partly documented), as it has not had
the benefit of widespread support. Assuming you are going to have to read the
RFCs and study other stacks anyway, it at least gives a step up on writing from
scratch.
--
Bob Cousins, Software Engineer.
http://www.lintilla.demon.co.uk/
"We demand that we may, or may not, be philosophers!"
next prev parent reply other threads:[~1999-04-23 12:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-23 10:20 Fred Fierling
1999-04-23 12:10 ` Bob Cousins [this message]
1999-04-23 13:27 ` Fred Fierling
1999-04-23 16:08 ` Bob Cousins
1999-04-23 17:56 ` Frank W. Miller
1999-04-24 3:38 ` [ECOS] h800 porting looking for Paolo Torricelli
1999-04-27 8:12 ` [ECOS] " Bart Veer
1999-04-28 0:17 ` Paolo Torricelli
1999-04-28 4:42 ` Bart Veer
1999-04-26 7:02 ` [ECOS] TCP/IP Stack for eCos Bart Veer
1999-04-27 6:01 ` Fernando D. Mato Mira
1999-04-27 11:08 ` Fred Fierling
1999-04-26 7:04 Leonard, Niall
1999-04-27 17:55 Kenneth Porter
1999-04-28 1:14 Fernando D. Mato Mira
1999-05-04 4:36 Jay Lepreau
1999-05-04 12:36 ` Fred Fierling
[not found] <Fred>
[not found] ` <Fierling's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <Tue,>
[not found] ` <04>
[not found] ` <May>
[not found] ` <99>
[not found] ` <12:35:31>
[not found] ` <PDT>
1999-05-04 13:51 ` Jay Lepreau
1999-05-04 17:06 ` Fred Fierling
1999-05-04 17:43 ` Brendan Simon
1999-05-05 1:54 ` Fernando D. Mato Mira
1999-09-23 15:44 [ECOS] TCP/IP Stack for ECOS Ramana
1999-09-24 9:08 ` Jonathan Larmour
1999-09-28 22:04 [ECOS] TCP/IP Stack for eCos Prakash R
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=3720c0d0.32189806@post.demon.co.uk \
--to=bob@lintilla.demon.co.uk \
--cc=ecos-discuss@sourceware.cygnus.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).