From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Guillaume La Roque <glaroque@baylibre.com>,
Bryan Brattlof <bb@ti.com>, Tom Rini <trini@konsulko.com>,
Joe Hershberger <joe.hershberger@ni.com>,
Nishanth Menon <nm@ti.com>,
Robert Nelson <robertcnelson@gmail.com>,
Vignesh Raghavendra <vigneshr@ti.com>
Cc: u-boot@lists.denx.de, Vishal Mahaveer <vishalm@ti.com>,
Guillaume La Roque <glaroque@baylibre.com>
Subject: Re: [PATCH 2/3] board: beagle: beagleplay: Add android bootflow support
Date: Tue, 03 Sep 2024 09:27:15 +0200 [thread overview]
Message-ID: <8734mh8aek.fsf@baylibre.com> (raw)
In-Reply-To: <20240902-sitaraupstream-v1-2-0c478c33c08b@baylibre.com>
Hi Guillaume,
Thank you for the patch.
On lun., sept. 02, 2024 at 18:31, Guillaume La Roque <glaroque@baylibre.com> wrote:
> From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
>
> Beagle Play has a different boot flow than the AM62x SK EVM.
>
> AM62x SK EVM:
> 1. Boot rom reads UDA (User Data Area), looking for tiboot3
> 2. Boot rom finds tiboot3 and loads it
>
> Beagle Play:
> 1. Boot rom looks for tiboot3 in mmc0boot0
> 2. Boot rom finds tiboot3 and loads it
>
> Because of this difference, we need to have a different
> partitioning table than the generic TI one.
>
> Include generic TI android support and override the partitioning table
> to boot Android.
>
> Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
> Signed-off-by: Guillaume La Roque <glaroque@baylibre.com>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
> ---
> board/beagle/beagleplay/beagleplay.env | 30 ++++++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/board/beagle/beagleplay/beagleplay.env b/board/beagle/beagleplay/beagleplay.env
> index 354bc987d12b..fc29d49712db 100644
> --- a/board/beagle/beagleplay/beagleplay.env
> +++ b/board/beagle/beagleplay/beagleplay.env
> @@ -17,3 +17,33 @@ bootdir=/boot
> boot_targets=mmc1 mmc0
> bootmeths=script extlinux efi pxe
> rd_spec=-
> +
> +#if CONFIG_BOOTMETH_ANDROID
> +#include <env/ti/android.env>
> +/* Override Android partitions
> + * Required because tiboot3 is in mmc0boot0, not in UDA
> + * note that += is needed because \n is converted by space in .env files */
> +partitions=
> + name=bootloader,start=5M,size=8M,uuid=${uuid_gpt_bootloader};
> +partitions+=name=misc,start=13824K,size=512K,uuid=${uuid_gpt_misc};
> +partitions+=name=frp,size=512K,uuid=${uuid_gpt_frp};
> +partitions+=name=boot_a,size=40M,uuid=${uuid_gpt_boot_a};
> +partitions+=name=boot_b,size=40M,uuid=${uuid_gpt_boot_b};
> +partitions+=name=vendor_boot_a,size=32M,uuid=${uuid_gpt_vendor_boot_a};
> +partitions+=name=vendor_boot_b,size=32M,uuid=${uuid_gpt_vendor_boot_b};
> +partitions+=name=init_boot_a,size=8M,uuid=${uuid_gpt_init_boot_a};
> +partitions+=name=init_boot_b,size=8M,uuid=${uuid_gpt_init_boot_b};
> +partitions+=name=dtbo_a,size=8M,uuid=${uuid_gpt_dtbo_a};
> +partitions+=name=dtbo_b,size=8M,uuid=${uuid_gpt_dtbo_b};
> +partitions+=name=vbmeta_a,size=64K,uuid=${uuid_gpt_vbmeta_a};
> +partitions+=name=vbmeta_b,size=64K,uuid=${uuid_gpt_vbmeta_b};
> +partitions+=name=vbmeta_vendor_dlkm_a,size=64K,uuid=${uuid_gpt_vbmeta_vendor_dlkm_a};
> +partitions+=name=vbmeta_vendor_dlkm_b,size=64K,uuid=${uuid_gpt_vbmeta_vendor_dlkm_b};
> +partitions+=name=super,size=4608M,uuid=${uuid_gpt_super};
> +partitions+=name=metadata,size=64M,uuid=${uuid_gpt_metadata};
> +partitions+=name=persist,size=32M,uuid=${uuid_gpt_persist};
> +partitions+=name=userdata,size=-,uuid=${uuid_gpt_userdata}
> +fastboot_raw_partition_tiboot3="0x0 0x800 mmcpart 1"
> +
> +adtb_idx=2
> +#endif
>
> --
> 2.34.1
next prev parent reply other threads:[~2024-09-03 7:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 16:31 [PATCH 0/3] Add Android 14 bootflow support for AM62X and AM62P board Guillaume La Roque
2024-09-02 16:31 ` [PATCH 1/3] board: ti: am62x_evm: Add android bootflow Guillaume La Roque
2024-09-03 7:25 ` Mattijs Korpershoek
2024-09-02 16:31 ` [PATCH 2/3] board: beagle: beagleplay: Add android bootflow support Guillaume La Roque
2024-09-03 7:27 ` Mattijs Korpershoek [this message]
2024-09-02 16:31 ` [PATCH 3/3] board: ti: am62px: " Guillaume La Roque
2024-09-03 7:40 ` Mattijs Korpershoek
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=8734mh8aek.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=bb@ti.com \
--cc=glaroque@baylibre.com \
--cc=joe.hershberger@ni.com \
--cc=nm@ti.com \
--cc=robertcnelson@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
--cc=vishalm@ti.com \
/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