From: Colin Ford <colin.ford@pipinghotnetworks.com>
To: Ecos Mailing List <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Interrupts In MIPS....?
Date: Tue, 03 Oct 2000 09:09:00 -0000 [thread overview]
Message-ID: <39DA048B.23FEA384@pipinghotnetworks.com> (raw)
Hello,
I've got a bit of a design question. Eventually I want
to service all types of interrupts i.e. Ethernet, DMA,
MII, UART, PCI etc.
The problem I have is that all of these interrupts latch
up to a bit in the "cause" register. Now the question
I have is should I change the "hal_interrupt_handler" to
call another handler to then check which actual
peripheral caused the interrupt which in turn calls the
devices ISR or should I go about it in a different way.
I don't really know the philosophy of eCos enough to
know what would be the best course of action?
Any advice?
Cheers,
Col.
--
===========================================
Colin Ford PipingHot Networks
Software Engineer +44 (0)1364 655510
next reply other threads:[~2000-10-03 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-03 9:09 Colin Ford [this message]
2000-10-06 5:15 ` Nick Garnett
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=39DA048B.23FEA384@pipinghotnetworks.com \
--to=colin.ford@pipinghotnetworks.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).