From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21760 invoked by alias); 5 Apr 2005 09:20:49 -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 21611 invoked from network); 5 Apr 2005 09:20:36 -0000 Received: from unknown (HELO ns1.nec.com.au) (147.76.180.1) by sourceware.org with SMTP; 5 Apr 2005 09:20:36 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by ns1.nec.com.au (Postfix) with ESMTP id 9C5D637746; Tue, 5 Apr 2005 19:20:34 +1000 (EST) Received: from ns1.nec.com.au ([127.0.0.1]) by localhost (ns1.nec.com.au [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 02803-02-84; Tue, 5 Apr 2005 19:20:34 +1000 (EST) Received: from smtp2.nec.com.au (smtp2.internal.nec.com.au [172.31.8.19]) by ns1.nec.com.au (Postfix) with ESMTP id 8B0DA37742; Tue, 5 Apr 2005 19:20:34 +1000 (EST) Received: from deer.kts.nec.com.au (localhost.localdomain [127.0.0.1]) by smtp2.nec.com.au (8.12.8/8.12.8) with ESMTP id j359KYPH013348; Tue, 5 Apr 2005 19:20:34 +1000 Received: from dvalin.dd.nec.com.au ([172.31.20.70]) by deer.kts.nec.com.au (8.12.5/8.12.5/Debian-1) with ESMTP id j359KJ7w020369; Tue, 5 Apr 2005 19:20:20 +1000 Received: from dvalin.dd.nec.com.au (localhost [127.0.0.1]) by dvalin.dd.nec.com.au (8.12.3/8.12.3/Debian-5) with ESMTP id j359IfQX005316; Tue, 5 Apr 2005 19:18:41 +1000 Received: (from erik@localhost) by dvalin.dd.nec.com.au (8.12.3/8.12.3/Debian-5) id j359Icuf005314; Tue, 5 Apr 2005 19:18:38 +1000 From: Erik Christiansen Date: Tue, 05 Apr 2005 09:20:00 -0000 To: Nick Garnett Cc: ecos-discuss@ecos.sourceware.org Message-ID: <20050405091838.GE677@dd.nec.com.au> References: <20050404054851.GB842@dd.nec.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040722i Subject: Re: [ECOS] Interrupt-free scheduler X-SW-Source: 2005-04/txt/msg00044.txt.bz2 On Mon, Apr 04, 2005 at 04:57:45PM +0100, Nick Garnett wrote: > What exactly are you trying to do? If you don't have any interrupting > devices, then eCos will run just fine. The task is to provide a uitron API to an existing PPC850 card, which does have interrupting devices. The original OS knows nothing about interrupts. Our ISRs handle all that. If eCos were to fiddle with interrupts, we couldn't just leave the ISRs in place, as part of the port. Fortunately, I've now learned enough about enabling and disabling components in a .ecc file to disable everything that smells of interrupts, and resolve the conflicts. Hopefully eCos will now be unaware of interrupts. > Some things, like timers, will not work, but presumably you have > already allowed for that. Oh yes, the timers. It took several cycles to resolve those conflicts, but with persistence, they're gone too. The application provides timers from a task. As a first cut, I'm kinda hoping to re-use that as is. Although a bit weird, it works like a bought one. Reconfiguring eCos is faster and more robust than recoding all the timer stuff in the application. (You wouldn't want to know the proposed schedule for this. But then, you've probably been there, at least once. ;) Things are now fine up to cyg_user_start(), running on the target. (Just turning on a few LEDs.) Next step is a thread or two, but I'll have to translate the examples to uitron API first. Erik -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss