On 11/10/25 14:05, Bin Meng wrote:
The U-Boot community reported a CI failure [1] where the
`sifive_unleashed` target failed to boot from an SD card after
upgrading from QEMU v8.2.0 to v9.2.3.
At that time, the issue was traced to commit da954d0e
("hw/sd/sdcard: Add spi_cmd_SEND_CSD/CID handlers (CMD9 & CMD10)")
which was introduced in v9.1.0.
Testing with the latest QEMU mainline shows that the problem still
persists, although the underlying cause has changed due to refactoring
since then.
This series fixes the broken `ssi-sd` model. After applying these
patches, U-Boot successfully boots again on the `sifive_unleashed`
target using QEMU’s `sifive_u` machine.
[1] https://gitlab.com/qemu-project/qemu/-/issues/2945
Hi!
This seems to be a qemu-stable material.
The refactoring mentioned above happened between 10.1.0-rc1 and
10.1.0-rc2, which is quite a hot spot for a refactoring. So the
changes are definitely relevant for 10.1.x series, where I applied
them already.
But we've 10.0.x series which supposed to be long-term support
series, where we have the problem too (since the issue were
introduced before 10.0), but the 2 fixes here don't apply to 10.0,
obviously, due to refactoring.
Now I wonder should we fix this in 10.0.x at all, should we
create some unique fix for 10.0.x, or should we pick the
refactoring done in 10.1.0-rc stage, to 10.0.x?
This is the original refactoring patchset:
https://lore.kernel.org/qemu-devel/[email protected]/
The patchset applies cleanly to 10.0.x, with these 2 fixes on
top, and the resulting thing seem to work fine, so far anyway:
https://gitlab.com/mjt0k/qemu/-/commits/10.0-sdcard
(and with local tests, including the test in the above series).
What do you think? How important it is to make this whole
thing work in 10.0.x lts series (including distribution(s)
based on this, such as current debian stable "trixie")?
Thanks,
/mjt
