From: "Jon Mason" <jdmason@kudzu.us>
To: Diego Sueiro <diego.sueiro@arm.com>
Cc: meta-arm@lists.yoctoproject.org
Subject: Re: [meta-arm] [PATCH] arm/fiptool : provides fiptool for packaging
Date: Wed, 24 Jun 2020 14:39:41 -0400 [thread overview]
Message-ID: <20200624183940.GA5282@kudzu.us> (raw)
In-Reply-To: <14975.1592895937470124128@lists.yoctoproject.org>
On Tue, Jun 23, 2020 at 12:05:37AM -0700, Diego Sueiro wrote:
> On Mon, Jun 22, 2020 at 03:16 PM, Khasim Mohammed wrote:
>
> >
> > Firmware Image Package (FIP), is a packaging format used
> > by TF-A to package the firmware images in a single binary,
> > this tool is used to package the binaries in FIP format.
> >
> > Change-Id: Ie4108915c5d63be340d6f53148a6dff03d6d48e7
> > Issue-Id: PLATFORMS-3134
> > Signed-off-by: Khasim Syed Mohammed <khasim.mohammed@arm.com>
>
> Reviewed-by: Diego Sueiro <diego.sueiro@arm.com>
Pulled into master.
Thanks,
Jon
>
> > ---
> > .../fiptool/fiptool-native_2.3.bb | 29 +++++++++++++++++++
> > 1 file changed, 29 insertions(+)
> > create mode 100644 meta-arm/recipes-devtools/fiptool/fiptool-native_2.3.bb
> >
> > diff --git a/meta-arm/recipes-devtools/fiptool/fiptool-native_2.3.bb
> > b/meta-arm/recipes-devtools/fiptool/fiptool-native_2.3.bb
> > new file mode 100644
> > index 0000000..25ca111
> > --- /dev/null
> > +++ b/meta-arm/recipes-devtools/fiptool/fiptool-native_2.3.bb
> > @@ -0,0 +1,29 @@
> > +# Firmware Image Package (FIP)
> > +# It is a packaging format used by TF-A to package the
> > +# firmware images in a single binary.
> > +
> > +DESCRIPTION = "fiptool - Trusted Firmware tool for packaging"
> > +LICENSE = "BSD-3-Clause"
> > +
> > +SRC_URI =
> > "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;destsuffix=fiptool-${PV};protocol=https;"
> > +LIC_FILES_CHKSUM =
> > "file://docs/license.rst;md5=189505435dbcdcc8caa63c46fe93fa89"
> > +
> > +# Use fiptool from TF-A v2.3
> > +SRCREV = "ecd27ad85f1eba29f6bf92c39dc002c85b07dad5"
> > +
> > +DEPENDS += "openssl-native"
> > +
> > +inherit native
> > +
> > +do_compile () {
> > + # These changes are needed to have the fiptool compiling and executing
> > properly
> > + sed -i '/^LDLIBS/ s,$, \$\{BUILD_LDFLAGS},' ${S}/tools/fiptool/Makefile
> > + sed -i '/^INCLUDE_PATHS/ s,$, \$\{BUILD_CFLAGS},'
> > ${S}/tools/fiptool/Makefile
> > +
> > + oe_runmake fiptool
> > +}
> > +
> > +do_install () {
> > + install -d ${D}${bindir}/
> > + install -m 0755 tools/fiptool/fiptool ${D}${bindir}
> > +}
> > --
> > 2.17.1
> >
> >
>
prev parent reply other threads:[~2020-06-24 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 14:16 [PATCH] arm/fiptool : provides fiptool for packaging Khasim Mohammed
2020-06-23 7:05 ` Diego Sueiro
2020-06-24 18:39 ` Jon Mason [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=20200624183940.GA5282@kudzu.us \
--to=jdmason@kudzu.us \
--cc=diego.sueiro@arm.com \
--cc=meta-arm@lists.yoctoproject.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.