* [ECOS] Interrupt vectors
@ 2004-06-12 14:47 David Brennan
0 siblings, 0 replies; only message in thread
From: David Brennan @ 2004-06-12 14:47 UTC (permalink / raw)
To: eCos Discussion List
I am currently trying to implement a device driver for the Tundra
Universe chip. I have everything working, except I want to be able to
have the user program install interrupts off the chip. The main hardware
interrupt function would be the same for all. But the chip can generate
7 interrupts, each with 256 vectors. Is there a good way within the eCos
infra structure to handle this? I am porting this from VxWorks. On that
platform, the "device driver" provided a mechanism to translate the
interrupt/vector combination into a unique interrupt number that the
user routine attached to. Then I assume the hardware interrupt decodes
the interrupt data and does a software interrupt call to the user
routine. For my actual application, I will not need nearly that many
interrupts. I'm just not sure what the best way to handle this type of
situation is.
Thanks
David Brennan
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-06-12 14:47 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-06-12 14:47 [ECOS] Interrupt vectors David Brennan
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).