From: Gary Thomas <gary@mlbassoc.com>
To: Anders Olsen <aol@sagio.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] FW: eCOsPro - is it worth the money
Date: Mon, 07 Apr 2008 17:10:00 -0000 [thread overview]
Message-ID: <47FA4F01.60400@mlbassoc.com> (raw)
In-Reply-To: <A6938609E8A8144F94CC44166371CAB558C392@saturn-v.sagiooffice.local>
Anders Olsen wrote:
>
> Hi
>
> We're small development team looking at the eCOS OS. As far as we can
> see, the source code available in the CVS is quite old and we have to
> buy the eCOSPro package from eCosCentric in order to get sourcecode
> there is up-to-date.
I beg to differ; the CVS is fully up to date. There may be offerings
(targets and features) which eCosPro has that aren't available, but
AFAIK, nothing that makes the CVS out of date...
> Is the eCOSPro worth the money or not....
It depends. eCosPro would be indicated if:
* You need a target or feature that they provide not in CVS
* You want paid technical support
What target are you looking at?
What features do you need?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2008-04-07 16:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 16:31 Anders Olsen
2008-04-07 17:10 ` Gary Thomas [this message]
2008-04-07 17:18 ` Anders Olsen
2008-04-08 6:57 ` Tom Deconinck
2008-04-08 8:37 ` Anders Olsen
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=47FA4F01.60400@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=aol@sagio.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).