From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 03/11] board: Add Bananapi M64 support
Date: Mon, 4 Dec 2017 16:18:40 +0100 [thread overview]
Message-ID: <20171204161840.4e84f146@windsurf.lan> (raw)
In-Reply-To: <3669564e-b1ff-1ad3-80bd-3d0f021c7735@arm.com>
Hello,
On Mon, 4 Dec 2017 15:03:38 +0000, Andre Przywara wrote:
> > Since ADDITIONAL_VARIABLES resembles to use additional parameters for
> > ATF build, I've treated bl31 as additional variable for this ATF
>
> I have the same feeling as Thomas: bl31 is just a make target (instead
> of "all" and/or "fip"). So it should be treated like this. Using
> ADDITIONAL_VARIABLES sounds like a hack.
See the series I have posted at
http://lists.busybox.net/pipermail/buildroot/2017-December/208788.html
for a proposal that (among other things) supports bl31 as a proper make
target.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-04 15:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 18:05 [Buildroot] [PATCH v5 00/11] board: Add Allwinner A64/H5 boards Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 01/11] arm-trusted-firmware: Build FIP for BL33 Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 02/11] uboot: Add U-Boot-bundles-ATF support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 03/11] board: Add Bananapi M64 support Jagan Teki
[not found] ` <20171103181810202829132@banana-pi.com>
[not found] ` <2017110815285072387665@banana-pi.com>
2017-11-08 7:39 ` [Buildroot] 回复: " Thomas Petazzoni
2017-11-08 7:44 ` Jagan Teki
2017-12-02 14:58 ` [Buildroot] " Thomas Petazzoni
2017-12-02 15:10 ` Jagan Teki
2017-12-04 15:03 ` Andre Przywara
2017-12-04 15:18 ` Thomas Petazzoni [this message]
2017-11-01 18:05 ` [Buildroot] [PATCH v5 04/11] board: Add Pine64 support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 05/11] board: Add SoPine support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 06/11] board: Add FriendlyARM Nanopi A64 support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 07/11] board: Add FriendlyARM Nanopi NEO2 support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 08/11] board: Add Olimex A64-OLinuXino support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 09/11] board: Add Orangepi Win/Win Plus support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 10/11] board: Add Orangepi Prime support Jagan Teki
2017-11-01 18:05 ` [Buildroot] [PATCH v5 11/11] board: Add Orangepi Zero Plus2 support Jagan Teki
2017-11-06 9:39 ` [Buildroot] [PATCH v5 00/11] board: Add Allwinner A64/H5 boards Jagan Teki
2017-11-06 9:48 ` Thomas Petazzoni
2017-11-10 6:06 ` Jagan Teki
2017-11-10 12:33 ` nimaim
2017-11-23 16:27 ` Jagan Teki
2017-11-23 16:32 ` Thomas Petazzoni
2017-12-03 21:51 ` Thomas Petazzoni
2017-12-04 4:43 ` Jagan Teki
2017-12-04 8:04 ` Thomas Petazzoni
2017-12-19 20:48 ` Sergey Matyukevich
2017-12-20 9:05 ` Jagan Teki
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=20171204161840.4e84f146@windsurf.lan \
--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