Gregory Haerr
Gregory Haerr
The screenshots don't show enough history for me to see what you are doing. I will need a complete execution history in order to debug more. It is possible that...
If it is now working, I suspect the problem was/is that you were running ./build.sh, a shell script that doesn't work with WSL, while `make`, `make clean` or `make kimage`...
Hello @Ferry! Thanks for your interest in ELKS. It looks like you've already managed to come pretty far, cool! :) > I can see that kbd_timer() in kbd-poll.c is not...
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 way...
If this is the problem, you can have the kernel set the mask for you, I think the file is irq-8259.c or something like that.
Sure, I'll look at them tomorrow. You can copy masking code to your file, The point is to check the code to see whether our kernel actually unmasks IRQ 0...
> I have a custom irq-solo86.c. > The point is to check the code to see whether our kernel actually unmasks IRQ 0 so that the CPU gets the interrupt....
> possibly the mapping from IRQ0 to INT 0x20? The IBM PC mapping from IRQ 0 is to INT 8. The interrupt vector table offset is specified in `irq_vector`, like...
> Now I need to figure out if the issue lies with EMU86 I seem to remember something about counting instructions before simulating an INT 8 (IRQ 0) on EMU86......
> I press enter, and it seems to hang... then I press CTRL-C, and the prompt comes back Now that I think of it, /bin/sh does send some ANSI strings...