From 480c96bcd95601ee1263edcaa51966a9ea304e69 Mon Sep 17 00:00:00 2001
From: Dmitry Ermakov <7954832+dimerr@users.noreply.github.com>
Date: Wed, 28 Oct 2026 08:01:28 +0000
Subject: [PATCH 1/2] qemu-boot: FH8626V100 runs 4.9.129, so its flash is
 spi0.0

The *v100 arm sent fh8626v100 the 3.0.8 kernels' spi_flash MTD id; its
kernel (fullhan-fh8852v200) names the flash spi0.0, so the mtdparts were
ignored and the board's built-in partitions mounted no root.
---
 qemu-boot/test-fullhan-boot.sh | 1 +
 1 file changed, 1 insertion(+)

diff --git a/qemu-boot/test-fullhan-boot.sh b/qemu-boot/test-fullhan-boot.sh
index 3e0550d..b767f89 100755
--- a/qemu-boot/test-fullhan-boot.sh
+++ b/qemu-boot/test-fullhan-boot.sh
@@ -45,6 +45,7 @@ KERNEL=$DIR/uImage.$SOC
 ROOTFS=$DIR/rootfs.squashfs.$SOC
 
 case $SOC in
+    fh8626v100) MTDID=spi0.0 ;;        # 4.9.129, despite the suffix
     *v100) MTDID=spi_flash ;;          # the 3.0.8 m25p80 platform data's
     *)     MTDID=spi0.0 ;;
 esac

From 4fe304c5982288a888cbd4e9ea519c009658e349 Mon Sep 17 00:00:00 2001
From: Dmitry Ermakov <7954832+dimerr@users.noreply.github.com>
Date: Wed, 28 Oct 2026 11:41:34 +0000
Subject: [PATCH 2/2] qemu-boot: the same FH8626V100 exception in
 fh-openipc-flash.sh

It writes the mtdparts= into the generated image's U-Boot environment
and maps every *v100 SoC to spi_flash too, so an FH8626V100 image booted
from its own bootargs had the same unmountable root.
---
 qemu-boot/fh-openipc-flash.sh | 1 +
 1 file changed, 1 insertion(+)

diff --git a/qemu-boot/fh-openipc-flash.sh b/qemu-boot/fh-openipc-flash.sh
index bd38fa2..7a0bfa9 100755
--- a/qemu-boot/fh-openipc-flash.sh
+++ b/qemu-boot/fh-openipc-flash.sh
@@ -59,6 +59,7 @@ dd if="$ROOTFS" of="$OUT" bs=64k seek=37 conv=notrunc status=none
 # The MTD device's name: the 3.0.8 kernels' m25p80 platform data says
 # "spi_flash", the 4.9 ones take the SPI device's.
 case $SOC in
+    fh8626v100) MTDID=spi0.0 ;;        # 4.9.129, despite the suffix
     *v100) MTDID=spi_flash ;;
     *)     MTDID=spi0.0 ;;
 esac