public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@cygnus.co.uk>
To: lepreau@cs.utah.edu
Cc: ecos-discuss@cygnus.com
Subject: [ECOS] Re: TCP/IP Stack for eCos
Date: Wed, 05 May 1999 05:12:00 -0000	[thread overview]
Message-ID: <199905051211.NAA13411@sheesh.cygnus.co.uk> (raw)
In-Reply-To: <199905041135.FAA13988@mancos.cs.utah.edu>

>>>>> "Jay" == Jay Lepreau <lepreau@cs.utah.edu> writes:

    >> Is anyone interested in working on an open TCP/IP stack for
    >> eCos?
    Jay> It probably would take very little effort to get the OSKit's
    Jay> TCP/IP stack working in eCos, because one of the OSKit's
    Jay> goals is that each component not only be entirely separable
    Jay> and optional, but be able to fit into *other* operating
    Jay> systems and environments.

    Jay> Copious docs, examples, papers and source available at
    Jay> http://www.cs.utah.edu/flux/oskit/ .

    <snip>

    Jay> It's written in C, uses autoconf, the GNU toolchain, supports
    Jay> ELF and a.out on the x86. Many components export the COM
    Jay> object model (scary sounding I know, but it's really just a
    Jay> glorified function table, so it's fast). You can debug on top
    Jay> of Unix or use remote gdb. In some ways eCos and the OSKit
    Jay> overlap but in more ways they are complementary. Good things
    Jay> could be done with them together.

All true, and OSKit is certainly worth a look. However readers should
also be aware that at least some parts of the software are GPL'd,
which would be a problem for many embedded systems developers. See
http://www.cs.utah.edu/flux/oskit/LICENSE for details.

Bart Veer // eCos net maintainer

  parent reply	other threads:[~1999-05-05  5:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-04  4:36 [ECOS] " Jay Lepreau
1999-05-04 12:36 ` Fred Fierling
1999-05-05  5:12 ` Bart Veer [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-10-04  9:50 [ECOS] " 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-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-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=199905051211.NAA13411@sheesh.cygnus.co.uk \
    --to=bartv@cygnus.co.uk \
    --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).