public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif@nuviainc.com>
To: Graeme Gregory <graeme@nuviainc.com>
Cc: devel@edk2.groups.io
Subject: Re: [PATCH edk2-non-osi 1/1] Platform/Qemu/Sbsa: Update ARM-TF binaries with EC and topology
Date: Tue, 15 Sep 2020 16:13:09 +0100	[thread overview]
Message-ID: <20200915151309.GN5623@vanye> (raw)
In-Reply-To: <20200915141027.24767-1-graeme@nuviainc.com>

On Tue, Sep 15, 2020 at 15:10:27 +0100, Graeme Gregory wrote:
> Based on arm-tf commit 1aabb74fae0e30901884b6cb230d7ea730a74344
> 
> With https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/5478
> applied to support CPU topology used by sbsa-ref machine.
> 
> With https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/5479
> applied to support the EC device in sbsa-ref machine so reboot/shutdown
> function as expected.
> 
> Signed-off-by: Graeme Gregory <graeme@nuviainc.com>

Reviewed-by: Leif Lindholm <leif@nuviainc.com>
Pushed as ff6750947db3.

Thanks!

> ---
> 
> Patch available for cherrypick
> https://github.com/xXorAa/edk2-non-osi/tree/qemu-sbsa-update-ec-topology-v1
> 
>  Platform/Qemu/Sbsa/bl1.bin | Bin 19301 -> 19301 bytes
>  Platform/Qemu/Sbsa/fip.bin | Bin 53973 -> 54002 bytes
>  2 files changed, 0 insertions(+), 0 deletions(-)
> 
> diff --git a/Platform/Qemu/Sbsa/bl1.bin b/Platform/Qemu/Sbsa/bl1.bin
> index bd0b2de1dfcb..794f5b68bd13 100755
> Binary files a/Platform/Qemu/Sbsa/bl1.bin and b/Platform/Qemu/Sbsa/bl1.bin differ
> diff --git a/Platform/Qemu/Sbsa/fip.bin b/Platform/Qemu/Sbsa/fip.bin
> index 03b327bcd022..a12cfa5ba2c9 100644
> Binary files a/Platform/Qemu/Sbsa/fip.bin and b/Platform/Qemu/Sbsa/fip.bin differ
> -- 
> 2.25.1
> 

      reply	other threads:[~2020-09-15 15:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-15 14:10 [PATCH edk2-non-osi 1/1] Platform/Qemu/Sbsa: Update ARM-TF binaries with EC and topology Graeme Gregory
2020-09-15 15:13 ` Leif Lindholm [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=20200915151309.GN5623@vanye \
    --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