Hi Hung-Chun, On 2026-10-31T15:02:07+11:00, Hung-Chun Tseng <[email protected]> wrote: > diff --git a/doc/develop/driver-model/virtio.rst > b/doc/develop/driver-model/virtio.rst > @@ -73,6 +73,14 @@ Requirements > It is required that QEMU v2.5.0+ should be used to test U-Boot VirtIO support > on QEMU ARM and x86, and v2.12.0+ on QEMU RISC-V.
> > +The ``date`` command only uses RTC sequence 0. The ARM and RISC-V ``virt`` The 'Requirements' section is about QEMU versions, so this looks out of place. It would be worth giving the RTC its own short subsection, and moving the v5 paragraph about the virtio-rtc -device options into it too. If v5 does not already do this, please can you also update the 'Status' section near the top, which still says that only network and block devices are supported. > diff --git a/doc/develop/driver-model/virtio.rst > b/doc/develop/driver-model/virtio.rst > @@ -73,6 +73,14 @@ Requirements > +VirtIO RTC does not have. On x86, ``CONFIG_DM_RTC`` must be enabled for the > +driver to be built. I'm not sure x86 is any different. arch/Kconfig has 'imply RTC_MC146818' for X86 and the QEMU x86 devicetrees include rtc.dtsi, so with DM_RTC enabled I suspect the CMOS RTC binds early and gets sequence 0, while the VirtIO RTC turns up later on PCI. If so, 'date' would still not read the VirtIO RTC unless CONFIG_RTC_MC146818 is disabled. Please can you check this and, if it is right, describe all three architectures the same way. Regards, Simon
