public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tristan Gingold <tgi@netgem.com>
To: ecos-discuss@sourceware.cygnus.com
Cc: eCos Discuss <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] Re: TCP/IP Stack for eCos
Date: Tue, 28 Sep 1999 08:38:00 -0000	[thread overview]
Message-ID: <19990927182736.C27629@tgi2.netgem> (raw)
In-Reply-To: <37EBC367.36C83617@microplex.com>

> Ramana:
> 
> If you read back through the archive, you'll see a discussion of this
> issue occurred
> earlier this year, in the spring I believe.  At that time, no one
> claimed to be working
> on such a project.  There was talk of porting the NetBSD stack, the way
> the
> RTEMS people did, but no-one volunteered to do it.
> 
> If anyone is working on a TCP/IP stack for eCos, please post.  My
> company,
> Microplex, has embedded networking technology on several commercial
> RTOSs,
> and I would be very interested in discussing any project to bring TCP/IP
> to eCos.
I have ported the TCP/IP stack of RTEMS (which is a port from FreeBSD) to
eCos.

I have at least do a tcp/ip echo.

Tristan.

  reply	other threads:[~1999-09-28  8:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-24 11:29 Jim Belton
1999-09-28  8:38 ` Tristan Gingold [this message]
  -- 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-28 22:04 [ECOS] " Prakash R
1999-10-04  9:34 ` [ECOS] " Bart Veer
1999-10-04 14:59   ` Ramana
1999-10-04 15:23     ` Andrew Over
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=19990927182736.C27629@tgi2.netgem \
    --to=tgi@netgem.com \
    --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).