From: Che-Wei Chuang via buildroot <buildroot@buildroot.org>
To: Che-Wei Chuang via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 0/2] board/andes: add AE350 OP-TEE support
Date: Thu, 8 Jan 2026 18:10:44 +0800 [thread overview]
Message-ID: <aV-CpLh7NMHvtq_A@swlinux01> (raw)
In-Reply-To: <20260107150232.7b672513@windsurf>
Hi Thomas,
On Wed, Jan 07, 2026 at 03:02:32PM +0100, Thomas Petazzoni wrote:
> So if the OP-TEE enabled build is the "future" in terms of how AE350
> will be running a Linux kernel, then this should be supported directly
> into the existing AE350 configuration.
Thank you very much for the detailed feedback and kind words.
I will discuss this internally with Leo to integrate the OP-TEE and non-OP-TEE configurations into a single official AE350 defconfig.
We will provide an update as soon as we have a concrete plan.
Best regards, Che-Wei
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-01-08 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 7:33 [Buildroot] [PATCH 0/2] board/andes: add AE350 OP-TEE support Che-Wei Chuang via buildroot
2026-01-07 7:34 ` [Buildroot] [PATCH 1/2] DEVELOPERS: add Che-Wei Chuang for andes boards Che-Wei Chuang via buildroot
2026-01-07 7:34 ` [Buildroot] [PATCH 2/2] board/andes: add AE350 OP-TEE board support Che-Wei Chuang via buildroot
2026-01-07 9:48 ` Vincent Jardin via buildroot
2026-01-07 14:02 ` [Buildroot] [PATCH 0/2] board/andes: add AE350 OP-TEE support Thomas Petazzoni via buildroot
2026-01-08 10:10 ` Che-Wei Chuang via buildroot [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=aV-CpLh7NMHvtq_A@swlinux01 \
--to=buildroot@buildroot.org \
--cc=cnoize@andestech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.