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: Wed, 27 Apr 2016 13:31:49 +0200	[thread overview]
Message-ID: <20160427133149.330a7ea0@free-electrons.com> (raw)
In-Reply-To: <20160427102302.GM28464@e106497-lin.cambridge.arm.com>

Hello,

On Wed, 27 Apr 2016 11:23:02 +0100, Liviu.Dudau at arm.com wrote:

> > On Tue, 26 Apr 2016 17:35:55 +0100, Joao Pinto wrote:
> > 
> > > +    +-- u-boot.bin
> > > +    +-- bl1.bin
> > > +    +-- bl2.bin
> > > +    +-- bl2u.bin
> > > +    +-- bl31.bin
> > > +    +-- fip.bin
> > 
> > Looking at your atfirmware package, I see bl1.bin and fip.bin being
> > copied to output/images, but not bl2.bin, bl2u.bin and bl31.bin. Why
> > are you mentioning them here?
> 
> Those get embedded into the fip.bin. For Juno you need only bl1.bin and
> fip.bin to be transfered to the board.

Right, and they are indeed not copied to $(BINARIES_DIR) by the
atfirmware package. So they shouldn't be mentioned in the readme.txt.

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

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

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=20160427133149.330a7ea0@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.