The eCos, QNX, ChorusOs irq handling API

[joel.sherrill at OARcorp.com (Joel Sherrill)]

Chris Johns wrote:
> 
> 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.

This is the better way I think.  I would expect to possibly see device
driver 
resources allocated and freed in the following pairings:

  + driver initialize and unregister
  + open and close
  + interrupt installation and removal

IMO those are the naturally symmetrical places to do it.

> --
>   Chris Johns, cjohns at cybertec.com.au

-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel at OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985