[U-Boot] [PATCH] fastboot: Fix slot names reported by getvar

Eugeniu Rosca erosca at de.adit-jv.com
Thu Jun 13 09:30:53 UTC 2019

Hi Sam,

On Thu, Jun 13, 2019 at 12:49:45AM +0300, Sam Protsenko wrote:
> In commit [1] fastboot tool was changed w.r.t. new A/B specification [2],
> and now we should report slot names in "a" format instead of "_a".
> Latter is now considered legacy and we shouldn't rely on that anymore.

This looks like a change which advantages the users who are always on
the tip/HEAD of all relevant components (fastboot and U-Boot), but that
rarely happens in the industry. Suppliers and hardening vendors often
deliver obsoleted versions because they can't keep up with upstream
development. Can you please document the behavior of 'fastboot flash'
(and anything else relying on
'fastboot getvar (current-slot|slot-suffixes) in below scenarios:

A. fastboot >= [1] && U-Boot + this patch
B. fastboot >= [1] && U-Boot - this patch
C. fastboot <  [1] && U-Boot + this patch
D. fastboot <  [1] && U-Boot - this patch

Would it be possible to keep U-Boot backward-compatible, such that
regardless of the scenario enumerated above, 'fastboot flash' will
always succeed?

> [1] https://android.googlesource.com/platform/system/core/+/8091947847d5e5130b09d2ac0a4bdc900f3b77c5
> [2] https://source.android.com/devices/tech/ota/ab/ab_implement#partitions

Best Regards,

More information about the U-Boot mailing list