From: Andrew Lunn <andrew@lunn.ch>
To: Alexander Neundorf <neundorf@kde.org>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: On ARM7 can one of FIQ/IRQ be used for non-eCos stuff?
Date: Wed, 02 Apr 2008 19:30:00 -0000 [thread overview]
Message-ID: <20080402193008.GE7929@lunn.ch> (raw)
In-Reply-To: <200804022125.19510.neundorf@kde.org>
On Wed, Apr 02, 2008 at 09:25:19PM +0200, Alexander Neundorf wrote:
> On Wednesday 02 April 2008, Grant Edwards wrote:
> ...
> > The main point of the CDL would be to avoid having to fork the
> > arm/arch code. I don't really like maintaining my own separate
> > versions of files unless I absolutely have to. Besides,
> > somebody else might actually want to use the new "feature".
>
> Yes. I think providing an official way how to use the FIQ with lowest possible
> overhead under eCos would be good. Some kind of communication with eCos is
> required I think, e.g. a recommended way how to generate a regular interrupt
> so that if some condition is detected in the FIQ handler a regular ISR can
> overtake.
I've done this before, but it used hardware support.
The Intel StrongARM interrupt controller had a bit you could set to
cause an IRQ interrupt to happen. So in the FIQ you hit this bit and
exit the FIQ. Once interrupts are re-enabled the IRQ goes off and you
are in normal eCos interrupt context.
I don't know of a generic way to do this. There is no standardised
interrupt controller for ARMs.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2008-04-02 19:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 16:48 [ECOS] " Grant Edwards
2008-04-02 16:51 ` Chris Zimman
2008-04-02 17:23 ` [ECOS] " Grant Edwards
2008-04-02 17:39 ` Chris Zimman
2008-04-02 18:48 ` Grant Edwards
2008-04-02 19:21 ` Alexander Neundorf
2008-04-02 19:30 ` Andrew Lunn [this message]
2008-04-02 19:40 ` Grant Edwards
2008-04-02 19:47 ` Andrew Lunn
2008-04-02 21:12 ` Grant Edwards
2008-04-02 19:33 ` Grant Edwards
2008-04-02 19:42 ` Andrew Lunn
2008-04-02 20:23 ` Alexander Neundorf
2008-04-02 20:59 ` Paul D. DeRocco
2008-04-02 21:20 ` Grant Edwards
2008-04-02 18:59 ` Andrew Lunn
2008-04-02 19:27 ` Grant Edwards
2008-04-02 19:35 ` Andrew Lunn
2008-04-02 19:39 ` Grant Edwards
2008-04-02 20:01 ` David Roethig
2008-04-02 20:17 ` Andrew Lunn
2008-04-02 21:15 ` Grant Edwards
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=20080402193008.GE7929@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=neundorf@kde.org \
/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).