public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Helgason <danielh@telus.net>
To: Mike Sweeney <msweeney77@gmail.com>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] HAL_INTERRUPT_ACKNOWLEDGE question
Date: Thu, 07 Jun 2007 11:55:00 -0000	[thread overview]
Message-ID: <1181191429.13729.65.camel@localhost.localdomain> (raw)
In-Reply-To: <1181189324.13729.57.camel@localhost.localdomain>

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 <danielh@telus.net>



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2007-06-07  4:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07  9:14 Mike Sweeney
2007-06-07 10:01 ` Daniel Helgason
2007-06-07 11:55   ` Daniel Helgason [this message]
2007-06-07 15:11 ` Nick Garnett
2007-06-07 17:02   ` Mike Sweeney

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=1181191429.13729.65.camel@localhost.localdomain \
    --to=danielh@telus.net \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=msweeney77@gmail.com \
    /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).