PowerPC exceptions and interrupts

[Till Straumann]

I haven't studied all the details yet
but agree with some of Pavel's comments.

In particular, I also think it is important
that the 'remove' routine be passed the user
argument in addition to the handler.

Another thing that rang my bells was the
lazy-init of the 'bsp_interrupt_mutex' which
is not thread safe in its current form. I do
these e.g., like this:

if ( ! mutex  ) {
     tmp_mutex = create_mutex();
     irq_disable();
          if ( !mutex ) {
              mutex = tmp_mutex;
              irq_enable();
          } else {
              /* somebody else won */
              irq_enable();
              destroy_mutex(tmp_mutex);
          }
}
take_mutex(mutex);

-- Till

Sebastian Huber wrote:
> Hi,
> here is my proposal for a unified interrupt API and the support code. 
> The aim was to provide a clean interface and convenience for the BSP 
> developer for a wide range of boards. You may have a look at 
> bsp-irq/index.html in the documentation:
>
> http://rapidshare.com/files/116211100/bsp-irq.tgz.html
>
> I'am sorry for this download link.
>
> Thanks,
>     Sebastian
>
> --------------------------------------------
> embedded brains GmbH
> Sebastian Huber           Obere Lagerstr. 30
> D-82178 Puchheim          Germany
> Tel. : +49-89-18 90 80 79-6
> Fax  : +49-89-18 90 80 79-9
> email: Sebastian.Huber at embedded-brains.de
> PGP public key available on request
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.com
> http://rtems.rtems.org/mailman/listinfo/rtems-users
>