public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Re: eCos (non-pro) roadmap ?
Date: Mon, 20 Nov 2017 15:54:00 -0000	[thread overview]
Message-ID: <ouutq6$k9l$1@blaine.gmane.org> (raw)
In-Reply-To: <c8ffd55f-97fc-252e-73a0-476c2d161ec2@kuantic.com>

On 2017-11-20, Bernard Fouché <bpfl@kuantic.com> wrote:

> is there any chance to get any roadmap regarding the public version of 
> eCos ? At my company we are at a cross-road for our new design, we can 
> continue with eCos if there is a visible future (at least an updated 
> toolchain for instance) however it seems that the overall activity on 
> the public version is close to zero for the last couple of years.

I would not recommed it for new designs.

AFAICT, there is no development being done on the public version.

The most recent change in the CVS repository was over 2-1/2 years ago,
and only a handful of changes have been committed in the past 4 years.

$ ls -ltr $(find . -name ChangeLog) | tail -n20
-rw-r--r-- 1 grante users   4923 Jul  1  2013 ./devs/disk/generic/mmc/current/ChangeLog
-rw-r--r-- 1 grante users   1974 Jul  2  2013 ./hal/cortexm/kinetis/twr_k60f120m/current/ChangeLog
-rw-r--r-- 1 grante users   3496 Jul  9  2013 ./devs/spi/freescale/dspi/current/ChangeLog
-rw-r--r-- 1 grante users   1968 Aug 11  2013 ./hal/cortexm/stm32/stm32f4discovery/current/ChangeLog
-rw-r--r-- 1 grante users  38491 Aug 25  2013 ./language/c/libm/current/ChangeLog
-rw-r--r-- 1 grante users  10423 Aug 28  2013 ./io/common/current/ChangeLog
-rw-r--r-- 1 grante users   8701 Aug 28  2013 ./io/can/current/ChangeLog
-rw-r--r-- 1 grante users   3433 Sep 11  2013 ./hal/arm/lpc2xxx/olpcl2294/current/ChangeLog
-rw-r--r-- 1 grante users  81086 Sep 11  2013 ./ChangeLog
-rw-r--r-- 1 grante users   6660 Sep 18  2013 ./devs/can/arm/lpc2xxx/current/ChangeLog
-rw-r--r-- 1 grante users  14952 Mar  3  2014 ./hal/cortexm/stm32/var/current/ChangeLog
-rw-r--r-- 1 grante users 164188 Mar 13  2014 ./kernel/current/ChangeLog
-rw-r--r-- 1 grante users  60647 Mar 16  2014 ./hal/arm/arch/current/ChangeLog
-rw-r--r-- 1 grante users  59237 Mar 22  2014 ./hal/powerpc/arch/current/ChangeLog
-rw-r--r-- 1 grante users   7606 May  3  2014 ./hal/cortexm/kinetis/var/current/ChangeLog
-rw-r--r-- 1 grante users   7350 Jun  6  2014 ./hal/cortexm/arch/current/ChangeLog
-rw-r--r-- 1 grante users  15440 Jun 16  2014 ./isoinfra/current/ChangeLog
-rw-r--r-- 1 grante users  21868 Jul  3  2014 ./language/c/libc/stdio/current/ChangeLog
-rw-r--r-- 1 grante users  19706 Oct  3  2014 ./hal/synth/arch/current/ChangeLog
-rw-r--r-- 1 grante users   2730 Apr 29  2015 ./hal/misc/freescale/edma/current/ChangeLog

-- 
Grant Edwards               grant.b.edwards        Yow! MMM-MM!!  So THIS is
                                  at               BIO-NEBULATION!
                              gmail.com            


-- 
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:[~2017-11-20 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20  9:31 [ECOS] " Bernard Fouché
2017-11-20 15:54 ` Grant Edwards [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='ouutq6$k9l$1@blaine.gmane.org' \
    --to=grant.b.edwards@gmail.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).