The goal is to insert device drivers in between.

I'd like to move this code, along with all recipe contents, to blk/.
It's easier if "emul-related" code is gathered at the same place.

With all this recent movements, we had a bit of a fragmentation
issue.

2 was overkill

This would allow things like temporary giving control to the *CL
line on the TRS-80. For example... A very far fetched example. Not
at all the only *raison d'etre* of the layer...

Big bootstrapping change which greatly reduces the role of the modern
operating system in the bootstrapping process.

Less noisy this way

The way is clear for complete stage1 bootstrapping on the RC2014
target!

It seems that xcomp can't manage to reliably compile core+ units.
Let's limit the role of xcomp to z80c+icore.

I'm getting a little desperate here. I'll revisit the link.fs approach
with a new idea I had...

... instead of building boot.fs, and then z80c.fs/icore.fs in separate
passes. This strengten xcomp by making it support 2 completely separate
dicts (that is, the X dict is *not* connected to the system dict. The chain
now stops at EXIT def in boot.fs).

We can now cross-compile core.fs.

Memory mapping is a dead end too, solution has to be at a higher
level. xcomp is my new approach.