I might later question this decision.
I liked how each "hardware" example was roughly one self-contained file. In the
"input_keyboard" case, this is no longer true.
This improves ttf-convert slightly:
- variable size glyphs
- initialize metrics for glyphs with zero-size bitmaps (e.g "space")
- move the font/serialization structures to a common header
The keyboard example includes keyboard layout data for the HSS-0129 (Japanese)
Sega Saturn keyboard.
The Sega Saturn does not have enough video RAM to store an entire 24-bit
framebuffer. Attempting this causes the "bottom" half of the scene to be
clipped, as video RAM addresses that do not exist are written to.
I'd like to include bits of libgcc piecemeal--I don't want to "accidentally"
start depending on libgcc bits that I'm not aware of.
Reworked division so that it uses the on-chip division register.
