[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
The eCos, QNX, ChorusOs irq handling API
- Date: Fri, 21 Feb 2003 10:00:50 +1100
- From: cjohns at cybertec.com.au (Chris Johns)
- Subject: The eCos, QNX, ChorusOs irq handling API
till wrote:
> On the point of driver unloding: I absolutely agree with Sergei on that
> this is NOT the job of irqOff.
I think this is covered in PR127. IMO driver resources should be handled via the
unregister and/or close calls.
--
Chris Johns, cjohns at cybertec.com.au
- References:
- The eCos, QNX, ChorusOs irq handling API
- From: eric.valette at free.fr (Valette Eric)
- The eCos, QNX, ChorusOs irq handling API
- From: osv at javad.ru (Sergei Organov)
- The eCos, QNX, ChorusOs irq handling API
- From: eric.valette at free.fr (Valette Eric)
- The eCos, QNX, ChorusOs irq handling API
- From: osv at javad.ru (Sergei Organov)
- The eCos, QNX, ChorusOs irq handling API
- From: eric.valette at free.fr (Valette Eric)
- The eCos, QNX, ChorusOs irq handling API
- From: osv at javad.ru (Sergei Organov)
- The eCos, QNX, ChorusOs irq handling API
- From: eric.valette at free.fr (Valette Eric)
- The eCos, QNX, ChorusOs irq handling API
- From: strauman at slac.stanford.edu (till)