README: link lanai documentation and header die shot
diff --git a/README.md b/README.md
index 2a1e8c0..6d50758 100644
--- a/README.md
+++ b/README.md
@@ -10,16 +10,18 @@
4. An SPI controller
5. A GPIO controller
+<img src="https://object.ceph-eu.hswaw.net/q3k-personal/81225263281a1b7c952f43354fb26eae63ec7970bd382d215303a34800afb8e9.png" width="300">
+
## Lanai
Lanai is a family of RISC CPUs first introduced by Myricom in their NICs. Since then, its use seems to have mostly shifted to Google, whose engineers have contributed a Lanai target to LLVM. Not much is known about the use of the core inside Google.
The Lanai implementation in the QF100 series SoC targets the instruction set as generated by LLVM, called 'Lanai 11'. It diverges in some aspects from the previous versions of the instruction set as documented by Myricom and as implemented by their network cards, by removing RRR (register-register-register, a.k.a. dual-ALU) instructions, removing the PUNT instruction, and tightening some pipeline timing.
-TODO: document differences better
-
We have a work-in-progress LLD implementation for Lanai and Rust target for Lanai, that will be opensourced (and hopefully upstreamed) soon.
+I wrote a [summary about Lanai](https://q3k.org/lanai.html) on my homepage.
+
## QF100 sources: qfc
The QF100 is built from a 'bundle' of verilog exported from the 'qfc' repository. This bundle contains pre-processed files containing both compiled Bluespec as well as Bluespec standard library code. Each hard macro in the resulting design has a separate Verilog file named the same way.
