public inbox for elix@sourceware.org
 help / color / mirror / Atom feed
From: Stuart Hughes <sehughes@zentropix.com>
To: Bhushit Joshipura <bhushit@hotmail.com>
Cc: nickg@cygnus.co.uk, elix@sourceware.cygnus.com
Subject: Re: From darkness of ignorance
Date: Tue, 28 Dec 1999 04:44:00 -0000	[thread overview]
Message-ID: <3868AFC4.139104CE@zentropix.com> (raw)
In-Reply-To: <19991225050922.7149.qmail@hotmail.com>

Bhushit Joshipura wrote:
> 
> Hello all,
> 
> Please put me to right track for the following bunch of thoughts:
> 
> 0. Till now it was embedded and if had an OS, it had to be RT
> 1. Then we had WindowCE and RT blurred
> 2. And there are more non-realtime, priority based OS's emerging: PalmOS is
> one more to consider. Till now Palm has not gone 'out of hand' but may go
> anytime
> 3. Thus 'embedded' is getting bigger than 'RT' and calls for precise lining.
> Soon we will be engulfed with products which are embedded but not so much RT
> 
> So, you must feel OK with the following points:
> 0. RTOS are going to become (or HAVE become) part of embedded OS
> 1. API fixation of embedded OS thus have to consider 'slimming down' as
> priority
> 2. RT API will be just a special case of embedded API
> 
> In this light, may I now ask the question:
> Which API standardization are we discussing in this group? Embedded or RT?
> 
> -Bhushit Joshipura


Hi Bhushit,

I think EL/IX can serve both the embedded and RT world.  In many cases,
as you say yourself the line can be blurred.  I feel it should be
possible for deterministic hard real-time OS's to provide a method to
conform to at least a subset of the EL/IX specification.  

For these reasons, I think this list is an appropriate place to discuss
the API for all systems seeking to provide some level of compliance,
including RT systems.

Regards, Stuart

      reply	other threads:[~1999-12-28  4:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-24 21:09 Bhushit Joshipura
1999-12-28  4:44 ` Stuart Hughes [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=3868AFC4.139104CE@zentropix.com \
    --to=sehughes@zentropix.com \
    --cc=bhushit@hotmail.com \
    --cc=elix@sourceware.cygnus.com \
    --cc=nickg@cygnus.co.uk \
    /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).