Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [git commit] configs/ti_am64x_sk_defconfig: fix BR2_TARGET_OPTEE_OS_PLATFORM setting
Date: Fri, 22 Mar 2024 21:05:08 +0100	[thread overview]
Message-ID: <871q822ft7.fsf@48ers.dk> (raw)
In-Reply-To: <20240319213722.5A147835FC@busybox.osuosl.org> (Yann E. MORIN's message of "Tue, 19 Mar 2024 22:15:02 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > commit: https://git.buildroot.net/buildroot/commit/?id=fde806f8220720b95cb3973fe9d7e55057a1bee7
 > branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master

 > Using PLATFORM=k3 can leads to a runtime boot crash on some K3 SoC (e.g.
 > j721e) because the optee flavor is missing.

 > We could use BR2_TARGET_OPTEE_OS_PLATFORM=k3 and
 > BR2_TARGET_OPTEE_OS_PLATFORM_FLAVOR=am64x but we actually can use
 > BR2_TARGET_OPTEE_OS_PLATFORM=k3-am64x as explained in the optee-os
 > Makefile [1]:

 >   # If $(PLATFORM) is defined and contains a hyphen, parse it as
 >   # $(PLATFORM)-$(PLATFORM_FLAVOR) for convenience

 > This is how meta-ti set the optee-os platform:

 >   meta-ti]$ git grep OPTEEMACHINE
 >   meta-ti-bsp/conf/machine/am437x-hs-evm.conf:OPTEEMACHINE = "ti-am43xx"
 >   meta-ti-bsp/conf/machine/am57xx-hs-evm.conf:OPTEEMACHINE = "ti-am57xx"
 >   meta-ti-bsp/conf/machine/beagleplay.conf:OPTEEMACHINE = "k3-am62x"
 >   meta-ti-bsp/conf/machine/dra7xx-hs-evm.conf:OPTEEMACHINE = "ti-dra7xx"
 >   meta-ti-bsp/conf/machine/include/am62axx.inc:OPTEEMACHINE = "k3-am62x"
 >   meta-ti-bsp/conf/machine/include/am62pxx.inc:OPTEEMACHINE = "k3-am62x"
 >   meta-ti-bsp/conf/machine/include/am62xx.inc:OPTEEMACHINE = "k3-am62x"
 >   meta-ti-bsp/conf/machine/include/am64xx.inc:OPTEEMACHINE = "k3-am64x"
 >   meta-ti-bsp/conf/machine/include/am65xx.inc:OPTEEMACHINE = "k3-am65x"
 >   meta-ti-bsp/conf/machine/include/j7200.inc:OPTEEMACHINE = "k3-j721e"
 >   meta-ti-bsp/conf/machine/include/j721e.inc:OPTEEMACHINE = "k3-j721e"
 >   meta-ti-bsp/conf/machine/include/j721s2.inc:OPTEEMACHINE = "k3-j784s4"
 >   meta-ti-bsp/conf/machine/include/j722s.inc:OPTEEMACHINE = "k3-am62x"
 >   meta-ti-bsp/conf/machine/include/j784s4.inc:OPTEEMACHINE = "k3-j784s4"

 >   meta-ti uses the OPTEEMACHINE to set optee-os platform [2].

 > [1] https://github.com/OP-TEE/optee_os/blob/4.0.0/Makefile#L37
 > [2] https://git.yoctoproject.org/meta-arm/tree/meta-arm/recipes-security/optee/optee-os.inc?h=4.0.3#n23

 > Suggested-by: Romain Naour <romain.naour@smile.fr>
 > Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
 > Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>

Committed to 2024.02.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-03-22 20:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 21:15 [Buildroot] [git commit] configs/ti_am64x_sk_defconfig: fix BR2_TARGET_OPTEE_OS_PLATFORM setting Yann E. MORIN
2024-03-22 20:05 ` Peter Korsgaard [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=871q822ft7.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=yann.morin.1998@free.fr \
    /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