From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: On ARM7 can one of FIQ/IRQ be used for non-eCos stuff?
Date: Wed, 02 Apr 2008 18:48:00 -0000 [thread overview]
Message-ID: <ft0kbs$gb9$1@ger.gmane.org> (raw)
In-Reply-To: <F31C1582037F5041B0CD525FD870AE6A774279@ny2545.corp.bloomberg.com>
On 2008-04-02, Chris Zimman <czimman@bloomberg.com> wrote:
>> However, there quite a few spots in the arm/arch interrupt and
>> exception handling code where FIQ is being disabled. It looks
>> like I'd have to fork the arch code and modify it to prevent
>> it from disabling FIQ.
>
> Yes, there definitely is that issue. It's not too many places
> that have to be updated though.
>
>> I suppose the right thing to do would be to make the arm/arch
>> stuff configurable via CDL so that it would use either FIQ or
>> IRQ or both.
>
> I would think what you'd want to do is to provide a function
> to change the FIQ vector after eCos has started.
That's easy enough, but it'd be trickier to provide a run-time
function to fix the places in vectors.S that are currently
disabling FIQ.
> If you start things without the FIQ vector assigned, and for
> whatever reason it fires, you're in trouble.
True.
> With regards to CDL, I don't know that it would make sense to
> have a CDL option to not have eCos own the FIQ vector on
> startup.
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".
--
Grant Edwards grante Yow! I feel ... JUGULAR ...
at
visi.com
--
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 18:48 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 [this message]
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='ft0kbs$gb9$1@ger.gmane.org' \
--to=grante@visi.com \
--cc=ecos-discuss@sources.redhat.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).