Re: [meta-ti] [kirkstone][PATCH v3 1/2] preuth-fw: Remove packaging of PRU-ICSSM firmwares
On 10/10/23 3:03 AM, Andrew Davis wrote:
> On 10/9/23 4:25 PM, Ryan Eatmon wrote:
>>
>>
>> On 10/9/2023 3:20 PM, Denys Dmytriyenko wrote:
>>> On Mon, Oct 09, 2023 at 12:39:25PM +0530, Ravi Gunasekaran via
>>> lists.yoctoproject.org wrote:
PRU-ICSS on AM33x, AM43x, supports different ethernet modes such
as Ethernet, HSR and PRP by means of different firmwares and the
driver loads one of the these firmware. The PRU-ICSS linux driver
may not be available for all kernel versions.
So add an .inc file that avoids the packaging of such firmwares
in the SDK, so that it can be referenced by kernel recipes that
don't support PRU-ICSS.
Signed-off-by: Ravi Gunasekaran
---
meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc | 3 +++
1 file changed, 3 insertions(+)
create mode 100644 meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
diff --git a/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
b/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
new file mode 100644
index ..6698c9ed
--- /dev/null
+++ b/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
@@ -0,0 +1,3 @@
+# Do not package firmwares for kernels that don't support PRUETH
+RDEPENDS:${KERNEL_PACKAGE_NAME}-base:remove:ti43x = " prueth-fw pruhsr-fw
pruprp-fw"
+RDEPENDS:${KERNEL_PACKAGE_NAME}-base:remove:ti33x = " prueth-fw pruhsr-fw
pruprp-fw"
>>>
>>> This is asking for trouble - there's no way to un-do :remove downstream
>>> (e.g.
>>> any of the Distro, SDK, Product Line or Customer layers)
>>>
>>> It is not recommended to use :remove (and :append to a lesser degree) on a
>>> regular basis when it can be done differently.
>>>
>>> Moreover, what is a difference from v2? It is a more convoluted way to drop
>>> those FW images from getting installed, but it is still done unconditionally
>>> here in meta-ti - are there any benefits of doing it this way?
>>
>> From my understanding... This firmware was supported under 5.10. It is
>> not being supported for 6.1 but will be supported next year some time.
>>
>> So I was trying to communicate via the recipes that overall it is supported,
>> but for this blip it is removed.
>>
>> Either way we are adding some odd conditionals to support the logic. Two
>> choices:
>>
>> 1) Enabled by default, disable in the kernels were it is not supported.
>> 2) Disabled by default, enable in 5.10 and in the future.
>>
>
> 3) Install firmware unconditionally
>
> linux-firmware has plenty of firmware shipped that different version of the
> kernel can/cannot use. Why is this one little firmware so important to *not*
> ship right now?
>
The concern was raised by the Customer Apps team as the feature is not
supported. And the
presence of the firmwares may give an impression to the customer that feature
is supported.
> Andrew
>
>> Thoughts?
>>
>>
--
Regards,
Ravi
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17089):
https://lists.yoctoproject.org/g/meta-ti/message/17089
Mute This Topic: https://lists.yoctoproject.org/mt/101847815/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[meta-ti][master/kirkstone][PATCH] u-boot-ti: Correctly fix SPL binary name for SD/MMC media on HS boards
The previous patch is incorrectly accepted and released. This patch
applies the logic that was discussed on the mailing list.
- Create a new variable grouping for SPL_HS_MLO
- Update the install/deploy code to reference the new variables.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 33 ++--
1 file changed, 30 insertions(+), 3 deletions(-)
diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
index 355e9868..58ee6525 100644
--- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
+++ b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
@@ -81,15 +81,19 @@ SPL_UART_BINARY:k3r5 = ""
SPL_UART_IMAGE ?= "${SPL_UART_BINARY}-${MACHINE}-${PV}-${PR}"
SPL_UART_SYMLINK ?= "${SPL_UART_BINARY}-${MACHINE}"
+SPL_HS_MLO_BINARY = "u-boot-spl_HS_MLO"
+SPL_HS_MLO_IMAGE = "u-boot-spl_HS_MLO-${MACHINE}-${PV}-${PR}"
+SPL_HS_MLO_SYMLINK = "u-boot-spl_HS_MLO-${MACHINE}"
+
# HS XLD
UBOOT_HS_XLD_BINARY = "u-boot-spl_HS_X-LOADER"
UBOOT_HS_XLD_IMAGE = "u-boot-spl_HS_X-LOADER-${MACHINE}-${PV}-${PR}"
UBOOT_HS_XLD_SYMLINK = "u-boot-spl_HS_X-LOADER-${MACHINE}"
# HS MLO
-UBOOT_HS_MLO_BINARY = "u-boot-spl_HS_MLO"
-UBOOT_HS_MLO_IMAGE = "u-boot-spl_HS_MLO-${MACHINE}-${PV}-${PR}"
-UBOOT_HS_MLO_SYMLINK = "u-boot-spl_HS_MLO-${MACHINE}"
+UBOOT_HS_MLO_BINARY = "u-boot_HS_MLO"
+UBOOT_HS_MLO_IMAGE = "u-boot_HS_MLO-${MACHINE}-${PV}-${PR}"
+UBOOT_HS_MLO_SYMLINK = "u-boot_HS_MLO-${MACHINE}"
# HS ISSW
UBOOT_HS_ISSW_BINARY = "u-boot-spl_HS_ISSW"
@@ -121,6 +125,11 @@ do_install:append () {
ln -sf
${SPL_UART_IMAGE}-${type} ${D}/boot/${SPL_UART_BINARY}-${type}
ln -sf
${SPL_UART_IMAGE}-${type} ${D}/boot/${SPL_UART_BINARY}
fi
+ if [ -f
${B}/${config}/${SPL_HS_MLO_BINARY} ]; then
+ install
${B}/${config}/${SPL_HS_MLO_BINARY} ${D}/boot/${SPL_HS_MLO_IMAGE}-${type}
+ ln -sf
${SPL_HS_MLO_IMAGE}-${type} ${D}/boot/${SPL_HS_MLO_BINARY}-${type}
+ ln -sf
${SPL_HS_MLO_IMAGE}-${type} ${D}/boot/${SPL_HS_MLO_BINARY}
+ fi
if [ -f
${B}/${config}/${UBOOT_HS_XLD_BINARY} ]; then
install
${B}/${config}/${UBOOT_HS_XLD_BINARY} ${D}/boot/${UBOOT_HS_XLD_IMAGE}-${type}
ln -sf
${UBOOT_HS_XLD_IMAGE}-${type} ${D}/boot/${UBOOT_HS_XLD_BINARY}-${type}
@@ -151,6 +160,10 @@ do_install:append () {
install ${B}/spl/${SPL_UART_BINARY}
${D}/boot/${SPL_UART_IMAGE}
ln -sf ${SPL_UART_IMAGE} ${D}/boot/${SPL_UART_BINARY}
fi
+ if [ -f ${B}/${SPL_HS_MLO_BINARY} ]; then
+ install ${B}/${SPL_HS_MLO_BINARY}
${D}/boot/${SPL_HS_MLO_IMAGE}
+ ln -sf ${SPL_HS_MLO_IMAGE}
${D}/boot/${SPL_HS_MLO_BINARY}
+ fi
if [ -f ${B}/${UBOOT_HS_XLD_BINARY} ]; then
install ${B}/${UBOOT_HS_XLD_BINARY}
${D}/boot/${UBOOT_HS_XLD_IMAGE}
ln -sf ${UBOOT_HS_XLD_IMAGE}
${D}/boot/${UBOOT_HS_XLD_BINARY}
@@ -202,6 +215,14 @@ do_deploy:append () {
ln -sf
${SPL_UART_IMAGE}-${type} ${SPL_UART_SYMLINK}-${type}
ln -sf
${SPL_UART_IMAGE}-${type} ${SPL_UART_SYMLINK}
fi
+ if [ -f
${B}/${config}/${SPL_HS_MLO_BINARY} ]; then
+ install
${B}/${config}/${SPL_HS_MLO_BINARY} ${SPL_HS_MLO_IMAGE}-${type}
+ rm -f ${SPL_HS_MLO_BINARY}
${SPL_HS_MLO_SYMLINK}
+ ln -sf
${SPL_HS_MLO_IMAGE}-${type} ${SPL_HS_MLO_SYMLINK}-${type}
+ ln -sf
${SPL_HS_MLO_IMAGE}-${type} ${SPL_HS_MLO_SYMLINK}
+ ln -sf
${SPL_HS_MLO_IMAGE}-${type} ${SPL_HS_MLO_BINARY}-${type}
+ ln -sf
${SPL_HS_MLO_IMAGE}-${type} ${SPL_HS_MLO_BINARY}
+ fi
if [ -f
${B}/${config}/${UBOOT_HS_XLD_BINARY} ]; then
install
${B}/${config}/${UBOOT_HS_XLD_BINARY} ${UBOOT_HS_XLD_IMAGE}-${type}
rm -f ${UBOOT_HS_XLD_BINARY}
${UBOOT_HS_XLD_SYMLINK}
@@ -247,6 +268,12 @@ do_deploy:append () {
ln -sf ${SPL_UART_IMAGE} ${SPL_UART_BINARY}
ln -sf
Re: [meta-ti] [kirkstone][PATCH v3 1/2] preuth-fw: Remove packaging of PRU-ICSSM firmwares
On 10/9/23 4:25 PM, Ryan Eatmon wrote:
On 10/9/2023 3:20 PM, Denys Dmytriyenko wrote:
On Mon, Oct 09, 2023 at 12:39:25PM +0530, Ravi Gunasekaran via
lists.yoctoproject.org wrote:
PRU-ICSS on AM33x, AM43x, supports different ethernet modes such
as Ethernet, HSR and PRP by means of different firmwares and the
driver loads one of the these firmware. The PRU-ICSS linux driver
may not be available for all kernel versions.
So add an .inc file that avoids the packaging of such firmwares
in the SDK, so that it can be referenced by kernel recipes that
don't support PRU-ICSS.
Signed-off-by: Ravi Gunasekaran
---
meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc | 3 +++
1 file changed, 3 insertions(+)
create mode 100644 meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
diff --git a/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
b/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
new file mode 100644
index ..6698c9ed
--- /dev/null
+++ b/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
@@ -0,0 +1,3 @@
+# Do not package firmwares for kernels that don't support PRUETH
+RDEPENDS:${KERNEL_PACKAGE_NAME}-base:remove:ti43x = " prueth-fw pruhsr-fw
pruprp-fw"
+RDEPENDS:${KERNEL_PACKAGE_NAME}-base:remove:ti33x = " prueth-fw pruhsr-fw
pruprp-fw"
This is asking for trouble - there's no way to un-do :remove downstream (e.g.
any of the Distro, SDK, Product Line or Customer layers)
It is not recommended to use :remove (and :append to a lesser degree) on a
regular basis when it can be done differently.
Moreover, what is a difference from v2? It is a more convoluted way to drop
those FW images from getting installed, but it is still done unconditionally
here in meta-ti - are there any benefits of doing it this way?
From my understanding... This firmware was supported under 5.10. It is not
being supported for 6.1 but will be supported next year some time.
So I was trying to communicate via the recipes that overall it is supported,
but for this blip it is removed.
Either way we are adding some odd conditionals to support the logic. Two
choices:
1) Enabled by default, disable in the kernels were it is not supported.
2) Disabled by default, enable in 5.10 and in the future.
3) Install firmware unconditionally
linux-firmware has plenty of firmware shipped that different version of the
kernel can/cannot use. Why is this one little firmware so important to *not*
ship right now?
Andrew
Thoughts?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17087):
https://lists.yoctoproject.org/g/meta-ti/message/17087
Mute This Topic: https://lists.yoctoproject.org/mt/101847815/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [meta-ti] [kirkstone][PATCH v3 1/2] preuth-fw: Remove packaging of PRU-ICSSM firmwares
On 10/9/2023 3:20 PM, Denys Dmytriyenko wrote:
On Mon, Oct 09, 2023 at 12:39:25PM +0530, Ravi Gunasekaran via
lists.yoctoproject.org wrote:
PRU-ICSS on AM33x, AM43x, supports different ethernet modes such
as Ethernet, HSR and PRP by means of different firmwares and the
driver loads one of the these firmware. The PRU-ICSS linux driver
may not be available for all kernel versions.
So add an .inc file that avoids the packaging of such firmwares
in the SDK, so that it can be referenced by kernel recipes that
don't support PRU-ICSS.
Signed-off-by: Ravi Gunasekaran
---
meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc | 3 +++
1 file changed, 3 insertions(+)
create mode 100644 meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
diff --git a/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
b/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
new file mode 100644
index ..6698c9ed
--- /dev/null
+++ b/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
@@ -0,0 +1,3 @@
+# Do not package firmwares for kernels that don't support PRUETH
+RDEPENDS:${KERNEL_PACKAGE_NAME}-base:remove:ti43x = " prueth-fw pruhsr-fw
pruprp-fw"
+RDEPENDS:${KERNEL_PACKAGE_NAME}-base:remove:ti33x = " prueth-fw pruhsr-fw
pruprp-fw"
This is asking for trouble - there's no way to un-do :remove downstream (e.g.
any of the Distro, SDK, Product Line or Customer layers)
It is not recommended to use :remove (and :append to a lesser degree) on a
regular basis when it can be done differently.
Moreover, what is a difference from v2? It is a more convoluted way to drop
those FW images from getting installed, but it is still done unconditionally
here in meta-ti - are there any benefits of doing it this way?
From my understanding... This firmware was supported under 5.10. It
is not being supported for 6.1 but will be supported next year some time.
So I was trying to communicate via the recipes that overall it is
supported, but for this blip it is removed.
Either way we are adding some odd conditionals to support the logic.
Two choices:
1) Enabled by default, disable in the kernels were it is not supported.
2) Disabled by default, enable in 5.10 and in the future.
Thoughts?
--
Ryan Eatmonreat...@ti.com
-
Texas Instruments, Inc. - LCPD - MGTS
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17086):
https://lists.yoctoproject.org/g/meta-ti/message/17086
Mute This Topic: https://lists.yoctoproject.org/mt/101847815/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe:
https://lists.yoctoproject.org/g/meta-ti/leave/6695321/21656/1393940836/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [meta-ti] [master/kirkstone] u-boot-ti: Fix SPL binary name for SD/MMC media on HS boards
On 10/9/2023 2:58 PM, Denys Dmytriyenko wrote:
On Mon, Oct 02, 2023 at 11:44:42AM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
On 10/2/2023 10:30 AM, Andrew Davis via lists.yoctoproject.org wrote:
On 10/2/23 9:06 AM, Julien Panis wrote:
On 9/29/23 14:25, Julien Panis wrote:
The SPL binary built by u-boot for SD/MMC/eMMC media on HS platforms is
u-boot-spl_HS_MLO. Thanks to this fix, the binary is properly installed
and deployed.
Signed-off-by: Julien Panis
---
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
index d9a3a520e857..9ca0fb44d127 100644
--- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
+++ b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
@@ -100,9 +100,9 @@ UBOOT_HS_XLD_IMAGE =
"u-boot-spl_HS_X-LOADER-${MACHINE}-${PV}-${PR}"
UBOOT_HS_XLD_SYMLINK = "u-boot-spl_HS_X-LOADER-${MACHINE}"
# HS MLO
-UBOOT_HS_MLO_BINARY = "u-boot_HS_MLO"
-UBOOT_HS_MLO_IMAGE = "u-boot_HS_MLO-${MACHINE}-${PV}-${PR}"
-UBOOT_HS_MLO_SYMLINK = "u-boot_HS_MLO-${MACHINE}"
+UBOOT_HS_MLO_BINARY = "u-boot-spl_HS_MLO"
+UBOOT_HS_MLO_IMAGE = "u-boot-spl_HS_MLO-${MACHINE}-${PV}-${PR}"
+UBOOT_HS_MLO_SYMLINK = "u-boot-spl_HS_MLO-${MACHINE}"
# HS ISSW
UBOOT_HS_ISSW_BINARY = "u-boot-spl_HS_ISSW"
I'm not sure that this patch should be applied actually.
In doc/README.ti-secure, u-boot_HS_MLO is mentioned for
Keystone2 Secure Devices.
So, maybe this name was used intentionally...(?)
On Keystone2 HS, we do not use SPL, so the ROM loaded image (MLO) is the
normal U-Boot image, we name it u-boot_HS_MLO. For others that do use SPL
the ROM image is the SPL, and it is called u-boot-spl_HS_MLO.
So this patch has the right idea, just we should add another deployed image
var in addition to this one, not replace it, maybe:
SPL_HS_MLO_BINARY = "u-boot-spl_HS_MLO"
...
And add the appropriate install code later in the file as well.
Was this supposed to be changed from UBOOT_HS_MLO_* -> SPL_HS_MLO_* per the
discussion above? Or did I miss something and the old patch got merged:
Ooops. I accepted it incorrectly... I'll submit the "correct" patch on
top of this one.
https://git.yoctoproject.org/meta-ti/commit/?id=5306d61211edecf3d04cd9e8c0b64cd4a0ef3549
--
Ryan Eatmonreat...@ti.com
-
Texas Instruments, Inc. - LCPD - MGTS
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17085):
https://lists.yoctoproject.org/g/meta-ti/message/17085
Mute This Topic: https://lists.yoctoproject.org/mt/101656237/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe:
https://lists.yoctoproject.org/g/meta-ti/leave/6695321/21656/1393940836/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [meta-ti] [kirkstone][PATCH v3 1/2] preuth-fw: Remove packaging of PRU-ICSSM firmwares
On Mon, Oct 09, 2023 at 12:39:25PM +0530, Ravi Gunasekaran via
lists.yoctoproject.org wrote:
> PRU-ICSS on AM33x, AM43x, supports different ethernet modes such
> as Ethernet, HSR and PRP by means of different firmwares and the
> driver loads one of the these firmware. The PRU-ICSS linux driver
> may not be available for all kernel versions.
>
> So add an .inc file that avoids the packaging of such firmwares
> in the SDK, so that it can be referenced by kernel recipes that
> don't support PRU-ICSS.
>
> Signed-off-by: Ravi Gunasekaran
> ---
> meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc | 3 +++
> 1 file changed, 3 insertions(+)
> create mode 100644 meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
>
> diff --git a/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
> b/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
> new file mode 100644
> index ..6698c9ed
> --- /dev/null
> +++ b/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
> @@ -0,0 +1,3 @@
> +# Do not package firmwares for kernels that don't support PRUETH
> +RDEPENDS:${KERNEL_PACKAGE_NAME}-base:remove:ti43x = " prueth-fw pruhsr-fw
> pruprp-fw"
> +RDEPENDS:${KERNEL_PACKAGE_NAME}-base:remove:ti33x = " prueth-fw pruhsr-fw
> pruprp-fw"
This is asking for trouble - there's no way to un-do :remove downstream (e.g.
any of the Distro, SDK, Product Line or Customer layers)
It is not recommended to use :remove (and :append to a lesser degree) on a
regular basis when it can be done differently.
Moreover, what is a difference from v2? It is a more convoluted way to drop
those FW images from getting installed, but it is still done unconditionally
here in meta-ti - are there any benefits of doing it this way?
--
Denys
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17084):
https://lists.yoctoproject.org/g/meta-ti/message/17084
Mute This Topic: https://lists.yoctoproject.org/mt/101847815/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe:
https://lists.yoctoproject.org/g/meta-ti/leave/6695321/21656/1393940836/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [meta-ti] [kirkstone][PATCH v3 0/2] Remove PRU Ethernet firmwares for legacy devices
On Mon, Oct 09, 2023 at 12:23:08PM -0500, praneeth via lists.yoctoproject.org wrote: > > > On 10/9/2023 2:09 AM, Ravi Gunasekaran wrote: > >Linux kernel 6.1 does not have support for PRU-ICSSM driver. > >So remove packaging of all the PRU-ICSSM firmwares for kernel 6.1 > >based SDKs. > > > >In the v2 version, it was suggested to have the changes in the SDK layer. > >But after discussion with meta-ti(Ryan) and meta-processor-sdk(Gyan) > >maintainers, it was decided to introduce a new .inc file that removes the > >packaging of the firmware and include it in the kernel recipes that don't > >have support for PRU-ICSSM in meta-ti. This series attempts to take that > >approach. > > > >The support for PRU-ICSSM driver will be available in mainline and TI kernel > >towards the end of 2024. So until such time, this approach will be followed. > > > >v2:https://serenity.dal.design.ti.com/patchwork/project/meta-ti/patch/20230908113836.12413-1-r-gunaseka...@ti.com/ > >v1:https://serenity.dal.design.ti.com/patchwork/project/meta-ti/patch/20230908114439.13213-1-r-gunaseka...@ti.com/ > > For future reference, please do not post internal links. > Instead, use https://lists.yoctoproject.org/g/meta-ti/messages Or public Patchwork: https://patchwork.yoctoproject.org/project/ti/patch/20230908114439.13213-1-r-gunaseka...@ti.com/ -- Denys -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17083): https://lists.yoctoproject.org/g/meta-ti/message/17083 Mute This Topic: https://lists.yoctoproject.org/mt/101847814/21656 Group Owner: meta-ti+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/leave/6695321/21656/1393940836/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [meta-ti] [master/kirkstone] u-boot-ti: Fix SPL binary name for SD/MMC media on HS boards
On Mon, Oct 02, 2023 at 11:44:42AM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
>
>
> On 10/2/2023 10:30 AM, Andrew Davis via lists.yoctoproject.org wrote:
> >On 10/2/23 9:06 AM, Julien Panis wrote:
> >>On 9/29/23 14:25, Julien Panis wrote:
> >>>The SPL binary built by u-boot for SD/MMC/eMMC media on HS platforms is
> >>>u-boot-spl_HS_MLO. Thanks to this fix, the binary is properly installed
> >>>and deployed.
> >>>
> >>>Signed-off-by: Julien Panis
> >>>---
> >>> meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc | 6 +++---
> >>> 1 file changed, 3 insertions(+), 3 deletions(-)
> >>>
> >>>diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> >>>b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> >>>index d9a3a520e857..9ca0fb44d127 100644
> >>>--- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> >>>+++ b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti.inc
> >>>@@ -100,9 +100,9 @@ UBOOT_HS_XLD_IMAGE =
> >>>"u-boot-spl_HS_X-LOADER-${MACHINE}-${PV}-${PR}"
> >>> UBOOT_HS_XLD_SYMLINK = "u-boot-spl_HS_X-LOADER-${MACHINE}"
> >>> # HS MLO
> >>>-UBOOT_HS_MLO_BINARY = "u-boot_HS_MLO"
> >>>-UBOOT_HS_MLO_IMAGE = "u-boot_HS_MLO-${MACHINE}-${PV}-${PR}"
> >>>-UBOOT_HS_MLO_SYMLINK = "u-boot_HS_MLO-${MACHINE}"
> >>>+UBOOT_HS_MLO_BINARY = "u-boot-spl_HS_MLO"
> >>>+UBOOT_HS_MLO_IMAGE = "u-boot-spl_HS_MLO-${MACHINE}-${PV}-${PR}"
> >>>+UBOOT_HS_MLO_SYMLINK = "u-boot-spl_HS_MLO-${MACHINE}"
> >>> # HS ISSW
> >>> UBOOT_HS_ISSW_BINARY = "u-boot-spl_HS_ISSW"
> >>
> >>I'm not sure that this patch should be applied actually.
> >>In doc/README.ti-secure, u-boot_HS_MLO is mentioned for
> >>Keystone2 Secure Devices.
> >>So, maybe this name was used intentionally...(?)
> >>
> >
> >On Keystone2 HS, we do not use SPL, so the ROM loaded image (MLO) is the
> >normal U-Boot image, we name it u-boot_HS_MLO. For others that do use SPL
> >the ROM image is the SPL, and it is called u-boot-spl_HS_MLO.
> >
> >So this patch has the right idea, just we should add another deployed image
> >var in addition to this one, not replace it, maybe:
> >
> >SPL_HS_MLO_BINARY = "u-boot-spl_HS_MLO"
> >...
>
> And add the appropriate install code later in the file as well.
Was this supposed to be changed from UBOOT_HS_MLO_* -> SPL_HS_MLO_* per the
discussion above? Or did I miss something and the old patch got merged:
https://git.yoctoproject.org/meta-ti/commit/?id=5306d61211edecf3d04cd9e8c0b64cd4a0ef3549
--
Denys
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17082):
https://lists.yoctoproject.org/g/meta-ti/message/17082
Mute This Topic: https://lists.yoctoproject.org/mt/101656237/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe:
https://lists.yoctoproject.org/g/meta-ti/leave/6695321/21656/1393940836/xyzzy
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [meta-ti] [kirkstone][PATCH v3 0/2] Remove PRU Ethernet firmwares for legacy devices
On 10/9/2023 2:09 AM, Ravi Gunasekaran wrote: Linux kernel 6.1 does not have support for PRU-ICSSM driver. So remove packaging of all the PRU-ICSSM firmwares for kernel 6.1 based SDKs. In the v2 version, it was suggested to have the changes in the SDK layer. But after discussion with meta-ti(Ryan) and meta-processor-sdk(Gyan) maintainers, it was decided to introduce a new .inc file that removes the packaging of the firmware and include it in the kernel recipes that don't have support for PRU-ICSSM in meta-ti. This series attempts to take that approach. The support for PRU-ICSSM driver will be available in mainline and TI kernel towards the end of 2024. So until such time, this approach will be followed. v2:https://serenity.dal.design.ti.com/patchwork/project/meta-ti/patch/20230908113836.12413-1-r-gunaseka...@ti.com/ v1:https://serenity.dal.design.ti.com/patchwork/project/meta-ti/patch/20230908114439.13213-1-r-gunaseka...@ti.com/ For future reference, please do not post internal links. Instead, use https://lists.yoctoproject.org/g/meta-ti/messages Ravi Gunasekaran (2): preuth-fw: Remove packaging of PRU-ICSSM firmwares linux-ti-staging_6.1: Remove packaging of PRU-ICSSM firmwares meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb | 1 + meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc | 3 +++ 2 files changed, 4 insertions(+) create mode 100644 meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc base-commit: 041271c30496bd1457cd2bd38e7d9b2f7b14372f -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17081): https://lists.yoctoproject.org/g/meta-ti/message/17081 Mute This Topic: https://lists.yoctoproject.org/mt/101847814/21656 Group Owner: meta-ti+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/leave/6695321/21656/1393940836/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[meta-ti][master][PATCH 0/5] Update to cicd.master.202310090100
Update k3conf, linux-ti-staging_6.1, linux-ti-staging-rt_6.1, ti-linux-fw and u-boot-ti-staging_2023.04 to cicd.master.202310090100 tag LCPD Automation Script (5): ti-linux-fw: CI/CD Auto-Merger: cicd.master.202310090100 u-boot-ti-staging_2023.04: CI/CD Auto-Merger: cicd.master.202310090100 k3conf: CI/CD Auto-Merger: cicd.master.202310090100 linux-ti-staging-rt_6.1: CI/CD Auto-Merger: cicd.master.202310090100 linux-ti-staging_6.1: CI/CD Auto-Merger: cicd.master.202310090100 meta-ti-bsp/recipes-bsp/ti-linux-fw/ti-linux-fw.inc | 2 +- meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 2 +- meta-ti-bsp/recipes-devtools/k3conf/k3conf_git.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 +- 5 files changed, 5 insertions(+), 5 deletions(-) -- 1.8.3.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17079): https://lists.yoctoproject.org/g/meta-ti/message/17079 Mute This Topic: https://lists.yoctoproject.org/mt/101852345/21656 Group Owner: meta-ti+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[meta-ti][master][PATCH 1/5] ti-linux-fw: CI/CD Auto-Merger: cicd.master.202310090100
Updated the value(s) for:
TI_LINUX_FW_SRCREV
Signed-off-by: LCPD Automation Script
---
meta-ti-bsp/recipes-bsp/ti-linux-fw/ti-linux-fw.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 be072e6..889c543 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
@@ -17,7 +17,7 @@ CNM_WAVE521_FW_VERSION = "1.0.00"
TI_DM_FW_VERSION = "08.06.04"
TI_SYSFW_VERSION = "08.06.04"
-TI_LINUX_FW_SRCREV ?= "b99791cb6496139dbeb1ccf0a72bb1cb1ecfa7e6"
+TI_LINUX_FW_SRCREV ?= "f903ca69b36c5a991728867153bf2e10cac35f6c"
SRCREV = "${TI_LINUX_FW_SRCREV}"
BRANCH ?= "ti-linux-firmware"
--
1.8.3.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17080):
https://lists.yoctoproject.org/g/meta-ti/message/17080
Mute This Topic: https://lists.yoctoproject.org/mt/101852346/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[meta-ti][master][PATCH 5/5] linux-ti-staging_6.1: CI/CD Auto-Merger: cicd.master.202310090100
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script
---
meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 dc3a441..60c03e1 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
@@ -24,7 +24,7 @@ S = "${WORKDIR}/git"
BRANCH ?= "ti-linux-6.1.y"
-SRCREV ?= "7d0810d9af6bb4948af8ce2f2a3a9aa40d1b9930"
+SRCREV ?= "3ec3755134e2a6c107b43e335fa32c958a2fe5f6"
PV = "6.1.46+git${SRCPV}"
# Append to the MACHINE_KERNEL_PR so that a new SRCREV will cause a rebuild
--
1.8.3.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17077):
https://lists.yoctoproject.org/g/meta-ti/message/17077
Mute This Topic: https://lists.yoctoproject.org/mt/101852343/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[meta-ti][master][PATCH 4/5] linux-ti-staging-rt_6.1: CI/CD Auto-Merger: cicd.master.202310090100
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script
---
meta-ti-bsp/recipes-kernel/linux/linux-ti-staging-rt_6.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 2eba707..2681adf 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,5 +6,5 @@ FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}-6.1:"
BRANCH = "ti-rt-linux-6.1.y"
-SRCREV = "5c91cbf4b3d6860742df8d1849095f2cc2103059"
+SRCREV = "4a3a5f9a7567d507b37b51980516ce26b34b353e"
PV = "6.1.46+git${SRCPV}"
--
1.8.3.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17076):
https://lists.yoctoproject.org/g/meta-ti/message/17076
Mute This Topic: https://lists.yoctoproject.org/mt/101852342/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[meta-ti][master][PATCH 3/5] k3conf: CI/CD Auto-Merger: cicd.master.202310090100
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script
---
meta-ti-bsp/recipes-devtools/k3conf/k3conf_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-ti-bsp/recipes-devtools/k3conf/k3conf_git.bb
b/meta-ti-bsp/recipes-devtools/k3conf/k3conf_git.bb
index c667634..dcff684 100644
--- a/meta-ti-bsp/recipes-devtools/k3conf/k3conf_git.bb
+++ b/meta-ti-bsp/recipes-devtools/k3conf/k3conf_git.bb
@@ -10,7 +10,7 @@ PV = "0.2+git${SRCPV}"
COMPATIBLE_MACHINE = "k3"
BRANCH ?= "master"
-SRCREV = "3297ea3ecb1fd39ce70504335dc2e5fb7e33dbfe"
+SRCREV = "de06befe878be061a40540d2127d4273320b35bc"
SRC_URI =
"git://git.ti.com/git/k3conf/k3conf.git;protocol=https;branch=${BRANCH}"
--
1.8.3.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17078):
https://lists.yoctoproject.org/g/meta-ti/message/17078
Mute This Topic: https://lists.yoctoproject.org/mt/101852344/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[meta-ti][master][PATCH 2/5] u-boot-ti-staging_2023.04: CI/CD Auto-Merger: cicd.master.202310090100
Updated the value(s) for:
SRCREV
Signed-off-by: LCPD Automation Script
---
meta-ti-bsp/recipes-bsp/u-boot/u-boot-ti-staging_2023.04.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 7e8b973..fbfe2d4 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 = "17439dc59aec6375772c4302a33b23370ca9c2d5"
+SRCREV = "9390b636e8e292a85f236b4f1c70feb0ad8299cc"
do_install:append:am62xx() {
install -d ${D}/boot
--
1.8.3.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17075):
https://lists.yoctoproject.org/g/meta-ti/message/17075
Mute This Topic: https://lists.yoctoproject.org/mt/101852341/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[meta-ti] [kirkstone][PATCH v3 2/2] linux-ti-staging_6.1: Remove packaging of PRU-ICSSM firmwares
Support for PRU-ICSSM driver is not available in linux
kernel version 6.1. So do not package the firmwares in the SDK.
Signed-off-by: Ravi Gunasekaran
---
meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb | 1 +
1 file changed, 1 insertion(+)
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 60c03e1d..5a13fa94 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
@@ -9,6 +9,7 @@ inherit kernel
require recipes-kernel/linux/setup-defconfig.inc
require recipes-kernel/linux/kernel-rdepends.inc
require recipes-kernel/linux/ti-kernel.inc
+require recipes-kernel/linux/prueth-fw.inc
include ${@ 'recipes-kernel/linux/ti-kernel-devicetree-prefix.inc' if
d.getVar('KERNEL_DEVICETREE_PREFIX') else ''}
include ${@ 'recipes-kernel/linux/ti-extras.inc' if d.getVar('TI_EXTRAS') else
''}
--
2.17.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17074):
https://lists.yoctoproject.org/g/meta-ti/message/17074
Mute This Topic: https://lists.yoctoproject.org/mt/101847816/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[meta-ti] [kirkstone][PATCH v3 1/2] preuth-fw: Remove packaging of PRU-ICSSM firmwares
PRU-ICSS on AM33x, AM43x, supports different ethernet modes such
as Ethernet, HSR and PRP by means of different firmwares and the
driver loads one of the these firmware. The PRU-ICSS linux driver
may not be available for all kernel versions.
So add an .inc file that avoids the packaging of such firmwares
in the SDK, so that it can be referenced by kernel recipes that
don't support PRU-ICSS.
Signed-off-by: Ravi Gunasekaran
---
meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc | 3 +++
1 file changed, 3 insertions(+)
create mode 100644 meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
diff --git a/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
b/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
new file mode 100644
index ..6698c9ed
--- /dev/null
+++ b/meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc
@@ -0,0 +1,3 @@
+# Do not package firmwares for kernels that don't support PRUETH
+RDEPENDS:${KERNEL_PACKAGE_NAME}-base:remove:ti43x = " prueth-fw pruhsr-fw
pruprp-fw"
+RDEPENDS:${KERNEL_PACKAGE_NAME}-base:remove:ti33x = " prueth-fw pruhsr-fw
pruprp-fw"
--
2.17.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17073):
https://lists.yoctoproject.org/g/meta-ti/message/17073
Mute This Topic: https://lists.yoctoproject.org/mt/101847815/21656
Group Owner: meta-ti+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[meta-ti] [kirkstone][PATCH v3 0/2] Remove PRU Ethernet firmwares for legacy devices
Linux kernel 6.1 does not have support for PRU-ICSSM driver. So remove packaging of all the PRU-ICSSM firmwares for kernel 6.1 based SDKs. In the v2 version, it was suggested to have the changes in the SDK layer. But after discussion with meta-ti(Ryan) and meta-processor-sdk(Gyan) maintainers, it was decided to introduce a new .inc file that removes the packaging of the firmware and include it in the kernel recipes that don't have support for PRU-ICSSM in meta-ti. This series attempts to take that approach. The support for PRU-ICSSM driver will be available in mainline and TI kernel towards the end of 2024. So until such time, this approach will be followed. v2:https://serenity.dal.design.ti.com/patchwork/project/meta-ti/patch/20230908113836.12413-1-r-gunaseka...@ti.com/ v1:https://serenity.dal.design.ti.com/patchwork/project/meta-ti/patch/20230908114439.13213-1-r-gunaseka...@ti.com/ Ravi Gunasekaran (2): preuth-fw: Remove packaging of PRU-ICSSM firmwares linux-ti-staging_6.1: Remove packaging of PRU-ICSSM firmwares meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb | 1 + meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc | 3 +++ 2 files changed, 4 insertions(+) create mode 100644 meta-ti-bsp/recipes-kernel/linux/prueth-fw.inc base-commit: 041271c30496bd1457cd2bd38e7d9b2f7b14372f -- 2.17.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17072): https://lists.yoctoproject.org/g/meta-ti/message/17072 Mute This Topic: https://lists.yoctoproject.org/mt/101847814/21656 Group Owner: meta-ti+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
