rajamesandClaude Opus 5.5
3b49cb15a2
Captain Bob, 2026-10-14: "change to PC, not SER5. it's not supposed to be specific, but PC generic." boards/ser5 -> boards/pc, TARGET=PC, lithos-pc.img; the image was never specific to one machine (the generic UEFI/ACPI path, FABRIC-3 III). The Beelink SER5 stays named where the text means the unit on the bench (its Secure Boot, BIOS, serial header) and in the records. Built: lithos-pc.img, system=v4, with its SBOM. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
31 lines
1.7 KiB
Markdown
31 lines
1.7 KiB
Markdown
# boards/
|
|
|
|
One directory per physical target. `make boot_image TARGET=<NAME>` (repo root) maps the
|
|
name to a directory here, reads its `board.mk`, and builds the single file that goes on
|
|
that board's boot medium into `build/boards/<board>/`.
|
|
|
|
| TARGET | Directory | ISA | Boot path | Image |
|
|
|---|---|---|---|---|
|
|
| `PC` | `pc/` | amd64 | UEFI firmware, removable-media path -- any x86-64 PC | GPT + FAT32 ESP: `EFI/BOOT/BOOTX64.EFI` |
|
|
| `RASPI` | `raspi/` | aarch64 | Pi 5 EEPROM firmware, native | MBR + FAT32: `config.txt`, `kernel_2712.img`, `bcm2712-rpi-5-b.dtb` |
|
|
| `MILKV` | `milkv/` | riscv64 | SPI-flash U-Boot + OpenSBI, `bootefi` | GPT + FAT32 ESP: `EFI/BOOT/BOOTRISCV64.EFI` |
|
|
| `ZYNQ7020` | `zynq7020/` | armv7 | BootROM, `BOOT.BIN`, U-Boot | not yet: needs `kernel/src/arch/armv7` |
|
|
|
|
`board.mk` sets:
|
|
|
|
- `BOARD_DESC`: one-line description (`make boards`)
|
|
- `BOARD_ARCH`: kernel ISA (`kernel/src/arch/<arch>`)
|
|
- `BOARD_BOOT`: image recipe in `kernel/Makefile` (`uefi-esp`, `rpi-native`, ...)
|
|
- `BOARD_IMAGE`: output file name
|
|
|
|
Disk images are assembled by `scripts/mkdiskimage.sh`, which needs no root access and no loop
|
|
devices. `KERNEL_ARGS="..."` is written as `starforth.cfg` (UEFI boards) or `cmdline.txt`
|
|
(Pi 5, where the firmware copies it into `/chosen/bootargs`). `BOOT_IMAGE_SIZE_MIB` sets the
|
|
image size; the default is 128.
|
|
|
|
Hardware status: none of these images has been booted on real silicon from this build. The
|
|
PC image has been booted in QEMU (q35 + OVMF, from its own disk) through POST. (`PC` was named
|
|
`SER5` until 2026-10-14, after the first PC on the bench; the image was never specific to it.) The Pi 5
|
|
native path (`raspi/README.md`) and the JH7110 peripherals have still only been checked by
|
|
compiling.
|