All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] uboot and arm trusted firmware build added to juno board
Date: Thu, 28 Apr 2016 21:57:33 +0200	[thread overview]
Message-ID: <20160428215733.378ce9ac@free-electrons.com> (raw)
In-Reply-To: <572246AE.9070804@synopsys.com>

Hello,

On Thu, 28 Apr 2016 18:21:50 +0100, Joao Pinto wrote:

> # Automatically find the U-Boot binary
> ifeq ($(BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME), )

use qstrip, otherwise this will never be true. Also, remove the space
after the comma.

> ATFIRMWARE_PAYLOAD_PATH = $(BINARIES_DIR)/"u-boot.bin"

Remove the quotes.

> else
> ATFIRMWARE_PAYLOAD_PATH = $(BINARIES_DIR)/$(BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME)

Use qstrip here as well.

Are you sure it's either u-boot.bin or a custom name? There are plenty
of other possible image names in uboot.mk (but quite certainly not all
of them apply to ARM64).

> In terms of the SCP_FW, I think for now is more reliable to make the final stage
> manually if using a Juno board. From my experience stuff in Linaro repositories
> change frequently and so we have a good probability of breaking the binary download.
> I suggest to put a note in the readme.txt saying what should be done, since
> everyone using a Juno will have access to the SCP FW in the board.
> 
> What do you think?

Sounds OK. Having everything built automatically is better, but as a
first step, it's definitely OK as long as there are explanations in
readme.txt.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-04-28 19:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 16:35 [Buildroot] [PATCH 1/2] uboot and arm trusted firmware build added to juno board Joao Pinto
2016-04-26 16:35 ` [Buildroot] [PATCH 2/2] ARM Trusted Firmware (ATF) added to boot/ Joao Pinto
2016-04-26 20:18   ` Thomas Petazzoni
2016-04-26 20:05 ` [Buildroot] [PATCH 1/2] uboot and arm trusted firmware build added to juno board Thomas Petazzoni
     [not found]   ` <20160427102152.GL28464@e106497-lin.cambridge.arm.com>
2016-04-27 11:31     ` Thomas Petazzoni
2016-04-26 20:19 ` Thomas Petazzoni
     [not found]   ` <20160427102302.GM28464@e106497-lin.cambridge.arm.com>
2016-04-27 11:31     ` Thomas Petazzoni
2016-04-27 11:44       ` Joao Pinto
2016-04-27 11:57         ` Thomas Petazzoni
     [not found]         ` <20160427120454.GN28464@e106497-lin.cambridge.arm.com>
2016-04-27 12:39           ` Thomas Petazzoni
     [not found]             ` <20160427124632.GO28464@e106497-lin.cambridge.arm.com>
2016-04-27 12:53               ` Thomas Petazzoni
2016-04-27 14:17                 ` Joao Pinto
2016-04-27 14:31                   ` Thomas Petazzoni
     [not found]                     ` <20160427144110.GR28464@e106497-lin.cambridge.arm.com>
2016-04-28 17:21                       ` Joao Pinto
2016-04-28 19:57                         ` Thomas Petazzoni [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=20160428215733.378ce9ac@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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.