Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yu-Chien Peter Lin via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: tim609@andestech.com, alvinga@andestech.com,
	Etienne Carriere <etienne.carriere@foss.st.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] boot: optee-os: enable RISC-V (64-bit) architecture
Date: Mon, 16 Sep 2024 13:44:01 +0800	[thread overview]
Message-ID: <ZufFoUvbRiVHFCCq@APC323> (raw)
In-Reply-To: <15d03499-bfe8-4b53-bc24-af06ab9fb97a@mind.be>

On Sat, Sep 14, 2024 at 06:02:08PM +0200, Arnout Vandecappelle wrote:
> 
> On 17/08/2024 13:22, Yu Chien Peter Lin via buildroot wrote:
> > OP-TEE OS and TAs can run on RISC-V (64-bit) machines, so allow
> > optee-os to be compiled for the new architecture.
> > 
> > Signed-off-by: Yu Chien Peter Lin <peterlin@andestech.com>
> 
>  Hi Peter,
> 
>  Applied to master, thanks. I made some changes, see below, please check if
> things are still OK!

Hi Arnout,

I've confirmed that the qemu_riscv64_virt_defconfig generates the RISC-V
OP-TEE binaries, thanks for handling this.

Best regards,
Peter Lin
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-09-16  5:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-17 11:22 [Buildroot] [PATCH] boot: optee-os: enable RISC-V (64-bit) architecture Yu Chien Peter Lin via buildroot
2024-09-11  7:44 ` Yu-Chien Peter Lin via buildroot
2024-09-14 16:02 ` Arnout Vandecappelle via buildroot
2024-09-16  5:44   ` Yu-Chien Peter Lin 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=ZufFoUvbRiVHFCCq@APC323 \
    --to=buildroot@buildroot.org \
    --cc=alvinga@andestech.com \
    --cc=arnout@mind.be \
    --cc=etienne.carriere@foss.st.com \
    --cc=peterlin@andestech.com \
    --cc=tim609@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox