All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Diego Sueiro" <diego.sueiro@arm.com>
To: "denis@denix.org" <denis@denix.org>,
	"meta-arm@lists.yoctoproject.org"
	<meta-arm@lists.yoctoproject.org>
Cc: nd <nd@arm.com>
Subject: Re: [meta-arm] [PATCH 2/5] trusted-firmware-a: Deliver binaries artefacts to sysroot/firmware
Date: Tue, 19 May 2020 06:10:46 +0000	[thread overview]
Message-ID: <AM0PR08MB39876088695CD79E3EECB31E92B90@AM0PR08MB3987.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20200519040543.GP11927@denix.org>

> -----Original Message-----
> From: meta-arm@lists.yoctoproject.org <meta-arm@lists.yoctoproject.org>
> On Behalf Of Denys Dmytriyenko via lists.yoctoproject.org
> Sent: 19 May 2020 05:06
> To: meta-arm@lists.yoctoproject.org
> Cc: nd <nd@arm.com>; Diego Sueiro <Diego.Sueiro@arm.com>
> Subject: Re: [meta-arm] [PATCH 2/5] trusted-firmware-a: Deliver binaries
> artefacts to sysroot/firmware
> 
> On Tue, Apr 21, 2020 at 08:33:52AM +0100, Diego Sueiro wrote:
> > Make usage of the do_install task to deliver binaries artefacts to the
> > `sysroot/firmware` path, making it easier for other recipes that
> > depends on it to make usage of those binaries instead of copying them
> > from the DEPLOY_DIR_IMAGE.
> >
> > This recipe still deploys its artefacts to DEPLOY_DIR_IMAGE.
> >
> > Change-Id: I97b97f90b23746557e981f8de10159c5f475becd
> > Issue-Id: SCM-888
> > Signed-off-by: Diego Sueiro <diego.sueiro@arm.com>
> > ---
> >  .../trusted-firmware-a/trusted-firmware-a-fvp.inc  |  7 +++--
> >  .../trusted-firmware-a/trusted-firmware-a.inc      | 31 +++++++++++++-------
> --
> >  2 files changed, 21 insertions(+), 17 deletions(-)
> >
> > diff --git
> > a/meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-fvp.i
> > nc
> > b/meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-fvp.i
> > nc
> > index 6e7eba3..3e58ecf 100644
> > ---
> > a/meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-fvp.i
> > nc
> > +++ b/meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-f
> > +++ vp.inc
> > @@ -12,9 +12,9 @@ TFA_MBEDTLS = "1"
> >  TFA_UBOOT = "1"
> >  TFA_BUILD_TARGET = "bl1 bl2 bl31 dtbs fiptool"
> >
> > -do_deploy[depends] += "virtual/kernel:do_deploy"
> > +do_install[depends] += "virtual/kernel:do_deploy"
> >
> > -do_deploy_append() {
> > +do_install_append() {
> >      ./tools/fiptool/fiptool create \
> >          --tb-fw ${S}/${TFA_BUILD_DIR}/bl2.bin \
> >          --soc-fw ${S}/${TFA_BUILD_DIR}/bl31.bin \ @@ -26,6 +26,5 @@
> > do_deploy_append() {
> >
> >      ./tools/fiptool/fiptool info fip.bin
> >
> > -    install -m 0644 ${S}/fip.bin ${DEPLOYDIR}/fip-fvp.bin
> > +    install -m 0644 ${S}/fip.bin ${D}/firmware/fip-fvp.bin
> >  }
> > -
> > diff --git
> > a/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
> > b/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
> > index d7c4fbf..93ca199 100644
> > --- a/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
> > +++ b/meta-arm/recipes-bsp/trusted-firmware-a/trusted-firmware-a.inc
> > @@ -5,7 +5,7 @@ PROVIDES = "virtual/trusted-firmware-a"
> >
> >  PACKAGE_ARCH = "${MACHINE_ARCH}"
> >
> > -inherit deploy
> > +inherit deploy nopackages
> 
> I totally missed this ^^^ - may I ask why nopackages was added here?

Because this recipe is not generating packages to be installed in the rootfs.

> 
> 
> >  COMPATIBLE_MACHINE ?= "invalid"
> >
> > @@ -42,12 +42,12 @@ SRCREV_FORMAT_append =
> > "${@bb.utils.contains('TFA_MBEDTLS', '1', '_mbedtls', '',  TFA_UBOOT ?=
> "0"
> >
> >  # What to build
> > -# By default we only build bl1, do_deploy will install
> > +# By default we only build bl1, do_deploy will copy
> >  # everything listed in this variable (by default bl1.bin)
> > TFA_BUILD_TARGET ?= "bl1"
> >
> >  # What to install
> > -# do_deploy will install everything listed in this
> > +# do_install and do_deploy will install everything listed in this
> >  # variable. It is set by default to TFA_BUILD_TARGET
> > TFA_INSTALL_TARGET ?= "${TFA_BUILD_TARGET}"
> >
> > @@ -60,9 +60,8 @@ LDFLAGS[unexport] = "1"
> >  AS[unexport] = "1"
> >  LD[unexport] = "1"
> >
> > -# No configure or install
> > +# No configure
> >  do_configure[noexec] = "1"
> > -do_install[noexec] = "1"
> >
> >  # We need dtc for dtbs compilation
> >  # We need openssl for fiptool
> > @@ -87,27 +86,27 @@ do_compile() {
> >      oe_runmake ${TFA_BUILD_TARGET}
> >  }
> >
> > -do_deploy() {
> > -    install -d -m 755 ${DEPLOYDIR}
> > +do_install() {
> > +    install -d -m 755 ${D}/firmware
> >      for atfbin in ${TFA_INSTALL_TARGET}; do
> >          if [ "$atfbin" = "all" ]; then
> >              # Target all is not handled by default
> > -            bberror "all as TFA_INSTALL_TARGET is not handled by do_deploy"
> > +            bberror "all as TFA_INSTALL_TARGET is not handled by do_install"
> >              bberror "Please specify valid targets in TFA_INSTALL_TARGET or"
> > -            bberror "rewrite or turn off do_deploy"
> > +            bberror "rewrite or turn off do_install"
> >              exit 1
> >          elif [ -f ${S}/${TFA_BUILD_DIR}/$atfbin.bin ]; then
> >              echo "Install $atfbin.bin"
> >              install -m 0644 ${S}/${TFA_BUILD_DIR}/$atfbin.bin \
> > -                ${DEPLOYDIR}/$atfbin-${TFA_PLATFORM}.bin
> > +                ${D}/firmware/$atfbin-${TFA_PLATFORM}.bin
> >          elif [ -f ${S}/${TFA_BUILD_DIR}/$atfbin.elf ]; then
> >              echo "Install $atfbin.elf"
> >              install -m 0644 ${S}/${TFA_BUILD_DIR}/$atfbin.elf \
> > -                ${DEPLOYDIR}/$atfbin-${TFA_PLATFORM}.elf
> > +                ${D}/firmware/$atfbin-${TFA_PLATFORM}.elf
> >          elif [ -f ${S}/${TFA_BUILD_DIR}/$atfbin ]; then
> >              echo "Install $atfbin"
> >              install -m 0644 ${S}/${TFA_BUILD_DIR}/$atfbin \
> > -                ${DEPLOYDIR}/$atfbin-${TFA_PLATFORM}
> > +                ${D}/firmware/$atfbin-${TFA_PLATFORM}
> >          elif [ "$atfbin" = "dtbs" ]; then
> >              echo "dtbs install, skipped"
> >          elif [ -f ${S}/tools/$atfbin/$atfbin ]; then @@ -118,4
> > +117,10 @@ do_deploy() {
> >          fi
> >      done
> >  }
> > -addtask deploy before do_build after do_compile
> > +
> > +SYSROOT_DIRS += "/firmware"
> > +
> > +do_deploy() {
> > +    cp -rf ${D}/firmware/* ${DEPLOYDIR}/ } addtask deploy after
> > +do_install
> > --
> > 2.7.4
> >
> 
> >


  reply	other threads:[~2020-05-19  6:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21  7:33 [PATCH 0/5] tf-a recipe improvements and new recipes for SCP and firmware image for Juno Diego Sueiro
2020-04-21  7:33 ` [PATCH 1/5] meta-arm-bsp:trusted-firmware-a: Remove custom do_clean task Diego Sueiro
2020-04-21  7:33 ` [PATCH 2/5] trusted-firmware-a: Deliver binaries artefacts to sysroot/firmware Diego Sueiro
2020-05-19  4:05   ` [meta-arm] " Denys Dmytriyenko
2020-05-19  6:10     ` Diego Sueiro [this message]
2020-05-19  6:40       ` Denys Dmytriyenko
2020-05-19  9:11         ` Diego Sueiro
2020-04-21  7:33 ` [PATCH 3/5] meta-arm-bsp: Introduce the scp-firmware-juno recipe Diego Sueiro
2020-04-21  7:33 ` [PATCH 4/5] meta-arm-bsp: Introduce firmware-image-juno recipe Diego Sueiro
2020-04-21  7:33 ` [PATCH 5/5] arm-autonomy: Append firmware-image-juno recipe to collect Xen binaries Diego Sueiro
2020-04-21  8:10 ` [meta-arm] [PATCH 0/5] tf-a recipe improvements and new recipes for SCP and firmware image for Juno Bertrand Marquis
2020-04-23 18:35   ` Jon Mason

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=AM0PR08MB39876088695CD79E3EECB31E92B90@AM0PR08MB3987.eurprd08.prod.outlook.com \
    --to=diego.sueiro@arm.com \
    --cc=denis@denix.org \
    --cc=meta-arm@lists.yoctoproject.org \
    --cc=nd@arm.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.