public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] eCos Networking support
Date: Wed, 28 Jun 2000 12:03:00 -0000	[thread overview]
Message-ID: <20000628190329.A4688@visi.com> (raw)
In-Reply-To: <395A13EC.D880EDE6@redhat.co.uk>

On Wed, Jun 28, 2000 at 04:04:12PM +0100, Jonathan Larmour wrote:

> I don't know about the details of the stack itself (I'll leave
> that to others), but I would say that a very important thing is
> to work from the public anonymous CVS repository - there's been
> a lot of progress in the network support beyond that currently
> present in the "official" EPKs. See
> http://sourceware.cygnus.com/anoncvs.html

We're currently doing internal beta-test of a product that uses
eCos 1.3.1 and the "official" networking EPK file with some
patches to fix mutex problems (these patches have been
incorporated into the CVS tree).

I recently read through some of the history files in the
networking CVS tree, but It's pretty difficult for an outsider
to evaluate the risk/return associated with switching to a
current CVS snapshot.  Is there a higher-level (dumbed-down)
description of what's changed other than that in the history
files?

-- 
Grant Edwards
grante@visi.com

  parent reply	other threads:[~2000-06-28 12:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-28  1:13 Amit Agrawal
2000-06-28  8:04 ` Jonathan Larmour
2000-06-28  8:09   ` Andrew Lunn
2000-06-28 12:03   ` Grant Edwards [this message]
2000-06-28 13:31     ` Jonathan Larmour
2000-06-28 13:33       ` Grant Edwards

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=20000628190329.A4688@visi.com \
    --to=grante@visi.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).