public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Fred Fierling <fff@microplex.com>
To: Jay Lepreau <lepreau@cs.utah.edu>
Cc: ecos-discuss@cygnus.com
Subject: Re: [ECOS] TCP/IP Stack for eCos
Date: Tue, 04 May 1999 12:36:00 -0000	[thread overview]
Message-ID: <372F4C03.874F2246@microplex.com> (raw)
In-Reply-To: <199905041135.FAA13988@mancos.cs.utah.edu>

Jay Lepreau wrote:

> > Is anyone interested in working on an open TCP/IP stack for eCos?
>
> It probably would take very little effort to get the OSKit's TCP/IP
> stack working in eCos, [...]

Do you know if it's a zero copy stack?

  reply	other threads:[~1999-05-04 12:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-04  4:36 Jay Lepreau
1999-05-04 12:36 ` Fred Fierling [this message]
1999-05-05  5:12 ` [ECOS] " Bart Veer
  -- strict thread matches above, loose matches on Subject: below --
1999-09-28 22:04 [ECOS] " Prakash R
1999-09-23 15:44 [ECOS] TCP/IP Stack for ECOS Ramana
1999-09-24  9:08 ` Jonathan Larmour
     [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                   ` [ECOS] TCP/IP Stack for eCos 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-04-28  1:14 Fernando D. Mato Mira
1999-04-27 17:55 Kenneth Porter
1999-04-26  7:04 Leonard, Niall
1999-04-23 10:20 Fred Fierling
1999-04-23 12:10 ` Bob Cousins
1999-04-23 13:27   ` Fred Fierling
1999-04-23 16:08     ` Bob Cousins
1999-04-23 17:56       ` Frank W. Miller
1999-04-26  7:02 ` Bart Veer
1999-04-27  6:01   ` Fernando D. Mato Mira
1999-04-27 11:08     ` Fred Fierling

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=372F4C03.874F2246@microplex.com \
    --to=fff@microplex.com \
    --cc=ecos-discuss@cygnus.com \
    --cc=lepreau@cs.utah.edu \
    /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).