public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: William Gatliff <gatliff@haulpak.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Re: TCP/IP Stack for eCos.
Date: Mon, 04 Oct 1999 11:53:00 -0000	[thread overview]
Message-ID: <37F8F7A6.C4344808@haulpak.com> (raw)
In-Reply-To: <5692190AC12CD21180820060089845A82B5B98@MX_SOFTWARE_SRV>

Gordy Perkins wrote:

> As an attendee at the recent Embedded Systems Conference in San Jose,
> it's incredibly obvious that TCP/IP and capabilities like SNMP are of
> the highest importance - not another CPU port like SPARC. TCP/IP would
> increase the attractiveness of ECOS, therefore the *value* of future
> ports. Scenix (the Microchip competitor) had a PPP, TCP/IP and SMTP/HTTP
> demo - that's on a $3, 8-bit microcontroller. Someone at Cygnus ought to
> raise the priority to make sure ECOS has this critical feature ASAP.

... or sign a contract with someone who wants to do the work (like me!).
:^)

b.g.


--
William A. Gatliff
Senior Design Engineer
Komatsu Mining Systems
To teach is to learn.



  reply	other threads:[~1999-10-04 11:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-04  9:50 Gordy Perkins
1999-10-04 11:53 ` William Gatliff [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-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=37F8F7A6.C4344808@haulpak.com \
    --to=gatliff@haulpak.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).