public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
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 21:20:00 -0000	[thread overview]
Message-ID: <ft0t37$pa2$3@ger.gmane.org> (raw)
In-Reply-To: <PGEAIGBPLOMOJDAPCOJHOEEOKJAB.pderocco@ix.netcom.com>

On 2008-04-02, Paul D. DeRocco <pderocco@ix.netcom.com> wrote:
>> From: Grant Edwards
>>
>> 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.
>
> I think the issue is that there are lots of small critical sections
> scattered all over the place that mask interrupts in the CPU, and they
> currently mask both IRQ and FIQ. For the ARM, HAL_*_INTERRUPTS uses 0xC0 to
> manipulate both these bits. If all eCos ISRs are invoked via IRQ, and FIQ is
> reserved for a special bit of driver code that merely adds functionality to
> a piece of hardware (like adding a FIFO to a serial port) without invoking a
> DSR, then these macros really ought to use 0x80 instead. That would be a
> useful CDL option.

Exactly.  We can leave the FIQ handler code there, and just
overried it by pointing the VSR table entry elsewhere. But, the
places (e.g. in vectors.S) that are disabling and enabling
FIQ+IRQ need to be changed so that they only disable/enable
the right one(s).

-- 
Grant Edwards                   grante             Yow! WHOA!!  Ken and Barbie
                                  at               are having TOO MUCH FUN!!
                               visi.com            It must be the NEGATIVE
                                                   IONS!!


-- 
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:[~2008-04-02 21:20 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
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 [this message]
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='ft0t37$pa2$3@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).