From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32730 invoked by alias); 24 Jun 2005 12:32:07 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 32701 invoked by uid 22791); 24 Jun 2005 12:32:02 -0000 Received: from mfo00.mg.2iij.net (HELO mfo00.mg.2iij.net) (210.130.202.146) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 24 Jun 2005 12:32:02 +0000 Received: MGW MFO00 id j5OCVmdB001591; Fri, 24 Jun 2005 21:31:48 +0900 (JST) Received: MGW MO00 id j5OCV8af019773; Fri, 24 Jun 2005 21:31:08 +0900 (JST) Received: MGW MR01 from delilium.kme.co.jp (delilium.kme.co.jp [210.149.79.10]) id j5OCV7L2002907; Fri, 24 Jun 2005 21:31:07 +0900 (JST) Received: from kmegw.kme.co.jp (mm.kme.co.jp [192.168.1.2]) by delilium.kme.co.jp (8.12.10/8.12.10) with ESMTP id j5OCV26P031544; Fri, 24 Jun 2005 21:31:07 +0900 (JST) (envelope-from kakehi@kme.co.jp) Received: from vaio505r.kme.co.jp ([192.168.6.123]) by kmegw.kme.co.jp (8.12.9/3.7W-nomx) with ESMTP id j5OCV3YO076819; Fri, 24 Jun 2005 21:31:03 +0900 (JST) To: vamshi@cse.iitb.ac.in, ecos-discuss@sources.redhat.com From: Kozo Kakehi References: <20050624112732.GA7187@lunn.ch> In-Reply-To: Message-Id: <200506242130.JFG48907@vaio505r.kme.co.jp> Date: Fri, 24 Jun 2005 12:32:00 -0000 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [ECOS]: Is eCos Hard Real Time OS ?? X-SW-Source: 2005-06/txt/msg00236.txt.bz2 Hello. Vamshi. I'm a one of user in japan. in "Re: [ECOS]: Is eCos Hard Real Time OS ??" "R Vamshi Krishna " 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. // 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