Scarlet now ships a Limine-based boot workflow with RISC-V as the primary path.
Issue #345 now targets full boot unification around Limine. The current in-tree implementation moves the kernel toward that by:
- native Limine boot protocol on RISC-V
- DTB/FDT-driven
BootInfocreation - initramfs passed as a boot module
- higher-half kernel linking with HHDM-backed physical access
riscv64 is Scarlet's primary architecture, and issue #345 explicitly needs the higher-half move bundled with the Limine migration.
That makes RISC-V the correct place to establish the new boot contract first.
cargo make build-riscv64This produces mkfs/dist/limine-riscv64-boot.img and refreshes the matching initramfs/rootfs artifacts.
cargo make run-riscv64For debugging:
cargo make debug-riscv64The FAT boot image contains:
EFI/BOOT/BOOTRISCV64.EFI- Limine UEFI loaderEFI/BOOT/limine.conf- Limine configurationboot/kernel- higher-half-linked RISC-V kernel ELFboot/initramfs-riscv64.cpio- initramfs module- optional DTB override if provided
This path establishes Limine-native bring-up and higher-half groundwork on RISC-V. AArch64 still has transitional pieces in-tree, but the long-term target is one unified Limine-oriented boot model across supported architectures.