All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Jon Mason <jdmason@gmail.com>, Denys Dmytriyenko <denys@ti.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] arm-trusted-firmware: add upstream version 2.2
Date: Thu, 23 Jan 2020 17:05:36 -0500	[thread overview]
Message-ID: <20200123220536.GE4735@denix.org> (raw)
In-Reply-To: <CADkTA4OUcmx2wFVf9NAR8D7c_3n+303YFR3gwAWv08KgT_o+ww@mail.gmail.com>

On Thu, Jan 23, 2020 at 04:43:23PM -0500, Bruce Ashfield wrote:
> On Thu, Jan 23, 2020 at 4:00 PM Denys Dmytriyenko <denis@denix.org> wrote:
> >
> > From: Denys Dmytriyenko <denys@ti.com>
> >
> > Many BSPs require ARM Trusted Firmware (also known as Trusted Firmware-A).
> > To avoid duplicating efforts of adding very similar recipes to BSP layers,
> > add an upstream reference implementation to openembedded-core, which can be
> > customized by BSPs, if needed.
> 
> Isn't this one of the things that Jon Mason is trying to
> standardize/support in meta-arm ?
> 
> http://git.yoctoproject.org/cgit/cgit.cgi/meta-arm/tree/meta-arm/recipes-bsp/trusted-firmware-a

Ah, interesting, somehow I totally missed that one! :)

What triggered this submission is that we have our own variant in meta-ti and 
Joshua Watt was adding a very similar one to meta-rockchip:
https://lists.yoctoproject.org/g/yocto/topic/70054501#48116


> What's the delta between the two ?

Hmm, that one uses older 2.1 version. Other than that, I'll need to test to 
see if it's as adaptable and expandable as our more simplistic variants...

-- 
Denys


> > Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> > Cc: Joshua Watt <JPEWhacker@gmail.com>
> > ---
> >  .../arm-trusted-firmware_2.2.bb                    | 55 ++++++++++++++++++++++
> >  1 file changed, 55 insertions(+)
> >  create mode 100644 meta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb
> >
> > diff --git a/meta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb b/meta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb
> > new file mode 100644
> > index 0000000..3079a70
> > --- /dev/null
> > +++ b/meta/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb
> > @@ -0,0 +1,55 @@
> > +SUMMARY = "ARM Trusted Firmware"
> > +DESCRIPTION = "ARM Trusted Firmware provides a reference implementation of \
> > +Secure World software for ARMv8-A, including Exception Level 3 (EL3) software. \
> > +It provides implementations of various ARM interface standards such as the \
> > +Power State Coordination Interface (PSCI), Trusted Board Boot Requirements \
> > +(TBBR) and Secure monitor code."
> > +HOMEPAGE = "http://infocenter.arm.com/help/topic/com.arm.doc.dui0928e/CJHIDGJF.html"
> > +
> > +LICENSE = "BSD-3-Clause"
> > +LIC_FILES_CHKSUM = "file://docs/license.rst;md5=189505435dbcdcc8caa63c46fe93fa89"
> > +
> > +inherit deploy
> > +
> > +DEPENDS = "dtc-native openssl-native"
> > +
> > +PACKAGE_ARCH = "${MACHINE_ARCH}"
> > +
> > +S = "${WORKDIR}/git"
> > +B = "${WORKDIR}/build"
> > +
> > +BRANCH = "master"
> > +SRC_URI = "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=http;branch=${BRANCH}"
> > +SRCREV = "a04808c16cfc126d9fe572ae7c4b5a3d39de5796"
> > +
> > +ATF_BINARY ??= "bl31"
> > +ATF_SUFFIX ??= "bin"
> > +ATF_TARGET ??= "all"
> > +
> > +CFLAGS[unexport] = "1"
> > +LDFLAGS[unexport] = "1"
> > +AS[unexport] = "1"
> > +LD[unexport] = "1"
> > +
> > +do_configure[noexec] = "1"
> > +
> > +EXTRA_OEMAKE = '-C ${S} BUILD_BASE=${B} DEBUG=0 CROSS_COMPILE="${TARGET_PREFIX}" \
> > +               PLAT="${ATF_PLATFORM}" TARGET_BOARD="${ATF_BOARD}" ${PACKAGECONFIG_CONFARGS}'
> > +
> > +do_compile() {
> > +       oe_runmake ${ATF_TARGET}
> > +}
> > +
> > +do_install() {
> > +       install -d ${D}/boot
> > +       install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${D}/boot/
> > +}
> > +
> > +do_deploy() {
> > +       install -d ${DEPLOYDIR}
> > +       install -m 0644 ${B}/${ATF_PLATFORM}/${ATF_BOARD}/release/${ATF_BINARY}.${ATF_SUFFIX} ${DEPLOYDIR}/
> > +}
> > +addtask deploy before do_build after do_compile
> > +
> > +FILES_${PN} = "/boot"
> > +SYSROOT_DIRS += "/boot"
> > --
> > 2.7.4
> >
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> 
> 
> 
> -- 
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
> 


  reply	other threads:[~2020-01-23 22:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23 20:59 [PATCH] arm-trusted-firmware: add upstream version 2.2 Denys Dmytriyenko
2020-01-23 21:43 ` Bruce Ashfield
2020-01-23 22:05   ` Denys Dmytriyenko [this message]
2020-01-23 22:10     ` Joshua Watt
2020-01-23 22:14       ` Bruce Ashfield
2020-01-23 22:16       ` Denys Dmytriyenko
2020-01-24 22:30         ` Jon Mason
2020-01-24 22:46           ` Denys Dmytriyenko
2020-01-24 23:00             ` Jon Mason
2020-01-23 22:15     ` Bruce Ashfield
2020-01-24 22:26       ` Jon Mason
2020-01-24 22:24     ` Jon Mason
2020-01-23 22:17   ` Ross Burton
2020-01-23 22:39     ` Andre McCurdy
2020-01-23 22:43       ` Denys Dmytriyenko
2020-01-24 11:42         ` Ross Burton
2020-01-24 17:05           ` Khem Raj
2020-01-24 22:47             ` Jon Mason
2020-01-24 22:59             ` Denys Dmytriyenko
2020-01-23 22:50     ` Richard Purdie
2020-01-24 22:42       ` Jon Mason
2020-01-23 22:57     ` akuster808

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=20200123220536.GE4735@denix.org \
    --to=denis@denix.org \
    --cc=bruce.ashfield@gmail.com \
    --cc=denys@ti.com \
    --cc=jdmason@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.