[ECOS] TCP/IP Stack for eCos.

[ECOS] TCP/IP Stack for eCos.

[Prakash R]

We plan to port BSD-4.4lite's TCP/IP stack on eCos. Currently we are
trying to get the eCos to run on our MPC860 based board. Once we are
through with that we would be porting TCP/IP stack on eCos. I request
the people interested to get in touch, so that we can share our
expertise/experience.

We are also looking into RTEMS to find out how TCP/IP has been
implemented onto RTEMS.

-- 
Prakash R	
Co-ordinating Engineer, Internet Telephony Group
===========================================================================
C-DOT (Centre for Development of Telematics)	
71/1, Sneha Complex, Miller Road, Bangalore - 560052, India
Email:rprakash@cdotb.ernet.in, Phone:+91-80-2263399, Fax:+91-80-2263256 
===========================================================================

[ECOS] Re: TCP/IP Stack for eCos.

[Bart Veer]

>>>>> "Prakash" == Prakash R <rprakash@cdotb.ernet.in> writes:

    Prakash> We plan to port BSD-4.4lite's TCP/IP stack on eCos.
    Prakash> Currently we are trying to get the eCos to run on our
    Prakash> MPC860 based board. Once we are through with that we
    Prakash> would be porting TCP/IP stack on eCos. I request the
    Prakash> people interested to get in touch, so that we can share
    Prakash> our expertise/experience.

A port of a free TCP/IP stack to eCos is something that Cygnus would
very much like to see, but so far we have not had the time to work on
this ourselves. However we can provide some assistance. Several
members of the eCos team have prior experience with the BSD stacks and
can provide advise on integrating them with eCos. We can also provide
facilities on sourceware.cygnus.com, for example ftp space, to
make collaboration easier.

Bart Veer // eCos net maintainer

Re: [ECOS] Re: TCP/IP Stack for eCos.

[Ramana]

Hi,
I am the guy who seems to have started the current thread. My company is
willing to provide some of the required effort to do the port. Is it
possible for some one to coordinate the effort. We seem to have enough
people willing ot provide the time.
rgds
Ramana B.V


Bart Veer wrote:

> >>>>> "Prakash" == Prakash R <rprakash@cdotb.ernet.in> writes:
>
>     Prakash> We plan to port BSD-4.4lite's TCP/IP stack on eCos.
>     Prakash> Currently we are trying to get the eCos to run on our
>     Prakash> MPC860 based board. Once we are through with that we
>     Prakash> would be porting TCP/IP stack on eCos. I request the
>     Prakash> people interested to get in touch, so that we can share
>     Prakash> our expertise/experience.
>
> A port of a free TCP/IP stack to eCos is something that Cygnus would
> very much like to see, but so far we have not had the time to work on
> this ourselves. However we can provide some assistance. Several
> members of the eCos team have prior experience with the BSD stacks and
> can provide advise on integrating them with eCos. We can also provide
> facilities on sourceware.cygnus.com, for example ftp space, to
> make collaboration easier.
>
> Bart Veer // eCos net maintainer

Re: [ECOS] Re: TCP/IP Stack for eCos.

[Andrew Over]

On Mon, Oct 04, 1999 at 05:51:36PM -0400, Ramana wrote:

> I am the guy who seems to have started the current thread. My company is
> willing to provide some of the required effort to do the port. Is it
> possible for some one to coordinate the effort. We seem to have enough
> people willing ot provide the time.

If there is some sort of coordinated effort, I can probably contribute
some time over November and December.

Cheers,
--Andrew

Re: [ECOS] Re: TCP/IP Stack for eCos.

[William Gatliff]

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.

RE: [ECOS] Re: TCP/IP Stack for eCos.

[Gordy Perkins]

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. 

