right, i think i see it.

Up to and including kernel version 3.6 there was no handle_irq abstraction:
https://github.com/raspberrypi/linux/blob/rpi-3.2.27/arch/arm/mach-bcm2708/bcm2708.c

handle_irq was introduced in 3.8 and as such this is not getting patched.


On 27 February 2014 21:15, Gilles Chanteperdrix <
[email protected]> wrote:

> On 02/27/2014 09:33 PM, Gregory Dymarek wrote:
> > Not sure if I understand this. This is the first call to
> __report_bad_irq (
> >
> https://github.com/raspberrypi/linux/blob/rpi-3.8.y/kernel/irq/spurious.c)
> >
> > I added the trace on line 192.
> >
> > AFAIK this is the first call to the function. the trace freeze i added is
> > not conditional.
>
> I am looking at the "post" patch for Raspberry, and I do not see that
> it touches drivers/irqchip/irq-bcm2835.c
>
> Here the calls to handle_IRQ are not replaced with ipipe calls, this
> can not work.
>
> See:
>
> http://www.xenomai.org/index.php/I-pipe-core:ArmPorting#Interrupt_controller
>
> --
>                                                                 Gilles.
>
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai

Reply via email to