From: "Denys Dmytriyenko" <denys@ti.com>
To: Dan Murphy <dmurphy@ti.com>
Cc: <meta-ti@lists.yoctoproject.org>
Subject: Re: [PATCH] prusw-fw: Update the firmware to 3.1.6 version
Date: Fri, 16 Oct 2020 15:41:18 -0400 [thread overview]
Message-ID: <20201016194118.GU14852@beryl> (raw)
In-Reply-To: <20201015115548.21626-1-dmurphy@ti.com>
On Thu, Oct 15, 2020 at 06:55:48AM -0500, Dan Murphy wrote:
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> ---
> recipes-bsp/prusw-fw/{prusw-fw_3.1.4.bb => prusw-fw_3.1.6.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename recipes-bsp/prusw-fw/{prusw-fw_3.1.4.bb => prusw-fw_3.1.6.bb} (93%)
>
> diff --git a/recipes-bsp/prusw-fw/prusw-fw_3.1.4.bb b/recipes-bsp/prusw-fw/prusw-fw_3.1.6.bb
> similarity index 93%
> rename from recipes-bsp/prusw-fw/prusw-fw_3.1.4.bb
> rename to recipes-bsp/prusw-fw/prusw-fw_3.1.6.bb
> index b8897e4bb25b..684e77460021 100644
> --- a/recipes-bsp/prusw-fw/prusw-fw_3.1.4.bb
> +++ b/recipes-bsp/prusw-fw/prusw-fw_3.1.6.bb
> @@ -3,7 +3,7 @@ SUMMARY = "PRU Switch firmware for AM57xx, AM437x and AM335x"
> LICENSE = "TI-TFL"
> LIC_FILES_CHKSUM = "file://LICENSE.ti;md5=b5aebf0668bdf95621259288c4a46d76"
>
> -PR = "r0"
> +PR = "r1"
This is not strictly needed - you are already bumping PV from 3.1.4 to 3.1.6
> CLEANBROKEN = "1"
>
> @@ -11,7 +11,7 @@ COMPATIBLE_MACHINE = "ti33x|ti43x|am57xx-evm|am57xx-hs-evm"
>
> PACKAGE_ARCH = "${MACHINE_ARCH}"
>
> -SRCREV = "b19bf13a16d7f5c1260cf4d48cf967e5c7e15128"
> +SRCREV = "f95d048c0a007a5acac706edea4a3ffbfa8ca933"
> BRANCH ?= "ti-linux-firmware"
>
> SRC_URI = "git://git.ti.com/processor-firmware/ti-linux-firmware.git;protocol=git;branch=${BRANCH}"
> --
> 2.28.0.585.ge1cfff676549
>
prev parent reply other threads:[~2020-10-16 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 11:55 [PATCH] prusw-fw: Update the firmware to 3.1.6 version Dan Murphy
2020-10-16 19:41 ` Denys Dmytriyenko [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-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=20201016194118.GU14852@beryl \
--to=denys@ti.com \
--cc=dmurphy@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
/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.