Superseded by v2.
On Tue, Jul 9, 2019 at 5:45 PM 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 f
Hi Sam,
On Fri, Jul 12, 2019 at 04:18:20PM +0300, Sam Protsenko wrote:
> Let's finalize modern Android boot flow via scripting (as we need all
> those commands anyway), then we can think if we need to wrap the whole
> thing into boot_android command. There is a lot of stuff happening
> during the
Hi Eugeniu,
On Fri, Jul 12, 2019 at 12:39 AM Eugeniu Rosca wrote:
>
> Hi Sam,
>
> On Tue, Jul 09, 2019 at 05:45:43PM +0300, Sam Protsenko wrote:
> > "emmc_android_boot=" \
> > + "if bcb load " __stringify(CONFIG_FASTBOOT_FLASH_MMC_DEV) " misc; " \
> > + "then " \
> > + "
Hi Sam,
On Tue, Jul 09, 2019 at 05:45:43PM +0300, Sam Protsenko wrote:
> "emmc_android_boot=" \
> + "if bcb load " __stringify(CONFIG_FASTBOOT_FLASH_MMC_DEV) " misc; " \
> + "then " \
> + "if bcb test command = bootonce-bootloader; then " \
> + "echo B
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
5 matches
Mail list logo