From: "Chris Zimman" <czimman@bloomberg.com>
To: "Grant Edwards" <grante@visi.com>, <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] On ARM7 can one of FIQ/IRQ be used for non-eCos stuff?
Date: Wed, 02 Apr 2008 16:51:00 -0000 [thread overview]
Message-ID: <F31C1582037F5041B0CD525FD870AE6A774278@ny2545.corp.bloomberg.com> (raw)
In-Reply-To: <ft0dam$o5b$1@ger.gmane.org>
> From looking at the ARM/arch hal stuff, it looks like eCos
> expects to handle both IRQ and FIQ interrupts. AFAICT, all of
> the interrupt sources in my part (Samsung S3C4530) can be
> assigned to either IRQ or FIQ.
>
> Is there any reason why eCos has to have control of both
> interrupt sources if all of the peripherals which eCos is
> handling are on just one of them?
Just change the FIQ vector to point to your handler. I don't know of
anything that uses FIQ right now anyhow.
--Chris
--
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 16:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 16:48 Grant Edwards
2008-04-02 16:51 ` Chris Zimman [this message]
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
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=F31C1582037F5041B0CD525FD870AE6A774278@ny2545.corp.bloomberg.com \
--to=czimman@bloomberg.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=grante@visi.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).