From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Stefano Manni <stefano.manni@gmail.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: fixed partitions issue
Date: Tue, 5 Aug 2025 07:24:26 +0200 [thread overview]
Message-ID: <ad635228-e3ac-4593-9a02-490fd84cf82f@pengutronix.de> (raw)
In-Reply-To: <HKY90T.CZFW9DH4XY4I3@gmail.com>
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 |
prev parent reply other threads:[~2025-08-05 5:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 10:45 Stefano Manni
2025-07-30 12:40 ` Ahmad Fatoum
2025-07-31 17:43 ` Stefano Manni
2025-08-05 5:24 ` Ahmad Fatoum [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad635228-e3ac-4593-9a02-490fd84cf82f@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=stefano.manni@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox