meta-ti.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Eatmon <reatmon@ti.com>
To: LCPD Automation Script <lcpdbld@list.ti.com>,
	Praneeth Bajjuri <praneeth@ti.com>,
	Denys Dmytriyenko <denys@konsulko.com>,
	<meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti][kirkstone][PATCH 4/4] CI/CD Auto-Merger: cicd.kirkstone.202311271209
Date: Mon, 27 Nov 2023 16:24:52 -0600	[thread overview]
Message-ID: <4e6e0dd5-4428-457c-a210-30451ebfa280@ti.com> (raw)
In-Reply-To: <1701122316-142436-5-git-send-email-lcpdbld@list.ti.com>


There was a bug in our CICD script.  This is the only new patch.  Ignore 
the other tree patches in the series.  They were already applied.


On 11/27/2023 3:58 PM, LCPD Automation Script wrote:
> Updated the value(s) for:
>    ti-linux-fw: CNM_WAVE521_FW_VERSION,PRUETH_FW_AM65X_SR2_VERSION,TI_DM_FW_VERSION,TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION
>    u-boot-ti-staging_2023.04: SRCREV
>    linux-ti-staging-rt_6.1: SRCREV
>    linux-ti-staging_6.1: SRCREV
> 
> Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
> ---
>   meta-ti-bsp/recipes-bsp/ti-linux-fw/ti-linux-fw.inc         | 10 +++++-----
>   meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb |  2 +-
>   meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.1.bb |  2 +-
>   meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb    |  2 +-
>   4 files changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/meta-ti-bsp/recipes-bsp/ti-linux-fw/ti-linux-fw.inc b/meta-ti-bsp/recipes-bsp/ti-linux-fw/ti-linux-fw.inc
> index 65edb73..cee23b1 100644
> --- a/meta-ti-bsp/recipes-bsp/ti-linux-fw/ti-linux-fw.inc
> +++ b/meta-ti-bsp/recipes-bsp/ti-linux-fw/ti-linux-fw.inc
> @@ -9,15 +9,15 @@ INC_PR = "r4"
>   # Firmware versions
>   CORESDK_RTOS_VERSION = "08.02.00.04"
>   PRUETH_FW_AM65X_VERSION = "08.00.00.20"
> -PRUETH_FW_AM65X_SR2_VERSION = "02.02.11.02"
> +PRUETH_FW_AM65X_SR2_VERSION = "02.02.12.08"
>   GOODIX_FW_VERSION = "1.0.0.0"
>   CADENCE_MHDP_FW_VERSION = "2.1.0"
>   IMG_DEC_FW_VERSION = "1.0"
> -CNM_WAVE521_FW_VERSION = "1.0.00"
> -TI_DM_FW_VERSION = "08.06.04"
> -TI_SYSFW_VERSION = "08.06.04"
> +CNM_WAVE521_FW_VERSION = "1.0.3"
> +TI_DM_FW_VERSION = "09.01.02"
> +TI_SYSFW_VERSION = "09.01.07"
>   
> -TI_LINUX_FW_SRCREV ?= "a2d8865df39e9021001fcf06e5daaeab81ba608c"
> +TI_LINUX_FW_SRCREV ?= "6dc47e330f11d01493d24e3ffb8ab369c15068eb"
>   SRCREV = "${TI_LINUX_FW_SRCREV}"
>   
>   BRANCH ?= "ti-linux-firmware"
> diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb
> index 4456a17..23dee3e 100644
> --- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb
> +++ b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb
> @@ -6,7 +6,7 @@ PR = "r0"
>   
>   BRANCH = "ti-u-boot-2023.04"
>   
> -SRCREV = "8c121e6e3c7fd7be6e727ddd41880c202fb6e223"
> +SRCREV = "71b8c840ca61a4e11b2cdf63b0e6580ecb427912"
>   
>   do_install:append:am62xx() {
>   	install -d ${D}/boot
> diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.1.bb b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.1.bb
> index 3c82270..7f0df73 100644
> --- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.1.bb
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.1.bb
> @@ -6,7 +6,7 @@ FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}-6.1:"
>   
>   BRANCH = "ti-rt-linux-6.1.y"
>   
> -SRCREV = "2f5db0e70b5e1ea128754128ff87560ff0c7ffbb"
> +SRCREV = "a135c15322cfd7f341bde5de4df28208c1784d59"
>   
>   include ${@ 'recipes-kernel/linux/ti-extras-rt.inc' if d.getVar('TI_EXTRAS') else ''}
>   
> diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb
> index 45a43a9..e1ab980 100644
> --- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb
> @@ -23,7 +23,7 @@ S = "${WORKDIR}/git"
>   
>   BRANCH ?= "ti-linux-6.1.y"
>   
> -SRCREV ?= "3db9a45004a01caba21d64b397814abadcc841b0"
> +SRCREV ?= "5892b80d6b7786cb1a78aba8147c3f844e063119"
>   PV = "6.1.46+git${SRCPV}"
>   
>   # Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild

-- 
Ryan Eatmon                reatmon@ti.com
-----------------------------------------
Texas Instruments, Inc.  -  LCPD  -  MGTS


      reply	other threads:[~2023-11-27 22:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 21:58 [meta-ti][kirkstone][PATCH 0/4] Update to cicd.kirkstone.202311271209 LCPD Automation Script
2023-11-27 21:58 ` [meta-ti][kirkstone][PATCH 1/4] pru-icss_git.bb: update to PSSP v6.3.0 LCPD Automation Script
2023-11-27 21:58 ` [meta-ti][kirkstone][PATCH 2/4] mesa-pvr: use different srcrev for Rogue and SGX GPU platforms LCPD Automation Script
2023-11-27 21:58 ` [meta-ti][kirkstone][PATCH 3/4] ti-extras: Add support for extra kernel/u-boot features for am62pxx LCPD Automation Script
2023-11-27 21:58 ` [meta-ti][kirkstone][PATCH 4/4] CI/CD Auto-Merger: cicd.kirkstone.202311271209 LCPD Automation Script
2023-11-27 22:24   ` Ryan Eatmon [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=4e6e0dd5-4428-457c-a210-30451ebfa280@ti.com \
    --to=reatmon@ti.com \
    --cc=denys@konsulko.com \
    --cc=lcpdbld@list.ti.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=praneeth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).