Hi Neil,
The logic is complex but looks to be good.
What would happen if we plug an eMMC with conflicting partitions names ?
That would cause issues... Probably the more correct way to do things
here would be to use part UUIDs, but it's not clear how consistent those
are.
Is there a way
On 4/1/25 14:42, Ilias Apalodimas wrote:
Hi Caleb
On Wed, 26 Mar 2025 at 19:41, Caleb Connolly wrote:
Expand capsule update support to correctly identify which partition
U-Boot is flashed to (between xbl, uefi, and boot including A/B
variants).
Use qcom_boot_source to determine if we were
On 26/03/2025 18:40, Caleb Connolly wrote:
Expand capsule update support to correctly identify which partition
U-Boot is flashed to (between xbl, uefi, and boot including A/B
variants).
Use qcom_boot_source to determine if we were chainloaded from ABL,
meaning U-Boot is on the boot partition, ot
Hi Caleb
On Wed, 26 Mar 2025 at 19:41, Caleb Connolly wrote:
>
> Expand capsule update support to correctly identify which partition
> U-Boot is flashed to (between xbl, uefi, and boot including A/B
> variants).
>
> Use qcom_boot_source to determine if we were chainloaded from ABL,
> meaning U-Bo
Expand capsule update support to correctly identify which partition
U-Boot is flashed to (between xbl, uefi, and boot including A/B
variants).
Use qcom_boot_source to determine if we were chainloaded from ABL,
meaning U-Boot is on the boot partition, otherwise we assume uefi if
it's available, fin
5 matches
Mail list logo
