On Tue, May 21, 2019 at 9:37 AM Lukasz Majewski lukma@denx.de wrote:
Hi Alex,
On Mon, May 20, 2019 at 8:23 AM Eugeniu Rosca erosca@de.adit-jv.com wrote:
Should it default to enabled if avb is used?
I think at this specific moment in time, 'bcb' is orthogonal (meaning it is neither a direct, nor a reverse dependency) to any other Android feature in U-Boot. This could be re-assessed, if platform maintainers start to rely on 'bcb' in their U-Boot environments on regular basis.
'bcb' looks like something I'd be interested in, not running Android at all... currently I (ab)use the bootcounter to communicate between the kernel and U-Boot when I want to force a board through recovery,
I don't know your exact use case, but wouldn't it be better to use envs (with redundancy) and fw_setenv / fw_printenv from Linux user space?
Now those envs even support setting default values for u-boot (as there is now separate library used for it). Moreover there is OE/Yocto's recipe 'u-boot-fw-utils' which can be easily used and installed.
It's a long story... I'm constrained by historic choices, which makes using the environment problematic. But you're right.