From: Joao Pinto <Joao.Pinto@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] new package: atfirmware
Date: Tue, 10 May 2016 10:00:30 +0100 [thread overview]
Message-ID: <5731A32E.7080200@synopsys.com> (raw)
In-Reply-To: <20160509225510.GA18182@e106497-lin.cambridge.arm.com>
On 5/9/2016 11:55 PM, Liviu.Dudau at arm.com wrote:
> On Mon, May 09, 2016 at 10:27:12AM +0100, Joao Pinto wrote:
>> Hi guys,
>> I will have to give a Juno training soon, and this feature would be great to
>> have in the time. Could you comment of the atfirmware patch? Do you have any
>> improvement suggestions?
>
> It looks good to me but I have no ACK powers in the buildroot world.
>
> I am traveling away from my Juno boards at the moment so I cannot add my Tested-by.
>
> Best regards,
> Liviu
Thanks Liviu!
>
>>
>> Thanks.
>>
>> On 5/3/2016 11:13 AM, Joao Pinto wrote:
>>> This patch adds to buildroot an important package for ARM64 based development
>>> boards: The ARM Trusted Firmware (atfirmware).
>>> It also adds the scpfirmware which is a hidden package to get the System Control
>>> Processor (SCP) binary to be included in the bootloader (fip image), which is
>>> a requirement for ARM Juno's board. With this 2 packages, Juno gets fully
>>> supported in the Buildroot.
>>>
>>> Joao Pinto (2):
>>> new packages: atfirmware and scpfirmware
>>> configs: add u-noot and atfirmware options to juno
>>>
>>> board/arm/juno/readme.txt | 21 ++++++++--
>>> boot/Config.in | 2 +
>>> boot/atfirmware/Config.in | 70 +++++++++++++++++++++++++++++++++
>>> boot/atfirmware/atfirmware.hash | 5 +++
>>> boot/atfirmware/atfirmware.mk | 85 +++++++++++++++++++++++++++++++++++++++++
>>> boot/scpfirmware/Config.in | 23 +++++++++++
>>> boot/scpfirmware/scpfirmware.mk | 18 +++++++++
>>> configs/arm_juno_defconfig | 9 +++++
>>> 8 files changed, 230 insertions(+), 3 deletions(-)
>>> create mode 100644 boot/atfirmware/Config.in
>>> create mode 100644 boot/atfirmware/atfirmware.hash
>>> create mode 100644 boot/atfirmware/atfirmware.mk
>>> create mode 100644 boot/scpfirmware/Config.in
>>> create mode 100644 boot/scpfirmware/scpfirmware.mk
>>>
>>
>
next prev parent reply other threads:[~2016-05-10 9:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 10:49 [Buildroot] [PATCH v2 0/2] new package: atfirmware Joao Pinto
2016-05-09 9:27 ` [Buildroot] [PATCH " Joao Pinto
[not found] ` <20160509225510.GA18182@e106497-lin.cambridge.arm.com>
2016-05-10 9:00 ` Joao Pinto [this message]
2016-05-13 10:20 ` Joao Pinto
2016-05-13 13:08 ` Thomas Petazzoni
2016-06-01 10:49 ` [Buildroot] [PATCH v2 1/2] new packages: atfirmware and scpfirmware Joao Pinto
2016-07-05 15:50 ` [Buildroot] [RESEND][PATCH " Maxime Hadjinlian
2016-06-01 10:49 ` [Buildroot] [PATCH v2 2/2] configs: add u-boot and atfirmware options to juno Joao Pinto
[not found] ` <20160601103734.GB23566@e106497-lin.cambridge.arm.com>
2016-06-01 10:45 ` [Buildroot] [RESEND] [PATCH 2/2] configs: add u-noot " Joao Pinto
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=5731A32E.7080200@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