From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21974 invoked by alias); 24 Jun 2005 20:06:23 -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 21961 invoked by uid 22791); 24 Jun 2005 20:06:19 -0000 Received: from nproxy.gmail.com (HELO nproxy.gmail.com) (64.233.182.197) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 24 Jun 2005 20:06:19 +0000 Received: by nproxy.gmail.com with SMTP id d4so104181nfe for ; Fri, 24 Jun 2005 13:06:17 -0700 (PDT) Received: by 10.48.144.8 with SMTP id r8mr66886nfd; Fri, 24 Jun 2005 13:06:17 -0700 (PDT) Received: by 10.48.43.13 with HTTP; Fri, 24 Jun 2005 13:06:17 -0700 (PDT) Message-ID: <69dd805e05062413066cd6a188@mail.gmail.com> Date: Fri, 24 Jun 2005 20:06:00 -0000 From: Fabian Scheler Reply-To: Fabian Scheler To: R Vamshi Krishna Cc: ecos-discuss@sources.redhat.com In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Subject: Re: [ECOS] OSEK compliance in eCos X-SW-Source: 2005-06/txt/msg00255.txt.bz2 Hi, 1. As I already mentioned in a different thread, eCos is an operating system usable also for hard real time systems. 2. When implement an OSEK compliance layer on top of eCos, how should this eCos-based OSEK layer now be capable of doing hard real time? It is still the same operating system kernel. 3. It might be quite hard to implement just an OSEK compliance layer. You have to implement at least a different thread queue: the OSEK/VDX standard demands that TASKs are activatanle several times and the activation order has to be preserved. It might also get very tricky to implement resources on ISR level and adopt the interrupt synchronization mechanism. 4. The real strenght of OSEK based systems is, that you not just configure the runtime system, like this is the case with eCos, but a complete application. This makes it possible to generate an operating system that perfectly suites the needs of an application (you might wonder how many possiblities there are to optimize the implementation of an operating system kernel, even if it is as simple as OSEK is). Ciao, Fabian -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss