09-28-2020, 09:36 AM
Perhaps an off-topic, feel free to throw rocks at ignore me if it is...
Do I understand correctly that PBP SoC completely ignores the eMMC Boot Area Partitions like boot0 and boot1 (show up as, e.g., /dev/mmcblk2boot0 and are NOT visible in, say, GParted)? That is, it ONLY looks at fixed offsets on eMMC User Data Area (shows up as, e.g., /dev/mmcblk2 and IS visible in GParted)? Or at least that's the intention? Because if PBP doesn't completely ignore boot area partitions that might explain some of the booting weirdness some people experience while manipulating only the user data area. That also could be a way to avoid having a gazillion of partitions in the user data area on eMMC if one could write all the necessary U-boot data into the boot area partitions boot0 and boot1.
Do I understand correctly that PBP SoC completely ignores the eMMC Boot Area Partitions like boot0 and boot1 (show up as, e.g., /dev/mmcblk2boot0 and are NOT visible in, say, GParted)? That is, it ONLY looks at fixed offsets on eMMC User Data Area (shows up as, e.g., /dev/mmcblk2 and IS visible in GParted)? Or at least that's the intention? Because if PBP doesn't completely ignore boot area partitions that might explain some of the booting weirdness some people experience while manipulating only the user data area. That also could be a way to avoid having a gazillion of partitions in the user data area on eMMC if one could write all the necessary U-boot data into the boot area partitions boot0 and boot1.
This message was created with 100% recycled electrons