From: Sumit Garg <sumit.garg@linaro.org>
To: edk2-devel@lists.01.org
Subject: [PATCH edk2-non-osi v2 1/1] Platform/Socionext: uprev TF-A binary
Date: Tue, 12 Feb 2019 18:48:57 +0530 [thread overview]
Message-ID: <1549977537-29073-1-git-send-email-sumit.garg@linaro.org> (raw)
Update TF-A to upstream v2.0 release + synquacer-spm changes
(Commit: e86e202c2e4e).
Also update OP-TEE to upstream v3.4.0 release (Commit: 406c609bbf08).
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
---
Changes in v2:
Include synquacer-spm patches and some internal workarounds for TF-A.
Following is reference repo to pull this patch:
ssh://git@git.linaro.org/people/sumit.garg/edk2-non-osi.git
Platform/Socionext/DeveloperBox/fip_all_arm_tf.bin | Bin 415251 -> 402960 bytes
1 file changed, 0 insertions(+), 0 deletions(-)
diff --git a/Platform/Socionext/DeveloperBox/fip_all_arm_tf.bin b/Platform/Socionext/DeveloperBox/fip_all_arm_tf.bin
index bc6f4563a5d6..f6f4f5063edf 100644
Binary files a/Platform/Socionext/DeveloperBox/fip_all_arm_tf.bin and b/Platform/Socionext/DeveloperBox/fip_all_arm_tf.bin differ
--
2.7.4
next reply other threads:[~2019-02-12 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 13:18 Sumit Garg [this message]
2019-02-13 12:03 ` [PATCH edk2-non-osi v2 1/1] Platform/Socionext: uprev 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=1549977537-29073-1-git-send-email-sumit.garg@linaro.org \
--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