Ferry

> ELKS requires the hardware INT 0 timer in order to multitask applications, as well as the kernel counting down registered timeouts, which in this case ends up calling kbd_timer....

> Now that I think of it, the hardware timer issue may be that the PIC mask is not set to allow the interrupt. The kernel keeps certain masks the...

The only place I can find any "masks" are in arch/i86/kernel/irq-8259.c... which uses them for enable_irq() and disable_irq()... that said, I'm not using that file.. I have a custom irq-solo86.c....

Is it useful to send you a URL to the changes?

The code in irqtab.S doesn't seem to call the original INT 0 unless ARCH_IBMPC is defined. Might not be an issue after all? My changes to support elks are here:...

> Your "custom" IRQ handling file function enable_irq() is empty! I'm kind of running blind here, how does your system enable/disable external interrupts? Normally the enable_irq() and disable_irq() adjust the...

Probably worth saying that this board is like the PC platform, but a lot of the "supporting" chips are replaced by a single CPLD that does all the hard work....

As suspected, I'm not seeing the output of the printk in the timer_tick() function. Now I need to figure out if the issue lies with EMU86, or with the ELKS...

Right, I tracked down the issue with EMU86... it's expecting an EOI (or something of that ilk). So I've added one, and it's now working fine. I've also tracked down...

Thanks for your help in this... it's been very useful. 👍 I have CONFIG_APP_TAGS=":defash|:128k|:192k|", but when booting it says "/bin/init: Exec failed: /bin/sh (errno 2)"?.. what am I missing here?...