public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Uladzimir Bely <ubely@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 00/11] Add support for BeaglePlay
Date: Wed, 20 Mar 2024 18:17:30 +0300	[thread overview]
Message-ID: <0574d422562463994083fbfe976043b2e1dd5371.camel@ilbers.de> (raw)
In-Reply-To: <cover.1705239574.git.jan.kiszka@siemens.com>

On Sun, 2024-01-14 at 14:39 +0100, 'Jan Kiszka' via isar-users wrote:
> This adds basic support for the BeaglePlay, a TI AM62x based ARM64
> board (https://www.beagleboard.org/boards/beagleplay). The
> integration
> is upstream-based: U-Boot 2024.01-rc6, TF-A 2.10, OP-TEE 4.0.0 and
> kernel 6.6.11. Major features are working but others may not
> (upstream-based integrations are still uncommon...).
> 
> Patch 1 obsoletes patch 7 from the recent RISC-V series v2
> (
> https://groups.google.com/g/isar-users/c/0QBjhzcs3ac/m/KKPN9k8QAgAJ).
> 
> Still on my todo list is demoing RPMB and fTPM on this board, altough
> it
> does not support real security (GP variant only).
> 
> Changes in v2:
>  - fix and simplify the hybrid partition table generation
>    (previous approach caused bmap corruptions)
>  - hook into CI
>  - update to 6.6.11
> 
> Jan
> 
> Jan Kiszka (11):
>   meta-isar: linux-mainline: Update to 6.6.11
>   optee-os: Switch default binary to tee-raw.bin
>   u-boot-custom: Allow to set BL31 and TEE from recipes
>   u-boot-custom: Allow to define different installation binaries
>   beagleplay: Add TF-A recipe
>   beagleplay: Add OP-TEE recipe
>   beagleplay: Add U-Boot recipe
>   wic: Add hybrid-boot bootloader source plugin
>   expand-on-first-boot: Preserve MBR on expansion of GPT disks
>   Add support for the BeaglePlay board
>   ci: Add beagleplay to full CI test
> 
>  RECIPE-API-CHANGELOG.md                       |  5 ++
>  kas/machine/Kconfig                           |  5 ++
>  kas/machine/beagleplay.yaml                   |  9 +++
>  meta-isar/conf/machine/beagleplay.conf        | 20 +++++
>  meta-isar/conf/mc.conf                        |  1 +
>  .../conf/multiconfig/beagleplay-bookworm.conf |  7 ++
>  .../optee-os/optee-os-beagleplay_4.0.0.bb     | 18 +++++
>  .../trusted-firmware-a-beagleplay_2.10.bb     | 15 ++++
>  ...2x-Add-basic-initialization-for-usb-.patch | 80
> +++++++++++++++++++
>  .../recipes-bsp/u-boot/files/rules-beagleplay | 16 ++--
>  .../u-boot/u-boot-beagleplay_2024.01.bb       | 41 ++++++++++
>  ...ne_5.4.203.bb => linux-mainline_6.6.11.bb} |  6 +-
>  .../lib/wic/canned-wks/beagleplay.wks.in      | 11 +++
>  meta/recipes-bsp/optee-os/optee-os.inc        |  2 +-
>  .../u-boot/files/debian/rules.tmpl            |  2 +-
>  meta/recipes-bsp/u-boot/u-boot-custom.inc     | 12 ++-
>  .../files/expand-last-partition.sh            | 10 +++
>  .../lib/wic/plugins/source/hybrid-boot.py     | 38 +++++++++
>  testsuite/citest.py                           |  1 +
>  19 files changed, 283 insertions(+), 16 deletions(-)
>  create mode 100644 kas/machine/beagleplay.yaml
>  create mode 100644 meta-isar/conf/machine/beagleplay.conf
>  create mode 100644 meta-isar/conf/multiconfig/beagleplay-
> bookworm.conf
>  create mode 100644 meta-isar/recipes-bsp/optee-os/optee-os-
> beagleplay_4.0.0.bb
>  create mode 100644 meta-isar/recipes-bsp/trusted-firmware-a/trusted-
> firmware-a-beagleplay_2.10.bb
>  create mode 100644 meta-isar/recipes-bsp/u-boot/files/0001-TMP-
> board-ti-am62x-Add-basic-initialization-for-usb-.patch
>  copy meta/recipes-bsp/u-boot/files/debian/rules.tmpl => meta-
> isar/recipes-bsp/u-boot/files/rules-beagleplay (55%)
>  create mode 100644 meta-isar/recipes-bsp/u-boot/u-boot-
> beagleplay_2024.01.bb
>  rename meta-isar/recipes-kernel/linux/{linux-mainline_5.4.203.bb =>
> linux-mainline_6.6.11.bb} (85%)
>  create mode 100644 meta-isar/scripts/lib/wic/canned-
> wks/beagleplay.wks.in
>  create mode 100644 meta/scripts/lib/wic/plugins/source/hybrid-
> boot.py
> 
> -- 
> 2.35.3
> 

Applied to next.

Additionally, checked the images built with the patchset together with
hardware targets we have in the lab that also use linux-mainline this
patchset updates to 6.6.11.

      parent reply	other threads:[~2024-03-20 15:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-14 13:39 Jan Kiszka
2024-01-14 13:39 ` [PATCH v2 01/11] meta-isar: linux-mainline: Update to 6.6.11 Jan Kiszka
2024-01-14 13:39 ` [PATCH v2 02/11] optee-os: Switch default binary to tee-raw.bin Jan Kiszka
2024-01-14 13:39 ` [PATCH v2 03/11] u-boot-custom: Allow to set BL31 and TEE from recipes Jan Kiszka
2024-01-14 13:39 ` [PATCH v2 04/11] u-boot-custom: Allow to define different installation binaries Jan Kiszka
2024-01-14 13:39 ` [PATCH v2 05/11] beagleplay: Add TF-A recipe Jan Kiszka
2024-01-14 13:39 ` [PATCH v2 06/11] beagleplay: Add OP-TEE recipe Jan Kiszka
2024-01-14 13:39 ` [PATCH v2 07/11] beagleplay: Add U-Boot recipe Jan Kiszka
2024-01-14 13:39 ` [PATCH v2 08/11] wic: Add hybrid-boot bootloader source plugin Jan Kiszka
2024-01-14 13:39 ` [PATCH v2 09/11] expand-on-first-boot: Preserve MBR on expansion of GPT disks Jan Kiszka
2024-01-14 13:39 ` [PATCH v2 10/11] Add support for the BeaglePlay board Jan Kiszka
2024-01-14 13:39 ` [PATCH v2 11/11] ci: Add beagleplay to full CI test Jan Kiszka
2024-03-20 15:17 ` Uladzimir Bely [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=0574d422562463994083fbfe976043b2e1dd5371.camel@ilbers.de \
    --to=ubely@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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