From: "Neil Armstrong" <narmstrong@baylibre.com>
To: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Cc: u-boot-amlogic@groups.io, u-boot@lists.denx.de,
Gary Bisson <gary.bisson@boundarydevices.com>
Subject: Re: [PATCH] configs: meson64_android: define raw parts for bootloader
Date: Wed, 12 Jan 2022 10:05:26 +0100 [thread overview]
Message-ID: <af7499bf-18d6-8cfa-ce22-284d70d682ad@baylibre.com> (raw)
In-Reply-To: <20220107163913.3393563-1-mkorpershoek@baylibre.com>
On 07/01/2022 17:39, Mattijs Korpershoek wrote:
> Per the android documentation[1]:
> - the mmc2boot0 partition should be labeled "bootloader".
> - the mmc2boot1 partition should be labeled "bootenv".
>
> Also the u-boot documentation[2] refers to a BOOT1_OFFSET of 1 block.
>
> Define 2 raw partitions to store the bootloaders and the bootenv.
>
> [1] https://source.android.com/setup/build/devices#vim3-fastboot
> [2] https://u-boot.readthedocs.io/en/latest/board/amlogic/khadas-vim3l.html
>
> Suggested-by: Gary Bisson <gary.bisson@boundarydevices.com>
> Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
> ---
> include/configs/meson64_android.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/configs/meson64_android.h b/include/configs/meson64_android.h
> index 0303d187de..1266851196 100644
> --- a/include/configs/meson64_android.h
> +++ b/include/configs/meson64_android.h
> @@ -283,6 +283,8 @@
> EXTRA_ANDROID_ENV_SETTINGS \
> "partitions=" PARTS_DEFAULT "\0" \
> "mmcdev=2\0" \
> + "fastboot_raw_partition_bootloader=0x1 0xfff mmcpart 1\0" \
> + "fastboot_raw_partition_bootenv=0x0 0xfff mmcpart 2\0" \
> ANDROIDBOOT_GET_CURRENT_SLOT_CMD \
> AVB_VERIFY_CMD \
> "force_avb=0\0" \
>
Applied to u-boot-amlogic
Thanks,
Neil
prev parent reply other threads:[~2022-01-12 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 16:39 [PATCH] configs: meson64_android: define raw parts for bootloader Mattijs Korpershoek
2022-01-12 9:05 ` 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=af7499bf-18d6-8cfa-ce22-284d70d682ad@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=gary.bisson@boundarydevices.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).