diff options
| author | Sam Protsenko <semen.protsenko@linaro.org> | 2019-07-25 16:20:41 +0300 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2019-07-31 13:08:07 -0400 |
| commit | 3db0989e68ee23db9d5ae970304890100b4fb9bb (patch) | |
| tree | 613b98f9e8c367c08e07f1407b2740e96c03df0b /configs/snapper9g20_defconfig | |
| parent | a239147fa2c0c3fe849ccaffd72c4dc4cae2be71 (diff) | |
env: ti: boot: Handle reboot reason from BCB
In case of Android boot, reboot reason can be written into BCB (usually
it's an area in 'misc' partition). U-Boot then can obtain that reboot
reason from BCB and handle it accordingly to achieve correct Android
boot flow, like it was suggested in [1]:
- if it's empty: perform normal Android boot from eMMC
- if it contains "bootonce-bootloader": get into fastboot mode
- if it contains "boot-recovery": perform recovery boot
The latter is not implemented yet, as it depends on some features that
are not implemented on TI platforms yet (in AOSP and in U-Boot).
[1] https://marc.info/?l=u-boot&m=152508418909737&w=2
Signed-off-by: Sam Protsenko <semen.protsenko@linaro.org>
Diffstat (limited to 'configs/snapper9g20_defconfig')
0 files changed, 0 insertions, 0 deletions