From: "Denys Dmytriyenko" <denis@denix.org>
To: "Bajjuri, Praneeth" <praneeth@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Yogesh Siraswar <yogeshs@ti.com>,
meta-ti@lists.yoctoproject.org, Lokesh Vutla <lokeshvutla@ti.com>,
Grygorii Strashko <grygorii.strashko@ti.com>
Subject: Re: [PATCH 1/2] prusw-fw: Update switch firmwares to 3.2.9 version
Date: Mon, 28 Jun 2021 15:54:11 -0400 [thread overview]
Message-ID: <20210628195411.GW1528@denix.org> (raw)
In-Reply-To: <5df72a60-9793-04b2-bae9-5164b510ee02@ti.com>
On Mon, Jun 28, 2021 at 12:40:22PM -0500, Bajjuri, Praneeth wrote:
> Yogesh,Vignesh,
>
> On 6/28/2021 9:48 AM, Vignesh Raghavendra wrote:
> >From: Lokesh Vutla <lokeshvutla@ti.com>
> >
> >Update prueth switch firmwares to 3.2.9 version
> >
> >Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
> >---
> > recipes-bsp/prusw-fw/{prusw-fw_3.2.7.bb => prusw-fw_3.2.9.bb} | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> > rename recipes-bsp/prusw-fw/{prusw-fw_3.2.7.bb => prusw-fw_3.2.9.bb} (94%)
> >
> >diff --git a/recipes-bsp/prusw-fw/prusw-fw_3.2.7.bb b/recipes-bsp/prusw-fw/prusw-fw_3.2.9.bb
> >similarity index 94%
> >rename from recipes-bsp/prusw-fw/prusw-fw_3.2.7.bb
> >rename to recipes-bsp/prusw-fw/prusw-fw_3.2.9.bb
> >index 17de58c2..3f5ef7e7 100644
> >--- a/recipes-bsp/prusw-fw/prusw-fw_3.2.7.bb
> >+++ b/recipes-bsp/prusw-fw/prusw-fw_3.2.9.bb
> >@@ -11,7 +11,7 @@ COMPATIBLE_MACHINE = "ti33x|ti43x|am57xx-evm|am57xx-hs-evm"
> > PACKAGE_ARCH = "${MACHINE_ARCH}"
> >-SRCREV = "0038ff0ecda8dae83c65d454c85776c6a4ef8e63"
> >+SRCREV = "dccfb2328354be2933a5a179b528ec8a18b92d3a"
>
> Can we have once central recipe for ti-linux-firmware to pick the
> right SRCREV when firmware is integrated
> recipe-bsp/ti-linux-fw*/*.bb something like that, Instead of
> pointing to a different SRCREV in different bb recipe ?
>
> I see 9 different recipe-bsp/<>/ locations potentially pointing to
> different SRCREV.
Individual FW recipes in meta-ti evolved over long time, being added one by
one, as they were coming from different places and not necessarily hosted in
a single repo in the beginning...
Has anyone looked at upstreaming those FW images to main linux-firmware at
kernel.org?
There's a recipe for the upstream linux-firmware bundle in oe-core that
resides in recipes-kernel/linux-firmware/.
Until fully upstreamed, it might be possible to bbappend that recipe from
oe-core in meta-ti. But it tries to split up as much of individual FW images
as possible. That way one recipe with a single SRCREV produces multiple binary
packages that can be pulled into the image individually.
> > BRANCH ?= "ti-linux-firmware"
> > SRC_URI = "git://git.ti.com/processor-firmware/ti-linux-firmware.git;protocol=git;branch=${BRANCH}"
> >
>
--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964
next prev parent reply other threads:[~2021-06-28 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 14:48 [PATCH 1/2] prusw-fw: Update switch firmwares to 3.2.9 version Vignesh Raghavendra
2021-06-28 14:48 ` [PATCH 2/2] prueth-fw: Update prueth dual emac firmware to 5.6.15 Vignesh Raghavendra
2021-06-28 17:40 ` [PATCH 1/2] prusw-fw: Update switch firmwares to 3.2.9 version praneeth
2021-06-28 19:54 ` Denys Dmytriyenko [this message]
2021-06-29 6:11 ` Vignesh Raghavendra
[not found] ` <168CD716D1640986.22485@lists.yoctoproject.org>
2021-08-12 21:09 ` [meta-ti] " Denys Dmytriyenko
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=20210628195411.GW1528@denix.org \
--to=denis@denix.org \
--cc=grygorii.strashko@ti.com \
--cc=lokeshvutla@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=vigneshr@ti.com \
--cc=yogeshs@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.