Hi Torsten,
Tested-by: Peter Esselius <[email protected]>
I tested the NVMe-relevant subset (patches 1-3) on a Raspberry Pi 5
(4 GB, Rev 1.0) with a BIWIN CE430T5D100-512G NVMe, using U-Boot 2026.10
plus those patches and a one-line `boot_targets` follow-up.
Hardware/software:
- Pi 5 4 GB, non-HAT+ M.2 HAT, EEPROM 2026-05-26
- EEPROM: BOOT_ORDER=0xf416, PCIE_PROBE=1
- config.txt: dtparam=pciex1
- U-Boot 2026.10 with:
- [1/8] core: skip parent device nodes without a DT reference
- [2/8] test: add dma-ranges UT for dynamically created nodes
- [3/8] configs: enable NVMe on RPi4 and RPi5
- follow-up: boot_targets=mmc usb nvme pxe dhcp
- SD card removed for the NVMe-only test
Results:
- `nvme scan` finds the BIWIN NVMe.
- `bootflow scan` finds the NVMe ext4 partition and boots extlinux:
** Booting bootflow 'nvme#0.blk#1.bootdev.part_2' with extlinux
- The NVMe system booted; serial console and SSH work.
- With an SD card inserted, U-Boot still boots the SD first
(mmc before nvme), preserving the existing fallback:
** Booting bootflow '[email protected]_2' with extlinux
Removing the SD again and rebooting returned to the NVMe-only system.
- The `boot_targets` line is required for automatic boot: without it,
`nvme scan` creates the bootdev but bootstd never scans it. I have sent
a one-line follow-up patch separately; would you prefer it folded into
the series or kept separate?
Thanks,
Peter
