Hello Stefano,
On 31.07.25 19:43, Stefano Manni wrote:
> On v2025.07.0 every time I write barebox-env part (e.g. with nv command) also
> barebox
> part is written. This on v2025.01.0 does not happen.
>
> I supposed the problem was in the fixed-partition bindings but maybe it is
> somewhere
> else, for example in the spinor driver.
>
> Is that something I may test to understand more?
The issue was easily reproducible in QEMU with the virt platform or vexpress
platform,
e.g. for multi_v8_defconfig:
pytest --lg-env test/arm/multi_v8_defconfig.yaml --interactive
and then
barebox@ARM QEMU virt64:/ md -s /dev/nor0.initramfs 0+16 ; md -s
/dev/nor0.barebox-environment 0+16
00000000: 00000000 00000000 00000000 00000000 ................
00000000: 00000000 00000000 00000000 00000000 ................
barebox@ARM QEMU virt64:/ saveenv
saving environment to /dev/nor0.barebox-environment
barebox@ARM QEMU virt64:/ md -s /dev/nor0.initramfs 0+16 ; md -s
/dev/nor0.barebox-environment 0+16
00000000: 798fba79 00000000 00000000 00000000 y..y............
00000000: 798fba79 00000000 00000000 00000000 y..y............
I ran a git bisect and found the issue to be introduced by Sascha's commit
6d2b6f399c07 ("cdev: pass master cdev to cdev ops").
This was first included in v2025.07.0.
@Sascha, can you look into this?
Thanks,
Ahmad
>
> Best,
> Stefano
>
>
>
>
>
>
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
