From: Jan Kiszka <jan.kiszka@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Cc: Nishanth Menon <nm@ti.com>, Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH 0/9] Add support for BeaglePlay
Date: Mon, 8 Jan 2024 13:18:42 +0100 [thread overview]
Message-ID: <fc713cee-f2f7-4906-aa4e-8641ed0cc352@siemens.com> (raw)
In-Reply-To: <20273c39-0197-4e84-8865-70a5414f8061@ilbers.de>
On 08.01.24 09:51, Anton Mikanovich wrote:
> 07/01/2024 14:54, '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.10. Major features are working but others may not
>> (upstream-based integrations are still uncommon...).
>>
>> Patch 1 obsoletes patch 8 from the recent RISC-V series
>> (https://groups.google.com/g/isar-users/c/0QBjhzcs3ac/m/slLUMUUbBAAJ).
>>
>> Still on my todo list is demoing RPMB and fTPM on this board, altough it
>> does not support real security (GP variant only).
>>
>> Jan
>
> Hello Jan,
>
> Please cover this target under full CI in the next version of patchset
> if any.
Sure - but where exactly? CrossTest?
Jan
--
Siemens AG, Technology
Linux Expert Center
next prev parent reply other threads:[~2024-01-08 12:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-07 12:54 Jan Kiszka
2024-01-07 12:54 ` [PATCH 1/9] meta-isar: linux-mainline: Update to 6.6.10 Jan Kiszka
2024-01-07 12:54 ` [PATCH 2/9] optee-os: Switch default binary to tee-raw.bin Jan Kiszka
2024-01-07 12:54 ` [PATCH 3/9] u-boot-custom: Allow to set BL31 and TEE from recipes Jan Kiszka
2024-01-07 12:54 ` [PATCH 4/9] u-boot-custom: Allow to define different installation binaries Jan Kiszka
2024-01-07 12:54 ` [PATCH 5/9] beagleplay: Add TF-A recipe Jan Kiszka
2024-01-08 12:49 ` Florian Bezdeka
2024-01-07 12:54 ` [PATCH 6/9] beagleplay: Add OP-TEE recipe Jan Kiszka
2024-01-07 12:54 ` [PATCH 7/9] beagleplay: Add U-Boot recipe Jan Kiszka
2024-01-08 13:17 ` Florian Bezdeka
2024-01-08 13:19 ` Jan Kiszka
2024-01-07 12:54 ` [PATCH 8/9] Add support for the BeaglePlay board Jan Kiszka
2024-01-07 16:40 ` Jan Kiszka
2024-01-07 12:54 ` [PATCH 9/9] expand-on-first-boot: Preserve MBR on expansion of GPT disks Jan Kiszka
2024-01-08 8:51 ` [PATCH 0/9] Add support for BeaglePlay Anton Mikanovich
2024-01-08 12:18 ` Jan Kiszka [this message]
2024-01-08 13:53 ` Anton Mikanovich
2024-01-08 15:07 ` Jan Kiszka
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=fc713cee-f2f7-4906-aa4e-8641ed0cc352@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=amikan@ilbers.de \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=nm@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