From: Tom Rini Date: Wed, 31 Jul 2019 23:35:50 -0400 Subject: [U-Boot] [PATCH v3] env: ti: boot: Handle reboot reason from BCB In-Reply-To: <20190725132041.10117-1-semen.protsenko@linaro.org> References: <20190725132041.10117-1-semen.protsenko@linaro.org> Message-ID: <20190801033550.GO6403@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Thu, Jul 25, 2019 at 04:20:41PM +0300, Sam Protsenko wrote: > 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 Applied to u-boot/master, thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: