After more testing with the mentioned patch applied on parted 3.3, I
still have differences on the MBR
toward parted 3.2, below is what I got now:
:~# hexdump -n 1024 -C /dev/mmcblk0
fa b8 00 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 ||
0010 fb be 00 7c bf 00 06 b9
> > OK , thank you very much for the explanation. Since I don't use
> > raspberry Pi among my targets, do you think I can safely run a custom
> > parted with a revert of 61dd3d4c5eb782eb43caa95342e63727db3f8281 ?
> That's probably fine, as long as you know what you are doing ;)
Ok I'll go this
> This change was introduced by commit
> 61dd3d4c5eb782eb43caa95342e63727db3f8281, it was needed to fix problems
> growing partitions when using SD cards on the Raspberry Pi.
OK , thank you very much for the explanation. Since I don't use
raspberry Pi among my targets, do you think I can safely
On Thu, Jan 26, 2023 at 11:52:36AM +0100, Frédéric Martinsons wrote:
> Hello,
>
> I have an arm based board with an eMMC card for storage.
> I cross compil an GNU/Linux OS (with yocto) for this boardand and I came
> across an issue after updating parted to 3.3 and above.
[snip]
>
> The main
Hello,
I have an arm based board with an eMMC card for storage.
I cross compil an GNU/Linux OS (with yocto) for this boardand and I came
across an issue after updating parted to 3.3 and above.
Below are my commands to partition the 4GB storage (2 partitions of 1.8GB,
1 bootable partition of
