public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Rick Leir <rleir@hymarc.com>
To: Wendell Thompson <wendell@hiwaay.net>
Cc: ecos-discuss@cygnus.com
Subject: Re: [ECOS] Network Support
Date: Thu, 11 Feb 1999 09:45:00 -0000	[thread overview]
Message-ID: <36C2F1F1.63DE@hymarc.com> (raw)
In-Reply-To: <002c01be553f$c29fb660$0300a8c0@WENDELL>

I would look at the code in FreeBSD, or a derivative called PicoBSD.
Get there via www.freebsd.org.  The downside is that you might have to 
wade through all sorts of IPV6 and IPSec and Mbone stuff.  The upside 
is that you might need all that stuff!

cheers -- Rick

Wendell Thompson wrote:
> 
> Has anyone looked into porting the XINU stack to eCos? The license for XINU
> allows free commercial use and it's well documented.
> 
> Wendell Thompson
> 
> -----Original Message-----
> From: David J. Fiddes <D.J@fiddes.surfaid.org>
> >> Does this mean that there is *no* IP support is eCOS?
> >> I amplanning on making extensive use of the networking

-- 
Rick Leir,  Hymarc 3D Vision Systems      (613) 727 1584 x214
Fast, precise laser scanners.             http://www.hymarc.com/

  reply	other threads:[~1999-02-11  9:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-10 18:37 Wendell Thompson
1999-02-11  9:45 ` Rick Leir [this message]
     [not found]   ` < 36C2F1F1.63DE@hymarc.com >
1999-02-14  7:02     ` David J. Fiddes
  -- strict thread matches above, loose matches on Subject: below --
2001-01-30  6:20 [ECOS] network support James Dabbs
2001-01-19  8:41 Fano Ramparany
2001-01-19  9:36 ` Gary Thomas
2001-01-22  6:48   ` Fano Ramparany
2001-01-22  7:13     ` Gary Thomas
2001-01-30  2:52       ` Fano Ramparany
2001-01-30  4:34         ` Gary Thomas
2001-01-30  6:03           ` Fano Ramparany
2001-01-30  6:08             ` Gary Thomas
2001-01-30  6:25               ` Lewin A.R.W. Edwards
2001-01-30  6:31                 ` Gary Thomas
2001-01-30  6:43                   ` Lewin A.R.W. Edwards
2001-02-13  5:55               ` Fano Ramparany
2001-02-13  6:20                 ` Gary Thomas
2001-02-14  2:44                   ` Fano Ramparany
2001-02-14  5:08                     ` Gary Thomas
2001-02-14  7:59                       ` Fano Ramparany
2001-02-14  8:24                         ` Gary Thomas
2001-02-14  9:12                           ` Lewin A.R.W. Edwards
2001-02-14  9:25                             ` Gary Thomas
2001-02-14  9:32                               ` Lewin A.R.W. Edwards
2001-02-14  9:40                                 ` Gary Thomas
2001-02-14 10:28                                   ` Robin Farine
2001-02-15  6:42                           ` Fano Ramparany
2001-01-22  7:15   ` Fano Ramparany
1999-02-10 21:23 [ECOS] Network Support Zubin Burjor Sethna
     [not found] ` < 6006B52C37ABD211AB0900805FFE9D79169230@saturn.sg.adisys.com.au >
1999-02-12 19:57   ` David J. Fiddes
1999-02-09 11:01 Gordon McFadden
     [not found] ` < Pine.LNX.4.04.9902090702270.648-100000@mailhost.westsoft-systems.com >
1999-02-10 13:22   ` David J. Fiddes
1999-02-10 21:19     ` Brendan Simon
1999-02-06 13:48 weatp
     [not found] ` < 9902069183.AA918326790@mail.syntron.com >
1999-02-08  8:26   ` 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=36C2F1F1.63DE@hymarc.com \
    --to=rleir@hymarc.com \
    --cc=ecos-discuss@cygnus.com \
    --cc=wendell@hiwaay.net \
    /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).