Dear Gilles, Sorry, it's my own mistake. I forgot to append the dev_private when openning the device. I am actually using the TC1 for testing and not TC0 (TC0 is selected for IPIPE usage).
By the way, do we need to invoke the rtdm_irq_enable after the rtdm_irq_request? After excuting the ISR, is that the return of RTDM_IRQ_HANDLED will reenble the interrupt? Please advice. Thanks regards, chun yeow On 8/14/07, Gilles Chanteperdrix <[EMAIL PROTECTED]> wrote: > > Yeoh Chun Yeow wrote: > > Dear all, > > > > I have try to attach a AT91 TC hardware interrupt using > rtdm_irq_request. > > Sorry, I misunderstood your question. No, you can not do that, the TC > hardware is driven by Xenomai in one shot mode, you can not expect it to > tick on a regular basis. Besides, timers (either posix timers or native > alarms) are really what you are looking for. Nevertheless, you should > not get a oops when trying to do that. > > > > > Whenever the rtdm_irq_request is called, the kernel Oops occurs. > > > > Any ideas on the problem? > > > Either a programming error, or a bug in Xenomai. Could you show us the > code that triggers this behaviour ? Did you enable support for shared > IRQs in Xenomai ? The TC irq has to be shared in Xenomai domain, since > it is used by Xenomai and you also want to use it. > > -- > > > Gilles Chanteperdrix. >
_______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
