mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] tf-a: new package for ARM trusted firmware A
Date: Mon, 17 Feb 2020 17:33:57 +0100	[thread overview]
Message-ID: <CABDcavbURWVEugsZ4Y-=0X+7ifX59r2i6=P4jwhuMawx+imLYA@mail.gmail.com> (raw)
In-Reply-To: <20200217172553.7ffd12a4@litschi.hi.pengutronix.de>

Hi Michael,

El lun., 17 feb. 2020 a las 17:26, Michael Tretter
(<m.tretter@pengutronix.de>) escribió:
>
> On Wed, 12 Feb 2020 17:40:33 +0100, Ahmad Fatoum wrote:
> > Trusted Firmware-A (TF-A) is a reference implementation of secure world
> > software for Arm A-Profile architectures (Armv8-A and Armv7-A).
>
> I successfully built the TF-A BL31 for the ZynqMP using this rule.
>
> However, I saw that the TF-A build uses the current git commitish for
> BUILD_STRING, which will be written into the binary. If I build the
> TF-A with this rule, this ends up to be the commitish of the BSP. I'm
> not sure if I actually want this, but I don't know what to put there
> instead.

Since we finally agreed to keep TF_A_EXTRA_ARGS in the final TF-A rule
files, you can actually set BUILD_STRING to anything you want. Just
include BUILD_STRING=whatever in the TF_A_EXTRA_ARGS parameter.

Best,

Guillermo

>
> Michael
>
> >
> > Cc: Alejandro Vazquez <avazquez.dev@gmail.com>
> > Signed-off-by: Rouven Czerwinski <rouven@czerwinskis.de>
> > Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> > ---
> > v1 -> v2:
> >  - Made TF_A_ARCH_MAJOR configurable to support 32 bit ARMv8 (Guillermo)
> >  - Replaces stm32mp-specific TF_A_DTB with TF_A_EXTRA_ARGS to contain
> >    all board/vendor specific options
> >  - removed reference to no longer existing CREDITS file
> >  - removed TF_A_MAKE_OPT contents that are set elsewhere
> >  - reduced uses of += in favor of directly appending to the string
> >  - delete old build directory in prepare instead of compile
> >  - use default compile stage (Guillermo)
> >  - install artifacts to sysroot /usr/lib/firmware in install stage
> >  - install artifacts to IMAGEDIR in targetinstall
> >  - fix clean stage to delete proper artifacts
> > ---
> >  platforms/tf-a.in | 138 ++++++++++++++++++++++++++++++++++++++++++++++
> >  rules/tf-a.make   | 114 ++++++++++++++++++++++++++++++++++++++
> >  2 files changed, 252 insertions(+)
> >  create mode 100644 platforms/tf-a.in
> >  create mode 100644 rules/tf-a.make
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de



-- 
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2020-02-17 16:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12 16:40 Ahmad Fatoum
2020-02-13 12:59 ` Guillermo Rodriguez Garcia
2020-02-13 13:30   ` Ahmad Fatoum
2020-02-13 14:25     ` Guillermo Rodriguez Garcia
2020-02-13 14:28       ` Ahmad Fatoum
2020-02-13 14:32         ` Ahmad Fatoum
2020-02-13 14:35           ` Guillermo Rodriguez Garcia
2020-02-13 14:44             ` Ahmad Fatoum
2020-02-13 14:49               ` Ahmad Fatoum
2020-02-13 15:05               ` Guillermo Rodriguez Garcia
2020-02-13 15:08                 ` Ahmad Fatoum
2020-02-13 15:24                   ` Guillermo Rodriguez Garcia
2020-02-13 15:27                     ` Ahmad Fatoum
2020-02-13 15:33                       ` Guillermo Rodriguez Garcia
2020-02-14 10:57                         ` Alex Vazquez
2020-02-14 13:19 ` Michael Olbrich
2020-02-19 10:10   ` Ahmad Fatoum
2020-02-17 16:25 ` Michael Tretter
2020-02-17 16:33   ` Guillermo Rodriguez Garcia [this message]
2020-02-18  7:35     ` Michael Olbrich
2020-02-18  9:02       ` Guillermo Rodriguez Garcia
2020-02-19  7:48         ` Michael Tretter

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='CABDcavbURWVEugsZ4Y-=0X+7ifX59r2i6=P4jwhuMawx+imLYA@mail.gmail.com' \
    --to=guille.rodriguez@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /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