[okl4-developer] Interrupts

Sebastian Huß sebastian.huss at opensynergy.com
Tue Jun 3 01:50:49 EST 2008


Hi Geoffrey,

> In the latest OKL4 2.1 release the interrupts are normally assigned
> statically at build time.  You do this by editing the machines.py 
> file located in platforms/*/tools/machines.py.

Does this mean, the functions like hardware_register_interrupt() or
the corresponding low-level L4-Calls won't work?

> In OKL4 2.1 we migrated the interrupt IPC model from being synchronous
> to asynchronous, but the old IRQ handler was left lying around, which
> I think is the cause of some of your confusion.  Take a look 
> at the vserial_async_handler() in the vserial driver which should
> hopefully clear things up.

Well, the part in the idl4 [async_handler] is clear, but the problem is
now how to get correctly registered for interrupts using machines.py
For my raw testing purposes I hacked my code into the vserial_async_handler()
And used the corresponding interrupt, but that's no real solution.

Regards
Sebastian





More information about the Developer mailing list