* Re: [ECOS] TCP/IP Stack for eCos
@ 1999-05-04 4:36 Jay Lepreau
1999-05-04 12:36 ` Fred Fierling
1999-05-05 5:12 ` [ECOS] " Bart Veer
0 siblings, 2 replies; 12+ messages in thread
From: Jay Lepreau @ 1999-05-04 4:36 UTC (permalink / raw)
To: Fred Fierling; +Cc: ecos-discuss
> Is anyone interested in working on an open TCP/IP stack for eCos?
It probably would take very little effort to get the OSKit's TCP/IP
stack working in eCos, because one of the OSKit's goals is that each
component not only be entirely separable and optional, but be able to
fit into *other* operating systems and environments.
Copious docs, examples, papers and source available at
http://www.cs.utah.edu/flux/oskit/ .
Examples of fitting in to other envs:
Outside people have used it to get a "Scheme computer" running in a
few hours. We've done the same for Java (you can boot Kaffe on bare
hardware). Outside people have used the device drivers and low-level
code in a number of their own x86 kernels.
Although some of the low-level OSKit components contain x86 or
PC-specific code, a large number of the 31 component libraries are
high level and should work on any architecture. Besides networking,
of interest might be BOOTP, posix-like libraries, pthreads, BSD and
Linux-supported filesystems, simple virtual memory, and some research
products in thread scheduling and network link scheduling. All the
Linux devices drivers are there.
It's written in C, uses autoconf, the GNU toolchain, supports ELF and
a.out on the x86. Many components export the COM object model (scary
sounding I know, but it's really just a glorified function table, so
it's fast). You can debug on top of Unix or use remote gdb. In some
ways eCos and the OSKit overlap but in more ways they are complementary.
Good things could be done with them together.
Jay Lepreau
University of Utah
p.s. Hi Stan, long time no see-- you wouldn't recognize the
4th east penthouse any more!
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ECOS] TCP/IP Stack for eCos
1999-05-04 4:36 [ECOS] TCP/IP Stack for eCos Jay Lepreau
@ 1999-05-04 12:36 ` Fred Fierling
1999-05-05 5:12 ` [ECOS] " Bart Veer
1 sibling, 0 replies; 12+ messages in thread
From: Fred Fierling @ 1999-05-04 12:36 UTC (permalink / raw)
To: Jay Lepreau; +Cc: ecos-discuss
Jay Lepreau wrote:
> > Is anyone interested in working on an open TCP/IP stack for eCos?
>
> It probably would take very little effort to get the OSKit's TCP/IP
> stack working in eCos, [...]
Do you know if it's a zero copy stack?
^ permalink raw reply [flat|nested] 12+ messages in thread
* [ECOS] Re: TCP/IP Stack for eCos
1999-05-04 4:36 [ECOS] TCP/IP Stack for eCos Jay Lepreau
1999-05-04 12:36 ` Fred Fierling
@ 1999-05-05 5:12 ` Bart Veer
1 sibling, 0 replies; 12+ messages in thread
From: Bart Veer @ 1999-05-05 5:12 UTC (permalink / raw)
To: lepreau; +Cc: ecos-discuss
>>>>> "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
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: [ECOS] Re: TCP/IP Stack for eCos.
@ 1999-10-04 9:50 Gordy Perkins
1999-10-04 11:53 ` William Gatliff
0 siblings, 1 reply; 12+ messages in thread
From: Gordy Perkins @ 1999-10-04 9:50 UTC (permalink / raw)
To: ecos-discuss
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ECOS] Re: TCP/IP Stack for eCos.
1999-10-04 9:50 Gordy Perkins
@ 1999-10-04 11:53 ` William Gatliff
0 siblings, 0 replies; 12+ messages in thread
From: William Gatliff @ 1999-10-04 11:53 UTC (permalink / raw)
To: ecos-discuss
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.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [ECOS] TCP/IP Stack for eCos.
@ 1999-09-28 22:04 Prakash R
1999-10-04 9:34 ` [ECOS] " Bart Veer
0 siblings, 1 reply; 12+ messages in thread
From: Prakash R @ 1999-09-28 22:04 UTC (permalink / raw)
To: ecos-discuss; +Cc: 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
===========================================================================
^ permalink raw reply [flat|nested] 12+ messages in thread
* [ECOS] Re: TCP/IP Stack for eCos.
1999-09-28 22:04 [ECOS] " Prakash R
@ 1999-10-04 9:34 ` Bart Veer
1999-10-04 14:59 ` Ramana
0 siblings, 1 reply; 12+ messages in thread
From: Bart Veer @ 1999-10-04 9:34 UTC (permalink / raw)
To: rprakash, tgi; +Cc: ecos-discuss
>>>>> "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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ECOS] Re: TCP/IP Stack for eCos.
1999-10-04 9:34 ` [ECOS] " Bart Veer
@ 1999-10-04 14:59 ` Ramana
1999-10-04 15:23 ` Andrew Over
0 siblings, 1 reply; 12+ messages in thread
From: Ramana @ 1999-10-04 14:59 UTC (permalink / raw)
To: bartv; +Cc: ecos-discuss
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ECOS] Re: TCP/IP Stack for eCos.
1999-10-04 14:59 ` Ramana
@ 1999-10-04 15:23 ` Andrew Over
0 siblings, 0 replies; 12+ messages in thread
From: Andrew Over @ 1999-10-04 15:23 UTC (permalink / raw)
To: Ramana; +Cc: bartv, ecos-discuss
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* [ECOS] Re: TCP/IP Stack for eCos
@ 1999-09-24 11:29 Jim Belton
1999-09-28 8:38 ` Tristan Gingold
0 siblings, 1 reply; 12+ messages in thread
From: Jim Belton @ 1999-09-24 11:29 UTC (permalink / raw)
To: eCos Discuss
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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ECOS] Re: TCP/IP Stack for eCos
1999-09-24 11:29 Jim Belton
@ 1999-09-28 8:38 ` Tristan Gingold
0 siblings, 0 replies; 12+ messages in thread
From: Tristan Gingold @ 1999-09-28 8:38 UTC (permalink / raw)
To: ecos-discuss; +Cc: eCos Discuss
> 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.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ECOS] TCP/IP Stack for eCos
@ 1999-05-04 13:51 Jay Lepreau
1999-05-04 17:06 ` Fred Fierling
0 siblings, 1 reply; 12+ messages in thread
From: Jay Lepreau @ 1999-05-04 13:51 UTC (permalink / raw)
To: Fred Fierling; +Cc: ecos-discuss, oskit
> It probably would take very little effort to get the OSKit's TCP/IP
> stack working in eCos, [...]
Do you know if it's a zero copy stack?
Yes, I believe it is but can't swear to it. It's FreeBSD's
implementation with our wrapping code and environment.
Aside:
In Sec 5 of the SOSP paper on our site there's a discussion of a
networking example (ttcp) which might be enlightening in a general
way. In that particular example an extra copy is incurred on the
outgoing path because BSD's scatter/gather `mbufs' in the protocol
component have to be copied into linear `skbuffs' in the (unchanged)
Linux driver component. That is an artifact of the mismatch and would
not apply if you allowed yourself to change the Linux drivers or
provided other drivers. (For maintenance and philosophical reasons,
we generally avoid changing foreign "encapsulated" code in the OSKit.)
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [ECOS] TCP/IP Stack for eCos
1999-05-04 13:51 [ECOS] " Jay Lepreau
@ 1999-05-04 17:06 ` Fred Fierling
1999-05-05 5:15 ` [ECOS] " Bart Veer
0 siblings, 1 reply; 12+ messages in thread
From: Fred Fierling @ 1999-05-04 17:06 UTC (permalink / raw)
To: ecos-discuss
Jay Lepreau wrote:
> > It probably would take very little effort to get the OSKit's TCP/IP
> > stack working in eCos, [...]
I assume it's written in C?
It occurs to me that since eCos is written in C++ that it may be
an idea to write its TCP/IP stack in C++ as well. Thoughts?
^ permalink raw reply [flat|nested] 12+ messages in thread
* [ECOS] Re: TCP/IP Stack for eCos
1999-05-04 17:06 ` Fred Fierling
@ 1999-05-05 5:15 ` Bart Veer
0 siblings, 0 replies; 12+ messages in thread
From: Bart Veer @ 1999-05-05 5:15 UTC (permalink / raw)
To: fff; +Cc: ecos-discuss
>>>>> "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
^ permalink raw reply [flat|nested] 12+ messages in thread
* RE: [ECOS] TCP/IP Stack for eCos
@ 1999-04-26 7:04 Leonard, Niall
1999-04-26 7:39 ` [ECOS] " Bart Veer
0 siblings, 1 reply; 12+ messages in thread
From: Leonard, Niall @ 1999-04-26 7:04 UTC (permalink / raw)
To: 'bartv@cygnus.co.uk'; +Cc: ecos-discuss
Which processors are you currently poring eCos to ?
> -----Original Message-----
> From: Bart Veer [SMTP:bartv@cygnus.co.uk]
> Sent: Monday, April 26, 1999 3:02 PM
> To: fff@microplex.com
> Cc: ecos-discuss@cygnus.com
> Subject: Re: [ECOS] TCP/IP Stack for eCos
>
> >>>>> "Fred" == Fred Fierling <fff@microplex.com> writes:
>
> Fred> Is anyone interested in working on an open TCP/IP stack for
> Fred> eCos?
>
> Cygnus would very much like to see this happen. If nobody else does it
> then sooner or later we will end up doing a port of a suitable stack
> ourselves, but right now we are busy porting to various processors and
> have little spare bandwidth. However we should be able to assist any
> net effort, and several of the team members have experience with
> embedded TCP/IP stacks.
>
> Bart Veer // eCos net maintainer
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~1999-10-04 15:23 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-05-04 4:36 [ECOS] TCP/IP Stack for eCos Jay Lepreau
1999-05-04 12:36 ` Fred Fierling
1999-05-05 5:12 ` [ECOS] " Bart Veer
-- strict thread matches above, loose matches on Subject: below --
1999-10-04 9:50 Gordy Perkins
1999-10-04 11:53 ` William Gatliff
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-04-26 7:04 [ECOS] " Leonard, Niall
1999-04-26 7:39 ` [ECOS] " Bart Veer
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).