* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-atomic passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/simple-timing passed.
*
I've been digging and digging and digging and digging, and I think I'm
getting closer to an answer. What I'm trying to figure out now is if output
to the console is handled by a dedicated thread, or if it happens inline
with printk. It looks like printk puts stuff in a buffer and then the
I think I at least figured out what's going on. The console isn't using
interrupts from the UART to determine when to send the next character.
It's polling the LSR register which is hardwired (in M5) to always say
the UART is ready to go. What's actually happening, I think, is that
when
