Eckart G?hler wrote:
>
> Andrei Konovalov wrote:
> > Hi,
> >
> > In the Linux driver you should not access the interrupt controller
> > directly.
> > The relevant XIntc_* calls are done by arch/ppc/syslib/xilinx_pic.c
> code.
> > E.g. the particular interrupt is unmasked when one calls requ
Andrei Konovalov wrote:
> Hi,
>
> In the Linux driver you should not access the interrupt controller
> directly.
> The relevant XIntc_* calls are done by arch/ppc/syslib/xilinx_pic.c code.
> E.g. the particular interrupt is unmasked when one calls request_irq().
>
> Few more comments below
Hi,
In the Linux driver you should not access the interrupt controller directly.
The relevant XIntc_* calls are done by arch/ppc/syslib/xilinx_pic.c code.
E.g. the particular interrupt is unmasked when one calls request_irq().
Few more comments below.
Thanks,
Andrei
Eckart G?hler wrote:
> Hi,
Hi,
We try to run montavista Linux pro 3.1 on an ml300 like embedded system
on an Virtex V2-Pro system. The system works fine with UART, Xilinx enet
driver (booting with Das U-Boot).
Now we try to implement some custom GPIO driver that must be triggered
from outside interrupts. Polling for data
