[ECOS] eCos Networking support

[ECOS] eCos Networking support

[Amit Agrawal]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 364 bytes --]

    I m  Porting  eCos along 
with TCP/IP implementation for PC as target system.     I m 
trying to patch-up PPP( Point to Point Protocol )openBSD code to the existing 
networking support provided by eCos, Please guide me how to go about 
it. Reply ASAP Thanx Amit Agrawal Software 
Engineer Aftek Infosys Ltd. Pune-9, Maharashtra, 
India

Re: [ECOS] eCos Networking support

[Jonathan Larmour]

> Amit Agrawal wrote:
> 
>     I m  Porting  eCos along with TCP/IP implementation for PC as target
> system.

Cool! It would be really good if the community could benefit from it.

>     I m trying to patch-up PPP( Point to Point Protocol )openBSD code to
> the existing networking support provided by eCos, Please guide me how to
> go
> about it.

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

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

Re: [ECOS] eCos Networking support

[Andrew Lunn]

>     I m trying to patch-up PPP( Point to Point Protocol )openBSD code to
> the existing networking support provided by eCos, Please guide me how to
> go
> about it.

If you look down the source tree of the network code there are a few
doc directories which give some usefull implementation details. Id Use
these as a place to get started.

        Andrew

Re: [ECOS] eCos Networking support

[Grant Edwards]

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

Re: [ECOS] eCos Networking support

[Jonathan Larmour]

Grant Edwards wrote:
> 
> 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?

Not really. Stuff worthy of going in the NEWS file is probably _too_
high-level for that purpose. Other than that, the ChangeLog's really are
the best record, and we try to make them pretty thorough.

But the choice of what constitutes an "important" change depends most of
all on the application using the code, so it's unlikely we'd find the right
balance for everyone. It can only be up to you to determine the
significance of the changes, and the consequent risk to your app involved;
which is why the ChangeLogs are there. For anything more than that... well
that's why we sell support :-).

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

Re: [ECOS] eCos Networking support

[Grant Edwards]

On Wed, Jun 28, 2000 at 09:31:44PM +0100, Jonathan Larmour wrote:

> But the choice of what constitutes an "important" change
> depends most of all on the application using the code, so it's
> unlikely we'd find the right balance for everyone. It can only
> be up to you to determine the significance of the changes, and
> the consequent risk to your app involved; which is why the
> ChangeLogs are there. For anything more than that... well
> that's why we sell support :-).

I suppose it's hard to make a living if you give _everything_
away for free. :)

-- 
Grant Edwards
grante@visi.com