Re: [Xenomai-core] Registering MSI interrupt with Xenomai fails

2007-11-02 Thread Philippe Gerum
Jeroen Van den Keybus wrote: > > Now looking into xnintr_attach(). > > > In xnintr_attach(), the crash occurs in xnarch_set_irq_affinity(). If > the call is removed, the driver works as expected (gaining another 3 > usec of latency). Now investigating ipipe_set_irq_affinity. > arch_

Re: [Xenomai-core] Registering MSI interrupt with Xenomai fails

2007-11-02 Thread Jeroen Van den Keybus
> > > Now looking into xnintr_attach(). > In xnintr_attach(), the crash occurs in xnarch_set_irq_affinity(). If the call is removed, the driver works as expected (gaining another 3 usec of latency). Now investigating ipipe_set_irq_affinity. Jeroen. > > > Jeroen. > __

Re: [Xenomai-core] Registering MSI interrupt with Xenomai fails

2007-11-02 Thread Philippe Gerum
Jeroen Van den Keybus wrote: > We have a driver that operates on a PCIe card. The card has IRQ17. If we > use it like that (IO-APIC-fasteoi), interrupt registration using > rtdm_irq_request works correctly. (We also use rtdm_irq_enable > afterwards, but it seems that the request already enables the

[Xenomai-core] Registering MSI interrupt with Xenomai fails

2007-11-02 Thread Jeroen Van den Keybus
We have a driver that operates on a PCIe card. The card has IRQ17. If we use it like that (IO-APIC-fasteoi), interrupt registration using rtdm_irq_request works correctly. (We also use rtdm_irq_enable afterwards, but it seems that the request already enables the interrupt.) However, if we redefine