public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Pete Batard <pete@akeo.ie>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
	Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [edk2-non-osi: PATCH 1/1] Platform/RaspberryPi/RPi3: Update ATF binaries to v2.1
Date: Mon, 10 Jun 2019 16:59:26 +0200	[thread overview]
Message-ID: <CAKv+Gu8gK6ynOzJiOXu_q6h7HLQch-0yiTqzuwtmW1j=Z6bwkA@mail.gmail.com> (raw)
In-Reply-To: <20190610124504.6536-2-pete@akeo.ie>

On Mon, 10 Jun 2019 at 14:45, Pete Batard <pete@akeo.ie> wrote:
>
> This patch updates the ARM Trusted Firmware to the latest release
> using AppVeyor built binaries that provide verifiable evidence that
> the files have not been altered from a vanilla source compilation.
>
> Signed-off-by: Pete Batard <pete@akeo.ie>

Thanks Pete

Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>

Pushed as 596043ffb61d..eb114ec4db68

> ---
>  Platform/RaspberryPi/RPi3/TrustedFirmware/License.txt |   2 +-
>  Platform/RaspberryPi/RPi3/TrustedFirmware/Readme.md   |  18 +++++++++++-------
>  Platform/RaspberryPi/RPi3/TrustedFirmware/bl1.bin     | Bin 18801 -> 18776 bytes
>  Platform/RaspberryPi/RPi3/TrustedFirmware/fip.bin     | Bin 41714 -> 45792 bytes
>  4 files changed, 12 insertions(+), 8 deletions(-)
>
> diff --git a/Platform/RaspberryPi/RPi3/TrustedFirmware/License.txt b/Platform/RaspberryPi/RPi3/TrustedFirmware/License.txt
> index b98dc643227e..48429979fec2 100644
> --- a/Platform/RaspberryPi/RPi3/TrustedFirmware/License.txt
> +++ b/Platform/RaspberryPi/RPi3/TrustedFirmware/License.txt
> @@ -1,4 +1,4 @@
> -Copyright (c) 2013-2018, ARM Limited and Contributors. All rights reserved.
> +Copyright (c) 2013-2019, ARM Limited and Contributors. All rights reserved.
>
>  Redistribution and use in source and binary forms, with or without modification,
>  are permitted provided that the following conditions are met:
> diff --git a/Platform/RaspberryPi/RPi3/TrustedFirmware/Readme.md b/Platform/RaspberryPi/RPi3/TrustedFirmware/Readme.md
> index 74bcec7d1f12..f0c4fcf414be 100644
> --- a/Platform/RaspberryPi/RPi3/TrustedFirmware/Readme.md
> +++ b/Platform/RaspberryPi/RPi3/TrustedFirmware/Readme.md
> @@ -1,17 +1,21 @@
>  ARM Trusted Firmware for Raspberry Pi 3
>  =======================================
>
> -The `bl1` and `fip` ATF binaries, found in this directory, were built from
> -the [official ATF source](https://github.com/ARM-software/arm-trusted-firmware)
> -(commit c3859557) using Linaro's GCC 5.5 compiler with:
> +The `bl1.bin` and `fip.bin` ATF binaries found in this directory were built from the
> +[official ATF 2.1 release](https://github.com/ARM-software/arm-trusted-firmware/releases/tag/v2.1)
> +through an [AppVeyor build script](https://github.com/pbatard/pitf/blob/master/appveyor.yml)
> +that is designed to provide evidence that these binaries match the vanilla ATF source.
>
> +As per the [AppVeyor build log](https://ci.appveyor.com/project/pbatard/pitf/builds/24506898),
> +the SHA-256 sums for the blobs can be validated to be as follows:
> +- `bl1.bin`: `57e30ed8572e6a3a161c231e68138ee2c78e9dfc6dc51be8c0b4d9c3fe9bbfad`
> +- `fip.bin`: `b7eadad3a11088e322c52ab5fd2247a7bc79dc086a21db12cc8079a2ab4789f6`
> +
> +For Raspberry Pi 3 usage, ATF was built using the command:
>  ```
> -export CROSS_COMPILE=/usr/src/gcc-linaro-5.5.0-2017.10-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-
>  make PLAT=rpi3 PRELOADED_BL33_BASE=0x30000 RPI3_PRELOADED_DTB_BASE=0x10000 SUPPORT_VFP=1 RPI3_USE_UEFI_MAP=1 fip all
>  ```
> -
> -This results in the following memory mapping:
> -
> +which results in the following memory mapping:
>  ```
>      0x00000000 +-----------------+
>                 |       ROM       | BL1

      reply	other threads:[~2019-06-10 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10 12:45 [edk2-non-osi: PATCH 0/1] Platform/RaspberryPi/RPi3: Update ATF Pete Batard
2019-06-10 12:45 ` [edk2-non-osi: PATCH 1/1] Platform/RaspberryPi/RPi3: Update ATF binaries to v2.1 Pete Batard
2019-06-10 14:59   ` Ard Biesheuvel [this message]

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-list 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='CAKv+Gu8gK6ynOzJiOXu_q6h7HLQch-0yiTqzuwtmW1j=Z6bwkA@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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