public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Mike Arthur" <arth2219@gmail.com>
To: "Loginov Alexander" <aloginov@asmpt.com>
Cc: ecos-discuss@sourceware.org
Subject: Re: [ECOS] Re: Is eCos project still alive?
Date: Thu, 13 Dec 2007 20:06:00 -0000	[thread overview]
Message-ID: <2a3305fe0712130803o40e9f09cy91fcaaf5aff52272@mail.gmail.com> (raw)
In-Reply-To: <AD4B7F937BC23A4BABAF7F2470535E04721C84@aaants96.aaaex.asmpt.com>

> Thanks for your comments. Now a bit clearer why the releases are not
> available. But it is quite strange: there is eCosCentric but no
> releases. Normally the commercial companies that are at the back of the
> open-source project, do this job. Check RTEMS for example.

eCosCentric does contribute to the public CVS repository.  They keep
all of their releases internal to their branched version of eCos,
eCosPro.  The commercial arm of RTEMS (OAR Corporation) has not
branched from RTEMS, so all of their contributions and releases are
within the public tree.


> By the way, do you now any more-or-less free RTOS that provides support
> for privilege levels and process protection?
>

I believe there was some talk on the RTEMS mailing list about getting
something similar to VxWorks' RTPs going within RTEMS.  I don't know
if this ever came to fruition.

Hope this helps,
Mike

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

  parent reply	other threads:[~2007-12-13 16:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13  9:46 Loginov Alexander
2007-12-13  9:50 ` Loginov Alexander
2007-12-13 15:15 ` Grant Edwards
2007-12-13 15:43   ` Chris Zimman
2007-12-13 17:40     ` Grant Edwards
2007-12-14  0:48       ` Bob Koninckx
2007-12-14  1:41         ` Grant Edwards
2007-12-14  6:38           ` Frank Pagliughi
2007-12-14 11:15             ` Chris Zimman
2007-12-14 11:20               ` Andrew Lunn
2007-12-14 12:00                 ` Paul D. DeRocco
2007-12-14 14:28                 ` [ECOS] FSF copyright assignmnett. [Was Re: [ECOS] Re: Is eCos project still alive?] Ilija Koco
2007-12-14 16:21                   ` [ECOS] FSF copyright assignment. " Daniel Morris
2007-12-14 17:11                 ` [ECOS] Re: Is eCos project still alive? Grant Edwards
2007-12-14 18:10                   ` Brian Austin
2007-12-17 11:29                 ` Jonathan Larmour
2007-12-14 16:34             ` Brian Austin
2007-12-14 16:39               ` Sergei Organov
2007-12-14 18:47               ` Grant Edwards
2007-12-13 20:06 ` Mike Arthur [this message]
2007-12-14 13:47 ` Ilija Koco
  -- strict thread matches above, loose matches on Subject: below --
2007-12-14  9:07 Loginov Alexander
2007-12-14  8:28 Loginov Alexander
2007-12-14 11:09 ` Chris Zimman
2007-12-13  4:27 [ECOS] " Loginov Alexander
2007-12-13  6:15 ` [ECOS] " Grant Edwards
2007-12-13  3:31 Loginov Alexander
2007-12-13  8:07 ` Grant Edwards
2007-12-13 15:08   ` Brian Austin
2007-12-13  3:02 Anthony Tonizzo

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=2a3305fe0712130803o40e9f09cy91fcaaf5aff52272@mail.gmail.com \
    --to=arth2219@gmail.com \
    --cc=aloginov@asmpt.com \
    --cc=ecos-discuss@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).