Buildroot Archive on 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: Wed, 27 Apr 2016 14:39:15 +0200	[thread overview]
Message-ID: <20160427143915.4c66a19d@free-electrons.com> (raw)
In-Reply-To: <20160427120454.GN28464@e106497-lin.cambridge.arm.com>

Hello,

On Wed, 27 Apr 2016 13:04:54 +0100, Liviu.Dudau at arm.com wrote:

> > The SCP firmware is a critical piece for the Juno, but the problem is that it
> > can't be built from any repository I think.
> > @Liviu: Could you please confirm this info?
> 
> That's right, SCP firmware is not available in source form to 3rd parties for now.

Even though that's unfortunate, that's completely OK from a Buildroot
point of view: we already have lots of packages for closed-source
binary blobs (OpenGL implementations, firmwares, etc.).

> > If the SCP firmware exists as a binary only, then we have to include it in
> > /board/arm/juno folder for building the ATF out-of-the-box.
> 
> Thomas, the way ARM Trusted Firmware works (documented in docs/firmware-design.md in
> the ATF repo) requires that a runtime firmware binary for SCP (embedded within fip.bin)
> is loaded at boot time.

OK.

> One option is to copy the original fip.bin from the board, extract
> the bl2.bin from it using fip_create tool (bad name, sorry) and then
> embed it back in the newly created fip.bin. Mind you, fip_create
> actually supports updating an existing fip.bin, it doesn't have to
> create the file from scratch.

That's an option, but it doesn't give a Buildroot output that works
"out of the box" on the target, which is not unacceptable (it can be
explained in the readme.txt that comes with Buildroot for this board)
but a bit sad.

So when you're saying this, are you saying that the binary blob is not
even available publicly for download?

Best regards,

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

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

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=20160427143915.4c66a19d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox