commit: 74f1e6c3c99d869248e5913edcb84c52c39a693e
parent ed831be4604c5b8e6f767bd15dba5ab36b23c5df
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date: Mon, 3 Feb 2025 20:29:24 +0100
notes/starfive_visionfive2: More clearly document how extlinux.conf works
Diffstat:
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/notes/starfive_visionfive2.xhtml b/notes/starfive_visionfive2.xhtml
@@ -51,22 +51,23 @@ make PLATFORM=generic FW_PAYLOAD_PATH="${uboot_bin}" FW_FDT_PATH="${uboot_dtb}"
</ol>
</p>
- <h3>extlinux.conf</h3>
+ <h3>extlinux/extlinux.conf</h3>
<p>
- No need to have it flashed as MBR like on x86, just have it present into a FAT or ext{3,4} filesystem, u-boot will then use it as configuration.
+ No need to have anything flashed on SD/eMMC/NVMe like on x86-pc (MBR) or most other boards.
+ U-Boot flashed on the bootchip will by default search for an <code>(/boot)/extlinux/extlinux.conf</code> file in a FAT or ext[34] filesystem.
+ <br />
+ See <a href="https://docs.u-boot.org/en/latest/develop/bootstd/overview.html">Standard Boot Overview - Das U-Boot documentation</a>
+ and <a href="https://docs.u-boot.org/en/latest/develop/distro.html">Generic Distro Configuration Concept - Das U-Boot documentation</a>.
+ </p>
+
+ <p>
+ For example with Alpine main system installed in a ZFS filesystem and <code>/boot</code> as ext4/fat/…:
</p>
<pre><code><