[PATCH 1/2] prusw-fw: Update switch firmwares to 3.2.9 version


Vignesh Raghavendra
 

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"
BRANCH ?= "ti-linux-firmware"

SRC_URI = "git://git.ti.com/processor-firmware/ti-linux-firmware.git;protocol=git;branch=${BRANCH}"
--
2.32.0


praneeth
 

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.


BRANCH ?= "ti-linux-firmware"
SRC_URI = "git://git.ti.com/processor-firmware/ti-linux-firmware.git;protocol=git;branch=${BRANCH}"


Denys Dmytriyenko
 

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


Vignesh Raghavendra
 

On 6/28/21 11:10 PM, 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.
Sounds good to me. Not sure if I can do it for this release though.
Don't want to end up with bunch of broken stuff.

Regards
Vignesh


Denys Dmytriyenko
 

Yogesh,

See our earlier discussion on linux-firmware and the comment about splitting
individual FW binaries into own packages.


On Mon, Jun 28, 2021 at 03:54:11PM -0400, Denys Dmytriyenko wrote:
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 +-
[snip]

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.
--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964