From: Jonathan Larmour <jlarmour@redhat.com>
To: Arnaud Mouiche <arnaud.mouiche@inventel.fr>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] FIQ on ARM processor
Date: Thu, 16 Aug 2001 07:51:00 -0000 [thread overview]
Message-ID: <3B7BDE04.2593077E@redhat.com> (raw)
In-Reply-To: <5.0.2.1.0.20010816163127.00b1db70@193.54.84.101>
Arnaud Mouiche wrote:
>
> Hi.
>
> when reading vector.s, it looks like ecos deal with FIQ like it deals with
> IRQ. Does it means there is no advantage to use FIQ than IRQ.
Yes there is. FIQs are defined for very fast interrupts. If you choose to
use the "standard" eCos interrupt handling mechanism then this somewhat
defeats this, so there is no point eCos trying to handle FIQ differently.
But you can still attach your own VSR (written in assembler) to FIQ.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
next prev parent reply other threads:[~2001-08-16 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 7:46 Arnaud Mouiche
2001-08-16 7:51 ` Jonathan Larmour [this message]
2001-08-16 7:54 ` Andrew Lunn
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=3B7BDE04.2593077E@redhat.com \
--to=jlarmour@redhat.com \
--cc=arnaud.mouiche@inventel.fr \
--cc=ecos-discuss@sourceware.cygnus.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).