public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Anthony Tonizzo" <atonizzo@gmail.com>
To: "eCos Disuss" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: Is eCos project still alive?
Date: Thu, 13 Dec 2007 03:02:00 -0000	[thread overview]
Message-ID: <b437ec690712121854j6ec85541h4f644547e9afb3da@mail.gmail.com> (raw)

Alexander:

> Although I see some activity on eCos
> mailing lists, it doesn't bring a peace to my mind. What happened to
> eCos? It used to be very active in early 00. Why its releases are not
> updated? It is quite strange, that ecoscentric commercially distributes
> a product that is so old.

Some activity, ah?

How much time did you actually spend researching the subject before
posting your questions on the mailing list?

If you had your homework, you would have found out that eCos is very
much alive, and that snapshots of the latest development tree are issued
every week, not every month or every year. If you had spent more than a
passing moment on the web site of the fine people at eCosCentric you
would have found that under the "DevZone" tab there is menu called
Snapshots. Do you care to guess where that leads you?

And if you had spent more than a passing moment actually _reading_
the mailing lists you would have found that people keep posting patches
almost every day, not only making old packages even better, but
also adding new ones.

> 2) eCOS doesn't distinguish between privilege levels. Is there any way
> to enable it for x86 platform? We need to keep user applications away
> from the control system core that we would like to run in Ring 0.

That assumes that you have full support for an MMU. Ecos' use of MMU
is limited to static configuration of MMUs, even in those architectures
that actually have an MMU built in. Don't blame eCos for missing MMU
support: This is a carefully thought decision on the part of the eCos
architects. Remember that we are talking about real time systems,
where dynamic manipulation of an MMU is not such a great idea.

If you need a full MMU, Linux is your OS.

T

-- 
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:[~2007-12-13  2:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13  3:02 Anthony Tonizzo [this message]
2007-12-13  3:31 Loginov Alexander
2007-12-13  8:07 ` Grant Edwards
2007-12-13 15:08   ` Brian Austin
2007-12-13  4:27 [ECOS] " Loginov Alexander
2007-12-13  6:15 ` [ECOS] " Grant Edwards
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 17:11                 ` 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
2007-12-14 13:47 ` Ilija Koco
2007-12-14  8:28 Loginov Alexander
2007-12-14 11:09 ` Chris Zimman
2007-12-14  9:07 Loginov Alexander

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=b437ec690712121854j6ec85541h4f644547e9afb3da@mail.gmail.com \
    --to=atonizzo@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).