guix_mirror_bot pushed a commit to branch master
in repository guix.
commit 2cb6948dc22c710404bebeab987feea1b777cb14
Author: Artyom V. Poptsov <[email protected]>
AuthorDate: Sun Jan 11 21:11:40 2026 +0300
gnu: visionfive2: Update the module commentary.
* gnu/system/images/visionfive2.scm: Update the module commentary.
Change-Id: If3d12bb0e3ccb9eaced4eb1e3afe636c7b89896f
Signed-off-by: Rutherther <[email protected]>
Merges: #4855
---
gnu/system/images/visionfive2.scm | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/gnu/system/images/visionfive2.scm
b/gnu/system/images/visionfive2.scm
index 6cbf18ed6a..11826d01b2 100644
--- a/gnu/system/images/visionfive2.scm
+++ b/gnu/system/images/visionfive2.scm
@@ -1,5 +1,6 @@
;;; GNU Guix --- Functional package management for GNU
;;; Copyright © 2024-2025 Zheng Junjie <[email protected]>
+;;; Copyright © 2026 Artyom V. Poptsov <[email protected]>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -47,13 +48,13 @@
;;; Commentary:
;;;
-;;; VisionFive2 can boot from MMC1 (SPI flash) or MMC2 (SD card) selected
-;;; by DIP switches MSEL[1:0], you may want boot from MMC2 to use the
-;;; U-Boot from Guix System instead of the vendor U-Boot in MMC1. Before
-;;; doing so, make sure you have a correct 'fdtfile' in the environment:
+;;; With this image, VisionFive2 can boot from MMC1 (MicroSD card) with
+;;; SDIO3.0 boot mode (RPIO_1:L, RGPIO_0:H -- see [1]), in this case the
+;;; board will use U-Boot from Guix System instead of the vendor U-Boot.
+;;; Booting from eMMC and NVME is still work-in-progress.
;;;
-;;; uboot> setenv fdtfile starfive/jh7110-starfive-visionfive-2-v1.3b.dtb
-;;; uboot> saveenv
+;;; References:
+;;; 1.
<https://doc-en.rvspace.org/VisionFive2/Boot_UG/VisionFive2_SDK_QSG/boot_mode_settings.html>
;;;
;;; Code:
