From: "David J. Fiddes" <D.J@fiddes.surfaid.org>
To: <ecos-discuss@cygnus.com>
Subject: RE: [ECOS] Network Support
Date: Fri, 12 Feb 1999 19:57:00 -0000 [thread overview]
Message-ID: <000601be56d7$dac8c260$2a84c389@escom.fiddes-enterprises.com> (raw)
In-Reply-To: < 6006B52C37ABD211AB0900805FFE9D79169230@saturn.sg.adisys.com.au >
Hi,
> I had a quick look, it seems the development tools are ADA based
> and you can
> only access the on-line docs if you are a support customer. Doesn't sound
> very open to me. Have I missed something?
Yep. 'fraid so. RTEMS has a C *AND* ADA API. The majority of developers go
the C/C++ route. I'm hoping to get a GNU Pascal binding running at some
point this year.
The docs should be available in the free support section...and are available
in a variety of formats for download... at least I had no problems ;)
The licence is GPL with a single exception that by including the OS header
files you do not automatically place your app under the GPL. Many RTEMS
developers(pretty much 100% volunteers) are regular contributers to binutils
and EGCS just like the Cygnus guys( although not as numerous ;)... how much
more open do you want?
Dave
> > RTEMS (the first(?) Open Source RTOS ;) has a decent TCP/IP stack... and
> > has
> > a *LOT* of MPC860 people using it. I don't think that anyone
> has released
> > a
> > BSP for a generic MPC860 board but I'm sure that getting one together is
> > not
> > that tough.
> > As far as RTOSs go RTEMS is somewhere between eCos and a larger
> RTOS like
> > vxworks for features. Have a look at http://www.oarcorp.com/
> for details.
next prev parent reply other threads:[~1999-02-12 19:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-10 21:23 Zubin Burjor Sethna
[not found] ` < 6006B52C37ABD211AB0900805FFE9D79169230@saturn.sg.adisys.com.au >
1999-02-12 19:57 ` David J. Fiddes [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-30 6:20 [ECOS] network support James Dabbs
2001-01-19 8:41 Fano Ramparany
2001-01-19 9:36 ` Gary Thomas
2001-01-22 6:48 ` Fano Ramparany
2001-01-22 7:13 ` Gary Thomas
2001-01-30 2:52 ` Fano Ramparany
2001-01-30 4:34 ` Gary Thomas
2001-01-30 6:03 ` Fano Ramparany
2001-01-30 6:08 ` Gary Thomas
2001-01-30 6:25 ` Lewin A.R.W. Edwards
2001-01-30 6:31 ` Gary Thomas
2001-01-30 6:43 ` Lewin A.R.W. Edwards
2001-02-13 5:55 ` Fano Ramparany
2001-02-13 6:20 ` Gary Thomas
2001-02-14 2:44 ` Fano Ramparany
2001-02-14 5:08 ` Gary Thomas
2001-02-14 7:59 ` Fano Ramparany
2001-02-14 8:24 ` Gary Thomas
2001-02-14 9:12 ` Lewin A.R.W. Edwards
2001-02-14 9:25 ` Gary Thomas
2001-02-14 9:32 ` Lewin A.R.W. Edwards
2001-02-14 9:40 ` Gary Thomas
2001-02-14 10:28 ` Robin Farine
2001-02-15 6:42 ` Fano Ramparany
2001-01-22 7:15 ` Fano Ramparany
1999-02-10 18:37 [ECOS] Network Support Wendell Thompson
1999-02-11 9:45 ` Rick Leir
[not found] ` < 36C2F1F1.63DE@hymarc.com >
1999-02-14 7:02 ` David J. Fiddes
1999-02-09 11:01 Gordon McFadden
[not found] ` < Pine.LNX.4.04.9902090702270.648-100000@mailhost.westsoft-systems.com >
1999-02-10 13:22 ` David J. Fiddes
1999-02-10 21:19 ` Brendan Simon
1999-02-06 13:48 weatp
[not found] ` < 9902069183.AA918326790@mail.syntron.com >
1999-02-08 8:26 ` 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='000601be56d7$dac8c260$2a84c389@escom.fiddes-enterprises.com' \
--to=d.j@fiddes.surfaid.org \
--cc=ecos-discuss@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).