public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001572] New: Separate FIQ and IRQ management
Date: Mon, 23 Apr 2012 16:22:00 -0000	[thread overview]
Message-ID: <bug-1001572-13@http.bugs.ecos.sourceware.org/> (raw)

Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001572

           Summary: Separate FIQ and IRQ management
           Product: eCos
           Version: CVS
          Platform: All
        OS/Version: ARM
            Status: NEW
          Severity: enhancement
          Priority: low
         Component: HAL
        AssignedTo: unassigned@bugs.ecos.sourceware.org
        ReportedBy: nickg@ecoscentric.com
                CC: ecos-bugs@ecos.sourceware.org
             Class: Advice Request


Created an attachment (id=1712)
 --> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1712)
FIQ patch

This patch implements the separation of FIQ and IRQ in eCos critical sections.
The default is to continue disabling both FIQ and IRQ as at present. If
CYGOPT_HAL_ARM_FIQ_DISABLE is switched off then eCos will only manipulate IRQs
in HAL_DISABLE|ENABLE|RESTORE_INTERRUPTS FIQs will be untouched. This puts FIQs
entirely outside eCos, they cannot interact with the kernel through standard
means, and any FIQ handler must be written to run directly from the VSR, it
cannot be installed via the usual interrupt API.

To make FIQs easy to control, if FIQ and IRQ are separated, a set of FIQ
control macros, HAL_DISABLE|ENABLE|RESTORE|QUERY_FIQ, are enabled.


I'll check this in in a few days if nobody has any objections.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-04-23 16:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 16:22 bugzilla-daemon [this message]
2012-04-23 16:30 ` [Bug 1001572] " bugzilla-daemon
2012-04-23 19:39 ` bugzilla-daemon
2012-04-24  9:53 ` bugzilla-daemon
2012-05-11 10:36 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2012-04-23 16:22 [Bug 1001572] New: " bugzilla-daemon

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=bug-1001572-13@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-bugs@ecos.sourceware.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).