public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Pete Batard" <pete@akeo.ie>
To: devel@edk2.groups.io
Cc: ard.biesheuvel@arm.com, leif@nuviainc.com, awarkentin@vmware.com
Subject: [edk2-platforms][PATCH 1/2] Platform/RPi4: Update DSC to reflect switch to single TF-A binary
Date: Tue, 21 Apr 2020 12:30:14 +0100	[thread overview]
Message-ID: <20200421113015.13936-1-pete@akeo.ie> (raw)

Note: This commit depends on an "Update TF-A binaries to v2.3" patch
having been applied to edk2-non-osi.

With the update of non-osi TF-A binaries to latest, we can switch to
using the single bl31.bin instead of the now removed bl31_pl011.bin.

Signed-off-by: Pete Batard <pete@akeo.ie>
---
 Platform/RaspberryPi/RPi4/RPi4.dsc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Platform/RaspberryPi/RPi4/RPi4.dsc b/Platform/RaspberryPi/RPi4/RPi4.dsc
index de32aab2df3c..c401533a4abc 100644
--- a/Platform/RaspberryPi/RPi4/RPi4.dsc
+++ b/Platform/RaspberryPi/RPi4/RPi4.dsc
@@ -37,7 +37,7 @@ [Defines]
   #
   # Default TF-A binary checked into edk2-non-osi.
   #
-  DEFINE TFA_BUILD_BL31 = Platform/RaspberryPi/$(PLATFORM_NAME)/TrustedFirmware/bl31_pl011.bin
+  DEFINE TFA_BUILD_BL31 = Platform/RaspberryPi/$(PLATFORM_NAME)/TrustedFirmware/bl31.bin
 !else
   #
   # Usually we use the checked-in binaries, but for developers working
-- 
2.21.0.windows.1


             reply	other threads:[~2020-04-21 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 11:30 Pete Batard [this message]
2020-04-21 11:30 ` [edk2-platforms][PATCH 2/2] Platform/RPi: Fix Readme issues Pete Batard
2020-04-21 13:04 ` [edk2-platforms][PATCH 1/2] Platform/RPi4: Update DSC to reflect switch to single TF-A binary Ard Biesheuvel

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=20200421113015.13936-1-pete@akeo.ie \
    --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