Al,
In using ELKS v0.77, it's apparent that ^C console signals work
about 50% of the time. I was going to get involved in tracking this down,
but have some questions first.
Does ELKS use interrupt driven keyboard input? You were saying something
about tty input chars being checked only at when an app makes a system call.
If this is the case, I think we need to think about rewriting it so that it's
interrupt-driven.
What sections did you rewrite for the new interrupt stuff that was
required? Is the serial port interrupt driven? (In other words, if we were running
a serial console, and a ^C came in, would the signal be sent if the user
process was just "for(;;) ;"
Why is the scheduler so complicated? Couldn't ELKS do with a simple
round-robin scheduler for now? It seems there's *so much* code in sched.c, and
I can't imagine it's going to buy most ELKS programs/user much... Do we
really want the top-half/bottom-half processing with all it's overhead?
Greg
