Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] uboot and arm trusted firmware build added to juno board
Date: Wed, 27 Apr 2016 15:17:34 +0100	[thread overview]
Message-ID: <5720C9FE.9000507@synopsys.com> (raw)
In-Reply-To: <20160427145339.36ff162b@free-electrons.com>

On 4/27/2016 1:53 PM, Thomas Petazzoni wrote:
> Hello,
> 
> On Wed, 27 Apr 2016 13:46:33 +0100, Liviu.Dudau at arm.com wrote:
> 
>>> So when you're saying this, are you saying that the binary blob is not
>>> even available publicly for download?
>>
>> It is available for download from Linaro downloads page, look for Juno firmware.
>> However it is bundled inside a fip.bin and that is wrapped in a tarball.
> 
> That is still OK, we can always have a Buildroot package that
> downloads that tarball, extracts it, takes the fip.bin, uses the
> fip_create tool to extract the SCP firmware, install it somewhere, and
> then have the atfirmware package pick it up to create the final fip.bin.

There's a detail. fip_create is built by the atfirmware package. So the package
must be built once, extract the scp, copy somewhere, built it again now with the
SCP_BL2. It is doable, but double build is needed and I don't know how buildroot
deals with this 2xbuild operation.

> 
> Thomas
> 

Joao

  reply	other threads:[~2016-04-27 14:17 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 [this message]
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

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=5720C9FE.9000507@synopsys.com \
    --to=joao.pinto@synopsys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox