public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Anders Olsen" <aol@sagio.com>
To: "Tom Deconinck" <t.deconinck@gmail.com>, 	<ecos-discuss@sourceware.org>
Subject: RE: [ECOS] FW: eCOsPro - is it worth the money
Date: Tue, 08 Apr 2008 08:37:00 -0000	[thread overview]
Message-ID: <A6938609E8A8144F94CC44166371CAB558C394@saturn-v.sagiooffice.local> (raw)
In-Reply-To: <e37cb5250804072347o5e41f7d8o408a890b14a91ac@mail.gmail.com>

 Hi

Thanks - We will try this...


Anders

-----Original Message-----
From: Tom Deconinck [mailto:t.deconinck@gmail.com] 
Sent: 8. april 2008 08:48
To: Anders Olsen; ecos-discuss@sourceware.org
Subject: Re: [ECOS] FW: eCOsPro - is it worth the money

Flash V2 is available in CVS on it's own branch.
You can easily merge in those changes with the latest trunk sources.

Just checkout the latest from the trunk and replace the following
directories with their flash_v2 counterparts:
io/flash
dev/flash
redboot
fs/jffs2

Tom

On Mon, Apr 7, 2008 at 7:13 PM, Anders Olsen <aol@sagio.com> wrote:
>
>  The target is a ST based ARM (STR71x  ARM7TDMI). Well we have the 
> eCOS  running on the target basically en has started writing drivers 
> for our  platform (I2C, SPI, , Realtime, Atmel Dataflash...)
>
>
>  But when looking at the JIFFS2 filesystem, it requires Flash drivers
V2.
>  But Flash driver V2 seams not to be available in the CVS.
>
>
>  Another point by eCOSPro is that i contains a more stable version of 
> the
>  JIFFS2 filesystem, than the one available  through CVS.
>
>
>
>  Anders
>
>
>
>
>
>  -----Original Message-----
>  From: Gary Thomas [mailto:gary@mlbassoc.com]
>  Sent: 7. april 2008 18:43
>  To: Anders Olsen
>  Cc: ecos-discuss@ecos.sourceware.org
>  Subject: Re: [ECOS] FW: eCOsPro - is it worth the money
>
>  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
>
>

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2008-04-08  8:16 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
2008-04-07 17:18   ` Anders Olsen
2008-04-08  6:57     ` Tom Deconinck
2008-04-08  8:37       ` Anders Olsen [this message]

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=A6938609E8A8144F94CC44166371CAB558C394@saturn-v.sagiooffice.local \
    --to=aol@sagio.com \
    --cc=ecos-discuss@sourceware.org \
    --cc=t.deconinck@gmail.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).