From: "R. Vamshi Krishna" <vamshi@cse.iitb.ac.in>
To: Kozo Kakehi <kakehi@kme.co.jp>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS]: Is eCos Hard Real Time OS ??
Date: Fri, 24 Jun 2005 12:54:00 -0000 [thread overview]
Message-ID: <42BC02AC.3070109@cse.iitb.ac.in> (raw)
In-Reply-To: <200506242130.JFG48907@vaio505r.kme.co.jp>
Kozo Kakehi wrote:
>Hello. Vamshi.
>
> I'm a one of user in japan.
>
>in <Pine.LNX.4.61.0506241710050.5855@mars.cse.iitb.ac.in>
> "Re: [ECOS]: Is eCos Hard Real Time OS ??"
> "R Vamshi Krishna <vamshi@cse.iitb.ac.in>" wrote
>
>
>
>>Then what parts do I re-write to make it hard-real time ?
>>Because I want to use eCos but also I need a hard reak-time
>>OS.
>>
>>
>
> Choose eCos is better idea, and fast enough for realtime application.
>
> I don't know how hard real-time you need in your system.
>Where or what is a border about hard vs soft real-time.
>
> In my experience, someone force very hard response to OS, it's a bad design
>about elements (threads, messaging, mutex..) or whole system. In such system,
>may crash cause critical design.
>
> Let's try to use current eCos, just as it is.
>
>
I think I might have given the wrong impression.
I would like to add a compliance layer.
That means that if somebody does not want hard real-time behaviour, he
continue using eCos normally.
But if hard real-time is needed then he will use the alternative. i.e
some specific scheduler, drivers, some
specific API etc ..
>// Kozo Kakehi from Osaka
>// kakehi@kme.co.jp
>
>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-06-24 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 11:07 R Vamshi Krishna
2005-06-24 11:27 ` Andrew Lunn
2005-06-24 11:41 ` R Vamshi Krishna
2005-06-24 12:32 ` Kozo Kakehi
2005-06-24 12:54 ` R. Vamshi Krishna [this message]
2005-06-24 12:38 ` Andrew Lunn
2005-06-24 12:52 ` R. Vamshi Krishna
2005-06-24 13:32 ` Andrew Lunn
2005-06-24 19:52 ` Fabian Scheler
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=42BC02AC.3070109@cse.iitb.ac.in \
--to=vamshi@cse.iitb.ac.in \
--cc=ecos-discuss@sources.redhat.com \
--cc=kakehi@kme.co.jp \
/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).