> -----Original Message-----
> From:	Bart Veer [SMTP:bartv@cygnus.co.uk]
> Sent:	Monday, October 04, 1999 11:34 AM
> To:	rprakash@cdotb.ernet.in; tgi@netgem.com
> Cc:	ecos-discuss@sourceware.cygnus.com
> Subject:	[ECOS] Re: TCP/IP Stack for eCos.
> 
> >>>>> "Prakash" == Prakash R <rprakash@cdotb.ernet.in> writes:
> 
>     Prakash> We plan to port BSD-4.4lite's TCP/IP stack on eCos.
>     Prakash> Currently we are trying to get the eCos to run on our
>     Prakash> MPC860 based board. Once we are through with that we
>     Prakash> would be porting TCP/IP stack on eCos. I request the
>     Prakash> people interested to get in touch, so that we can share
>     Prakash> our expertise/experience.
> 
> A port of a free TCP/IP stack to eCos is something that Cygnus would
> very much like to see, but so far we have not had the time to work on
> this ourselves. However we can provide some assistance. Several
> members of the eCos team have prior experience with the BSD stacks and
> can provide advise on integrating them with eCos. We can also provide
> facilities on sourceware.cygnus.com, for example ftp space, to
> make collaboration easier.
> 
> Bart Veer // eCos net maintainer

Re: [ECOS] Re: TCP/IP Stack for eCos

[Tristan Gingold]

> Ramana:
> 
> If you read back through the archive, you'll see a discussion of this
> issue occurred
> earlier this year, in the spring I believe.  At that time, no one
> claimed to be working
> on such a project.  There was talk of porting the NetBSD stack, the way
> the
> RTEMS people did, but no-one volunteered to do it.
> 
> If anyone is working on a TCP/IP stack for eCos, please post.  My
> company,
> Microplex, has embedded networking technology on several commercial
> RTOSs,
> and I would be very interested in discussing any project to bring TCP/IP
> to eCos.
I have ported the TCP/IP stack of RTEMS (which is a port from FreeBSD) to
eCos.

I have at least do a tcp/ip echo.

Tristan.

[ECOS] Re: TCP/IP Stack for eCos

[Jim Belton]

Ramana:

If you read back through the archive, you'll see a discussion of this
issue occurred
earlier this year, in the spring I believe.  At that time, no one
claimed to be working
on such a project.  There was talk of porting the NetBSD stack, the way
the
RTEMS people did, but no-one volunteered to do it.

If anyone is working on a TCP/IP stack for eCos, please post.  My
company,
Microplex, has embedded networking technology on several commercial
RTOSs,
and I would be very interested in discussing any project to bring TCP/IP
to eCos.

Regards - Jim Belton

[ECOS] Re: TCP/IP Stack for eCos

[Bart Veer]

>>>>> "Fred" == Fred Fierling <fff@microplex.com> writes:

    >> > It probably would take very little effort to get the OSKit's TCP/IP
    >> > stack working in eCos, [...]

    Fred> I assume it's written in C?

    Fred> It occurs to me that since eCos is written in C++ that it
    Fred> may be an idea to write its TCP/IP stack in C++ as well.
    Fred> Thoughts?

If somebody were to write a completely new TCP/IP stack for eCos then
C++ would be a reasonable choice of language - or rather a subset of
the language, some parts such as exception handling involve rather
major code size overheads which are usually unacceptable in embedded
systems. In practice I am not sure there is much justification for
writing yet another TCP/IP stack, there are plenty of them out there
already.

Bart Veer // eCos net maintainer

[ECOS] Re: TCP/IP Stack for eCos

[Bart Veer]

>>>>> "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

[ECOS] Re: TCP/IP Stack for eCos

[Bart Veer]

>>>>> "Leonard" == Leonard, Niall <niall@exchange.Scotland.NCR.COM> writes:

    Leonard> Which processors are you currently porting eCos to ?

The only port that has been publicly announced so far is to the
Fujitsu SPARClite.

    http://www.cygnus.com/news/fujitsu.html

I expect that some more announcements will go out in the coming weeks,
but the exact timing is out of my control.

Bart Veer // eCos net maintainer