From: Robin Farine <acnrf@dial.eunet.ch>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] sa11x0 spurious interrupts
Date: Tue, 13 Feb 2001 01:19:00 -0000 [thread overview]
Message-ID: <867l2vuel3.fsf@halftrack.hq.acn-group.ch> (raw)
Hello,
While looking at the way the sa11x0 hal's routine 'hal_IRQ_handler()' decodes
interrupt sources, I noticed that when it does not find an interrupt source,
the routine returns CYGNUM_HAL_INTERRUPT_NONE, which equals to -1 for this
platform. However, the common ARM code in "vectors.S" assumes that a spurious
interrupt always have the vector #0. And worse, 'handle_IRQ_or_FIQ' will call
'hal_interrupt_handlers[-1]' which contains 0 and thus reboot!
Did I miss something?
Thanks,
Robin
next reply other threads:[~2001-02-13 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 1:19 Robin Farine [this message]
2001-02-13 9:18 ` Jonathan Larmour
2001-02-13 9:56 ` Gary Thomas
2001-02-13 10:10 ` Jonathan Larmour
2001-02-13 10:13 ` Gary Thomas
2001-02-13 11:06 ` Robin Farine
2001-02-13 10:09 ` Robin Farine
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=867l2vuel3.fsf@halftrack.hq.acn-group.ch \
--to=acnrf@dial.eunet.ch \
--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).