why did I think that I could read from it?

NetBSD doesn't have ncurses. Linking to curses doesn't seem to change
anything. Tried on OpenBSD and Ubuntu.

The '2' key on my PS/2 keyoard never worked on Collapse OS, I
wasn't sure why. I thought the keyboard was broken, but then I
tried another one, still broken. But it's only the '2'!

The KC sent is 0x1f. Is it a timing problem with the ATtiny? I
have yet to wire my prototype for logic probing. Meanwhile, let's
apply a band-aid.

Previous instructions would only work with an AT28C64. Now, it also
work with an AT28C256.

Add _TRA!, _THA!, _TRB!, _THB! routines to easily handle those pins'
value without stepping on other pins like the drivers previously
did. For SDC driver, it's going to be important soon because it turns
out that I can't get away with "always on" CS, so I'll need a scheme
where it's important that TH/TR pins have stable values.

Recipes contain bits and pieces of hardware-related knowledge, but
these bits feel sparse. I've been wanting to consolidate hardware-
related documentation for a while, but always fell at odds with the
recipes organisation.

We don't have recipes anymore, just a /doc/hw section that contains
hardware-related documentation which often translate to precise
instructions to run Collapse OS on a specific machine.

With this new organisation, I hope to end up with a better, more
solid documentation.

Theoretically, it works. I can access an emulated SD card on it.

Will it work on real hardware?

I've also made SMS emulation faster. It was unbearably slow for SDC
access.

My idea of plugging a RC2014 bridge directly onto a Sega Master System
cartridge doesn't work. The SMS eats all I/O addr space, we can't use
it. Therefore, this naive idea, in the emulator, of reusing sdc.c in
sms.c as-is, doesn't work either.

I'll have to find another way of communicating to a SPI device on the
SMS. I'll probably do it through a controller port. Meanwhile, I need
to decouple SPI from SDC in the emulator code so that I can reuse
sdc.c. This is what is done here.

There are many situations where it can be useful. Worth it.

This allows us to remove AMOVE* words.

This would be useful, for example, to allow the assembler to write
straight to an AT28 EEPROM without going to RAM. This would be a
life saver in machines with tight RAM such as the SMS.

With KEY and EMIT being switch words, most of the high layer can
be defined before drivers.

In addition to this change, I've compacted core blocks which were
becoming quite sparse.

This allows us to remove one layer of indirection in (wnf). This is
possible now that EMIT is a switch word.

Slightly larger binary, but clearer code and slightly faster.

RAM+ is the host's setup! Use SYSVARS instead, which is the guest's
value.

I'm pretty happy about how lightweight the implementation turns
out to be.

1 whole byte!

I think that when I added NL, I had troubles having access to CRLF's
address at boot time, which is why I had this system. But now that
CRLF is easily accessible during BOOT, we can simplify.

(and that will help us in the hopefully-upcoming change, which is
quite nice...)

They were only used in the ti84 recipe and were not worth their cost.

It works (in emulation, but soon on real hardware!), but the LIST
command is awkward due to tight screen estate...

I'm about to reuse sdc.c in sms.c and the old directory structure
was becoming awkward.

De-macroisation negatively impacts speed, but this emulator doesn't
need to be fast. Clear code is more important.

We assume CPU_V20 configuration at all times.

I had forgotten that heads index increment before track index.

Getting a Collapse OS prompt.

I'm planning on adding other subfolders. 8086 for example...

libz80 doesn't move much anymore, there not much advantage to the
git module indirection.

There's no reason to run them only under CVM.

I thought it wasn't possible with XCB to transform keycodes into
symbols for the current keyboard mapping, but I hadn't looked
hard enough.

Use reg 2 as specified.

I'm not sure if not setting IM 1 explicitly can be the source of bugs,
but SMS Power's tutorial mentions that everyone is doing it, so...