From: "Neil Armstrong" <narmstrong@baylibre.com>
To: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Cc: u-boot-amlogic@groups.io, u-boot@lists.denx.de
Subject: Re: [PATCH 0/2] meson64_android: fix initial flashing failures
Date: Wed, 17 Nov 2021 13:31:02 +0100 [thread overview]
Message-ID: <dbcb4a53-ddbd-78c9-210b-9a38fc09005f@baylibre.com> (raw)
In-Reply-To: <20211117110411.710190-1-mkorpershoek@baylibre.com>
Hi,
On 17/11/2021 12:04, Mattijs Korpershoek wrote:
> The SEI-610 and SEI-510 boards are well supported in the
> Android Open Source project via the yukawa [1] platform.
>
> Their U-Boot version, despite being public [2] is not in mainline.
>
> For initial boards, with an empty eMMC, we can have boot loops
> while using the flashing process described in [3].
>
> This series add 2 fixes for these bootloops.
>
> [1] https://android.googlesource.com/device/amlogic/yukawa
> [2] https://gitlab.com/baylibre/amlogic/atv/u-boot/-/tree/u-boot/v2021.07/integ
> [3] https://gitlab.com/baylibre/amlogic/atv/aosp/device/amlogic/yukawa/-/wikis/Khadas_VIM3#flash-android-bootloader
>
> Neil Armstrong (2):
> configs: meson64_android: bypass other checks on run_fastboot=1
> configs: meson64_android: add PANIC stage for SYSTEM fails
>
> include/configs/meson64_android.h | 47 +++++++++++++++++++------------
> 1 file changed, 29 insertions(+), 18 deletions(-)
>
>
> base-commit: 4f4f974a46244270c1c6723017711c0aa8250206
>
Thanks,
Applied to u-boot-amlogic
Neil
prev parent reply other threads:[~2021-11-17 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 11:04 [PATCH 0/2] meson64_android: fix initial flashing failures Mattijs Korpershoek
2021-11-17 11:04 ` [PATCH 1/2] configs: meson64_android: bypass other checks on run_fastboot=1 Mattijs Korpershoek
2021-11-17 11:04 ` [PATCH 2/2] configs: meson64_android: add PANIC stage for SYSTEM fails Mattijs Korpershoek
2021-11-17 12:31 ` Neil Armstrong [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dbcb4a53-ddbd-78c9-210b-9a38fc09005f@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=mkorpershoek@baylibre.com \
--cc=u-boot-amlogic@groups.io \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).