public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: "james chen" <james_ch1@sina.com>, <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] eCos API
Date: Wed, 18 Apr 2001 21:37:00 -0000	[thread overview]
Message-ID: <4.3.2.7.2.20010419002249.031d5dc0@mail.larwe.com> (raw)
In-Reply-To: <000d01c0c885$60e1f300$c408aa0a@inc.inventec>

>      Hi, many RTOS e.g. WinCE, Paml, etc. allow user to use it's API to
>develop applications and download it to it's system. Now I want to support

eCos does not support user-installable applications. It is a monolithic, 
statically-linked OS+application.

There are various proprietary ways to solve this, depending on your needs. 
For instance, we have developed a _very_ simple executable file format for 
our platform to allow third parties to develop "plugins" for the OS. 
However these plugins have no access to the eCos APIs and in fact the same 
plugin API is implemented both on the eCos and non-eCos products. We have a 
jump table at a known location in ROM, and a few system variables at known 
locations in RAM, and that's how "plugins" access APIs (filesystem stuff 
mostly) in our application. It is all very modal - our application runs 
entirely in a single thread, and when a "plugin" is executed, control of 
the system is surrendered entirely to that plugin - i.e. the application 
jumps into the plugin.

=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/

"... a man who is endowed with real qualities of leadership will be tempted 
to refrain from taking part in political life; because [...] the situation 
does not call for a man who has a capacity for constructive statesmanship 
but rather for a man who is capable of bargaining for the favour of the 
majority. Thus the situation will appeal to small minds and will attract 
them accordingly."

  reply	other threads:[~2001-04-18 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18 21:00 james chen
2001-04-18 21:37 ` Lewin A.R.W. Edwards [this message]
2001-04-19  7:43   ` Grant Edwards
2001-04-19 23:50     ` Fredrik Hederstierna
2001-04-19 23:57   ` Chris Gray
2001-04-20  0:06     ` Jonathan Larmour
2001-04-20  6:22     ` Lewin A.R.W. Edwards
2001-04-19  1:01 Nielsen Linus

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=4.3.2.7.2.20010419002249.031d5dc0@mail.larwe.com \
    --to=larwe@larwe.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=james_ch1@sina.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).