From: "praneeth" <praneeth@ti.com>
To: Dan Murphy <dmurphy@ti.com>
Cc: <meta-ti@lists.yoctoproject.org>, suman Anna <s-anna@ti.com>
Subject: Re: [master/dunfell PATCH V2] ti-sci-fw: am64x: Update image gen and sysfw to v2020.12
Date: Thu, 7 Jan 2021 17:15:36 -0600 [thread overview]
Message-ID: <30820829-d869-d4cd-36f1-55deb78e7a93@ti.com> (raw)
In-Reply-To: <20210107231438.18812-1-praneeth@ti.com>
On 1/7/21 5:14 PM, praneeth@ti.com wrote:
> From: Praneeth Bajjuri <praneeth@ti.com>
>
> Update the image gen and sysfw commit SHAs so that am64x picks
> v2020.12 version.
>
> Signed-off-by: Praneeth Bajjuri <praneeth@ti.com>
> ---
> v2: update commit message
>
> recipes-bsp/ti-sci-fw/ti-sci-fw.inc | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/recipes-bsp/ti-sci-fw/ti-sci-fw.inc b/recipes-bsp/ti-sci-fw/ti-sci-fw.inc
> index 174d9539..ae22b7a5 100644
> --- a/recipes-bsp/ti-sci-fw/ti-sci-fw.inc
> +++ b/recipes-bsp/ti-sci-fw/ti-sci-fw.inc
> @@ -4,11 +4,11 @@ LICENSE = "TI-TFL"
> LIC_FILES_CHKSUM = "file://LICENSE.ti;md5=b5aebf0668bdf95621259288c4a46d76"
>
> PV = "2020.08b"
> -PV_am64xx-evm-k3r5 = "2020.23"
> +PV_am64xx-evm-k3r5 = "2020.12"
>
> -SRCREV = "078c1bbf3d0a05b4045d4091c32e91ee1ae15ff8"
> +SRCREV = "0c268f292f3b3a71d3bd0b367f492304b45e37b1"
> BRANCH ?= "ti-linux-firmware"
> -SRCREV_imggen = "6d023674b0655f1a7bba192d2600c08be314e9ef"
> +SRCREV_imggen = "a4796e5f1304fe8197cba54ccea3d18b9998ff02"
> SRCREV_FORMAT = "imggen"
>
> SRC_URI = " \
>
next prev parent reply other threads:[~2021-01-07 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 23:14 [master/dunfell PATCH V2] ti-sci-fw: am64x: Update image gen and sysfw to v2020.12 praneeth
2021-01-07 23:15 ` praneeth [this message]
2021-01-07 23:16 ` [meta-ti] " Suman Anna
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-all 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=30820829-d869-d4cd-36f1-55deb78e7a93@ti.com \
--to=praneeth@ti.com \
--cc=dmurphy@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=s-anna@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.