From: Sumit Garg <sumit.garg@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [PATCH edk2-non-osi 1/1] Platform/Socionext: update TF-A binary to upstream release
Date: Mon, 11 Feb 2019 14:49:25 +0530 [thread overview]
Message-ID: <CAFA6WYMyuQM7e=H7b+a_1nbe97QTA4dy=2Fz8Uy7H2mXsRNM7A@mail.gmail.com> (raw)
In-Reply-To: <CAKv+Gu9QqTo5J=6-osGaLDJuFNYQqNx5Ys-zgZKGjkaPuY2aow@mail.gmail.com>
On Mon, 11 Feb 2019 at 14:30, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>
> On Mon, 11 Feb 2019 at 05:55, Sumit Garg <sumit.garg@linaro.org> wrote:
> >
> > On Sat, 9 Feb 2019 at 17:18, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> > >
> > > On Tue, 5 Feb 2019 at 09:01, Sumit Garg <sumit.garg@linaro.org> wrote:
> > > >
> > > > Update TF-A to upstream v2.0 release (Commit: dbc8d9496ead). 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>
> > > > ---
> > > >
> > > > 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 -> 402963 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..e6ce62a2a20b 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
> > > >
> > >
> > > Thanks Sumit
> > >
> > > I created a firmware build with this change, could you please double check it?
> > >
> >
> > Thanks Ard for incorporating this updated TF-A image. And yes this
> > updated firmware capsule could work pretty well for me.
> >
>
> Thanks Sumit.
>
> I take it you used fwupdate to install it? Which version did you use?
Yes I used fwupdate to install DeveloperBox.Cap. Following is version info:
Distro version:
Distributor ID: Debian
Description: Debian GNU/Linux 9.5 (stretch)
Release: 9.5
Codename: stretch
fwupdate version:
fwupdate/stretch-backports,now 10-3~bpo9+1 arm64 [installed]
> (We are seeing segfaults with fwupdate 12 on debian unstable)
Is it specific to any particular capsule update (like this one) or in
general when trying to run fwupdate?
-Sumit
next prev parent reply other threads:[~2019-02-11 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 8:01 [PATCH edk2-non-osi 1/1] Platform/Socionext: update TF-A binary to upstream release Sumit Garg
2019-02-09 11:48 ` Ard Biesheuvel
2019-02-11 5:55 ` Sumit Garg
2019-02-11 9:00 ` Ard Biesheuvel
2019-02-11 9:19 ` Sumit Garg [this message]
2019-02-11 9:21 ` 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='CAFA6WYMyuQM7e=H7b+a_1nbe97QTA4dy=2Fz8Uy7H2mXsRNM7A@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