From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10911 invoked by alias); 7 Jun 2007 04:43:55 -0000 Received: (qmail 10901 invoked by uid 22791); 7 Jun 2007 04:43:54 -0000 X-Spam-Check-By: sourceware.org Received: from outbound05.telus.net (HELO defout.telus.net) (199.185.220.224) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 07 Jun 2007 04:43:53 +0000 Received: from priv-edtnaa05.telusplanet.net ([154.20.174.236]) by priv-edtnes87.telusplanet.net (InterMail vM.7.08.02.00 201-2186-121-20061213) with ESMTP id <20070607044350.BSSZ21019.priv-edtnes87.telusplanet.net@priv-edtnaa05.telusplanet.net>; Wed, 6 Jun 2007 22:43:50 -0600 Received: from [192.168.1.126] (d154-20-174-236.bchsia.telus.net [154.20.174.236]) by priv-edtnaa05.telusplanet.net (BorderWare MXtreme Infinity Mail Firewall) with ESMTP id 61SN9GNBMX; Wed, 6 Jun 2007 22:43:50 -0600 (MDT) From: Daniel Helgason To: Mike Sweeney Cc: ecos-discuss@ecos.sourceware.org In-Reply-To: <1181189324.13729.57.camel@localhost.localdomain> References: <70d4f620706062016s593a05aen95aebfdad3f4ecf@mail.gmail.com> <1181189324.13729.57.camel@localhost.localdomain> Content-Type: text/plain Date: Thu, 07 Jun 2007 11:55:00 -0000 Message-Id: <1181191429.13729.65.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 (2.6.3-2.fc5) Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] HAL_INTERRUPT_ACKNOWLEDGE question X-SW-Source: 2007-06/txt/msg00079.txt.bz2 On Wed, 2007-06-06 at 21:08 -0700, Daniel Helgason wrote: > Generally, interrupts from higher priority sources are masked by the > interrupt controller until HAL_INTERRUPT_ACKNOWLEDGE is called. Oops, I can't believe I said that! I think it makes more sense that interrupts from *lower* priority sources are masked until HAL_INTERRUPT_ACKNOWLEDGE is called. But really, it is target-specific whether higher, lower, or any are released when HAL_INTERRUPT_ACKNOWLEDGE is called. Not that it makes any difference in HALs that don't support nested interrupts but the macro might have to tickle the interrupt controller and make it happy. -- +--------------------------------------------- | Daniel Helgason -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss