I originally posted this as part of the Software Internals Book Club, for OSTEP.
Alongside this book club I’ve been getting into retro computing. There is a story here involving picking up an amber CRT monitor at a local shop and getting to view some unreleased, remastered footage of ReBoot, but I digress.
m68k is an architecture I’ve been vaguely aware of through being around Linux, and Zig. I picked up a couple chips while shopping online, and started looking at them in more depth.
The timing of this, with reading this book was funny, because the releases of the different CPUs in this family line up pretty well with a few of the chapter topics:
- 68000:
- Basic CPU, no hardware support for memory virtualization.
- 68010:
- Introduced recoverable bus faults.
- Could be paired with an MMU chip (68451).
- The MMU used segment based memory management.
- The OS had to manually manage the segment table.
- 68020:
- Introduced a hardware coprocessor interface between CPU and MMU (68851).
- MMU used TLB, mapped virtual addresses, and managed the tables in hardware.
- 68030:
- MMU moved onto the CPU silicon to provide a single package.
- Non MMU variants offered ofc.
There are few more models, and way more details on what these chips were capable of, what they were used in, but I wanted to zoom in on these virtualization features offered.
The 68020 is particularly interesting to me, because it’s this cool sweet spot of having these modern looking virtual memory hardware features, but the MMU is physically disconnected, and could be replaced. It would be a very cool platform for education and experimenting because you could replace the MMU with an FPGA, and try out different MMU techniques with a toy OS.
Of course you could simulate all of this, but I think the hardware imposing constraints adds a lot to the creativity and fun to be had.