[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
The eCos, QNX, ChorusOs irq handling API
- Date: Wed, 19 Feb 2003 16:59:19 -0500 (EST)
- From: gregory.menke at gsfc.nasa.gov (gregory.menke at gsfc.nasa.gov)
- Subject: The eCos, QNX, ChorusOs irq handling API
Valette Eric writes:
> The one I prefer. I wrote it years ago and RTEMS one can be seen as a
> second iteration... API is at least still processor dependent :-)
> They have indeed added the void* argument, suppressed the isOn routine
> (probably because one can assume that irq is enabled if a vector is
> connected which is not always true?) and I would follow them...
I would prefer to keep the semantics of setting a vector and then
allowing the interrupt itself to be disabled- the RTEMS task interrupt
level provides a means of controlling the set of enabled interrupts on
a per task basis. Its not been useful to me yet, but I'd hate to
loose functionality in an enhancement.