date:20240411

Re: [yocto] [ANNOUNCEMENT] Yocto Project 4.3.4 is Released

2024-04-11 Thread Lee Chee Yang

> Can we expect a last 4.3.5 release, or was this the last one?

Seems like no plan for 4.3.5.
https://lists.yoctoproject.org/g/yocto/message/62906 
I think this should be the last dot release for nanbield.

> I'm asking to know whether the documentation branch for "nanbield" still needs
> maintaining for a few more weeks.
> 
> Thanks in advance
> Cheers
> Michael.
> 
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62923): https://lists.yoctoproject.org/g/yocto/message/62923
Mute This Topic: https://lists.yoctoproject.org/mt/105438322/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [linux-yocto std kernel]: update std kernel for nxp-imx9

2024-04-11 Thread Xiaolei Wang via lists.yoctoproject.org

Hi bruce

Would you please help to  merge the following patch into branch:

v6.1/standard/nxp-sdk-6.1/nxp-soc

for nxp-imx9 bsp?

The following changes since commit 93c514e7433e49536a23abaca358935674922bad:

  arm64: dts: fix ecspi2 dts node (2024-03-22 11:48:47 +0800)

are available in the Git repository at:

  https://github.com/wangxiaolei12/linux-yocto-6.1.git 
v6.1/standard/nxp-sdk-6.1/nxp-soc

for you to fetch changes up to 02fe605dcc348f36559b8ce4833cece1f1f65224:

  LF-10611 arm64: dts: imx8mq-evk-rpmsg: fix CMA memory reservation fail 
(2024-04-12 09:07:33 +0800)


Alexander Sverdlin (1):
  LF-9506-2 tty: serial: fsl_lpuart: fix race on RX DMA shutdown

Alice Guo (7):
  LF-9535 soc: imx: split i.MX93 SoC device support from soc-imx8m.c
  LF-9476-1 ele_base_msg: handle common fuse with special id
  LF-9476-2 nvmem: imx: update read_common_fuse with special ID
  LF-9476-3 nvmem: imx: update i.MX93 fuse read driver
  LF-9646-1: soc: imx: remove the part related to i.MX9 from soc-imx8m.c
  LF-9646-2 soc: imx9: i.MX91P reuses i.MX93 SoC driver
  LF-10365 nvmem: imx: i.MX8ULP: update fsb_bank_reg of imx8ulp_fsb_s400_hw

Alice Yuan (4):
  LF-9127-1: arm64: dtsi: imx8ulp: Support suspend/resume when camera is 
running
  LF-9127-2: media: csi: Support suspend/resume when camera is running
  LF-9127-3: media: isi: support suspend/resume when camera is running
  LF-9638 media: isi: Fix the isi-m2m play hang if convert format

Andrew Lunn (1):
  net: mdio: Add dedicated C45 API to MDIO bus drivers

Andy Shevchenko (1):
  device property: Introduce fwnode_device_is_compatible() helper

Apeksha Gupta (1):
  net/fec-uio: Fixed error handling

Camelia Groza (16):
  net: phy: aquantia: Add support for AQR115
  net: sdk_fman: macsec: check the return value of FM_MAC_GetId
  net: sdk_fman: macsec: free locks on error paths
  net: sdk_fman: fm_cc: free resources on MatchTableSet error path
  net: sdk_fman: fm_manip: initialize prsArrayOffset
  net: sdk_fman: fm_manip: release the p_Manip spinlock on error
  net: sdk_fman: wrapper: check the return value of FM_CtrlMonGetCounters
  fsl_qbman: check qman_ccsrmempeek's return value
  net: sdk_fman: cleanup memory on fm_port_probe error paths
  net: sdk_fman: cleanup memory on fm_probe error paths
  net: sdk_fman: initialize variables before use
  net: sdk_fman: cleanup SP memory on FM_Config errors
  net: sdk_fman: cleanup resources if HashTableSet fails
  soc: fsl: qbman: check kzalloc return value
  net: fman: fix variable type
  net: sdk_fman: avoid division by zero

Carlos Song (4):
  MLK-26127-1 arm64: dts: imx91p-9x9-qsb: add lpspi master support
  MLK-26127-2 arm64: dts: imx91p-9x9-qsb: add lpspi slave support
  LF-9490 arm64: dts: imx93: enable eDMA for lpspi devices
  LF-9692 arm64: dts: imx91p-11x11-evk: Add lpspi support

Chancel Liu (18):
  LF-9256: arm64: dts: imx93-11x11-evk-rpmsg: Disable unavailable devices
  MLK-26119: arm64: dts: imx91p-9x9-qsb-aud-hat: Add a new DT to support 
AUD-HAT board
  LF-9645-1: arm64: dts: imx91p-11x11-evk-mqs: Add a new DT to support MQS
  LF-9645-2: arm64: dts: imx91p-11x11-evk-aud-hat: Add a new DT to support 
AUD-HAT board
  LF-9688-1: arm64: dts: imx93-9x9-qsb-rpmsg: Add a DT to support LPA
  LF-9688-2: arm64: dts: imx93-9x9-qsb-rpmsg-lpv: Add a DT to support LPV
  LF-9708: arm64: dts: imx93-9x9-qsb-aud-hat: Use RPI 3v3 and 5v regulator
  ASoC: fsl_micfil: Add new registers and new bit definition
  ASoC: fsl_micfil: Add fsl_micfil_use_verid function
  ASoC: fsl_micfil: Use SET_SYSTEM_SLEEP_PM_OPS to simplify PM
  LF-9333: ASoC: fsl_rpmsg: Move MCLK control to runtime suspend/resume 
phase
  Revert "LF-9333: ASoC: fsl_rpmsg: Move MCLK control to runtime 
suspend/resume phase"
  LF-9368: arm64: dts: imx93-11x11-evk-rpmsg: Enable dynamic buffer size 
for i2c-rpmsg
  LF-9910-1: arm64: dts: imx8m: Let WM8524 driver constrain supported rate
  LF-9910-2: Revert "LF-6278-2: ASoC: fsl_rpmsg: Constrain rates of wm8524 
codec"
  ASoC: soc-pcm.c: Clear DAIs parameters after stream_active is updated
  ASoC: soc-pcm.c: Make sure DAI parameters cleared if the DAI becomes 
inactive
  LF-9973-7: arm64: dts: imx93: add fsl,sai-mclk-direction-output

Clark Wang (6):
  MLK-26126 arm64: dts: imx91p-9x9-qsb: add i3c support
  LF-9574-1 nvmem: imx: change the unit of offset
  LF-9574-2 arm64: dts: imx93: correct the offset of soc-uid
  LF-9584-1 nvmem: imx: add the function of swapping 6bytes of MAC address
  LF-9584-3 arm64: dts: ims93: add nvmem support for eqos
  LF-9690 arm64: dts: imx91p-11x11-evk: Add i3c support

Colin Foster (2):
  net: mscc: ocelot: expose generic phylink_mac_config routine
  net: mscc: ocelot: expose serdes

[linux-yocto] [linux-yoct rt kernel]: update rt kernel for nxp-imx9

2024-04-11 Thread Xiaolei Wang via lists.yoctoproject.org

Hi bruce

Would you please help to  merge the following patch into branch:

v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc

for nxp-imx9 bsp?

The following changes since commit 6d570a6b9d2e8aaabc5e7d461334974b9574b386:

  arm64: dts: fix ecspi2 dts node (2024-03-22 11:52:56 +0800)

are available in the Git repository at:

  https://github.com/wangxiaolei12/linux-yocto-6.1.git 
v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc

for you to fetch changes up to 0320eb876394b7cfd7cd57e1b8be3ea3408e8bcd:

  LF-10611 arm64: dts: imx8mq-evk-rpmsg: fix CMA memory reservation fail 
(2024-04-12 09:19:35 +0800)


Alexander Sverdlin (1):
  LF-9506-2 tty: serial: fsl_lpuart: fix race on RX DMA shutdown

Alice Guo (7):
  LF-9535 soc: imx: split i.MX93 SoC device support from soc-imx8m.c
  LF-9476-1 ele_base_msg: handle common fuse with special id
  LF-9476-2 nvmem: imx: update read_common_fuse with special ID
  LF-9476-3 nvmem: imx: update i.MX93 fuse read driver
  LF-9646-1: soc: imx: remove the part related to i.MX9 from soc-imx8m.c
  LF-9646-2 soc: imx9: i.MX91P reuses i.MX93 SoC driver
  LF-10365 nvmem: imx: i.MX8ULP: update fsb_bank_reg of imx8ulp_fsb_s400_hw

Alice Yuan (4):
  LF-9127-1: arm64: dtsi: imx8ulp: Support suspend/resume when camera is 
running
  LF-9127-2: media: csi: Support suspend/resume when camera is running
  LF-9127-3: media: isi: support suspend/resume when camera is running
  LF-9638 media: isi: Fix the isi-m2m play hang if convert format

Andrew Lunn (1):
  net: mdio: Add dedicated C45 API to MDIO bus drivers

Andy Shevchenko (1):
  device property: Introduce fwnode_device_is_compatible() helper

Apeksha Gupta (1):
  net/fec-uio: Fixed error handling

Camelia Groza (16):
  net: phy: aquantia: Add support for AQR115
  net: sdk_fman: macsec: check the return value of FM_MAC_GetId
  net: sdk_fman: macsec: free locks on error paths
  net: sdk_fman: fm_cc: free resources on MatchTableSet error path
  net: sdk_fman: fm_manip: initialize prsArrayOffset
  net: sdk_fman: fm_manip: release the p_Manip spinlock on error
  net: sdk_fman: wrapper: check the return value of FM_CtrlMonGetCounters
  fsl_qbman: check qman_ccsrmempeek's return value
  net: sdk_fman: cleanup memory on fm_port_probe error paths
  net: sdk_fman: cleanup memory on fm_probe error paths
  net: sdk_fman: initialize variables before use
  net: sdk_fman: cleanup SP memory on FM_Config errors
  net: sdk_fman: cleanup resources if HashTableSet fails
  soc: fsl: qbman: check kzalloc return value
  net: fman: fix variable type
  net: sdk_fman: avoid division by zero

Carlos Song (4):
  MLK-26127-1 arm64: dts: imx91p-9x9-qsb: add lpspi master support
  MLK-26127-2 arm64: dts: imx91p-9x9-qsb: add lpspi slave support
  LF-9490 arm64: dts: imx93: enable eDMA for lpspi devices
  LF-9692 arm64: dts: imx91p-11x11-evk: Add lpspi support

Chancel Liu (18):
  LF-9256: arm64: dts: imx93-11x11-evk-rpmsg: Disable unavailable devices
  MLK-26119: arm64: dts: imx91p-9x9-qsb-aud-hat: Add a new DT to support 
AUD-HAT board
  LF-9645-1: arm64: dts: imx91p-11x11-evk-mqs: Add a new DT to support MQS
  LF-9645-2: arm64: dts: imx91p-11x11-evk-aud-hat: Add a new DT to support 
AUD-HAT board
  LF-9688-1: arm64: dts: imx93-9x9-qsb-rpmsg: Add a DT to support LPA
  LF-9688-2: arm64: dts: imx93-9x9-qsb-rpmsg-lpv: Add a DT to support LPV
  LF-9708: arm64: dts: imx93-9x9-qsb-aud-hat: Use RPI 3v3 and 5v regulator
  ASoC: fsl_micfil: Add new registers and new bit definition
  ASoC: fsl_micfil: Add fsl_micfil_use_verid function
  ASoC: fsl_micfil: Use SET_SYSTEM_SLEEP_PM_OPS to simplify PM
  LF-9333: ASoC: fsl_rpmsg: Move MCLK control to runtime suspend/resume 
phase
  Revert "LF-9333: ASoC: fsl_rpmsg: Move MCLK control to runtime 
suspend/resume phase"
  LF-9368: arm64: dts: imx93-11x11-evk-rpmsg: Enable dynamic buffer size 
for i2c-rpmsg
  LF-9910-1: arm64: dts: imx8m: Let WM8524 driver constrain supported rate
  LF-9910-2: Revert "LF-6278-2: ASoC: fsl_rpmsg: Constrain rates of wm8524 
codec"
  ASoC: soc-pcm.c: Clear DAIs parameters after stream_active is updated
  ASoC: soc-pcm.c: Make sure DAI parameters cleared if the DAI becomes 
inactive
  LF-9973-7: arm64: dts: imx93: add fsl,sai-mclk-direction-output

Clark Wang (6):
  MLK-26126 arm64: dts: imx91p-9x9-qsb: add i3c support
  LF-9574-1 nvmem: imx: change the unit of offset
  LF-9574-2 arm64: dts: imx93: correct the offset of soc-uid
  LF-9584-1 nvmem: imx: add the function of swapping 6bytes of MAC address
  LF-9584-3 arm64: dts: ims93: add nvmem support for eqos
  LF-9690 arm64: dts: imx91p-11x11-evk: Add i3c support

Colin Foster (2):
  net: mscc: ocelot: expose generic phylink_mac_config routine
  net: mscc:

Re: [yocto] Any recommendation to make software layer Yocto Compatible?

2024-04-11 Thread Paul Barker

On 08/04/2024 13:36, Duy wrote:
> Hi Richard,
> 
> Thanks for your response.
> Here is one of the recipe bbappend files I'm working on:
> meta-agl-ic-container/recipes-extended/dlt-daemon/dlt-daemon_%.bbappend · 
> master · Automotive Grade Linux / AGL / meta-agl-devel · GitLab 
> 
> meta-agl-ic-container/recipes-extended/dlt-daemon/dlt-daemon_%.bbappend · 
> master · Automotive Grade Linux / AGL / meta-agl-devel · GitLab 
> 
> 
> I think some configurations are better to be upstreaming, e.g: Adding new 
> PACKAGES, adding new PACKAGECONFIG. It avoids adding too much to bbappend. If 
> you have any idea, please share it.

When in doubt, steal from meta-virtualization.

In 
https://git.yoctoproject.org/meta-virtualization/tree/recipes-kernel/linux/linux-%25.bbappend,
there is a conditional include based on DISTRO_FEATURES. You can do the
same based on DISTRO.

Then you have a .inc file which is only included when the appropriate
configuration is enabled, like
https://git.yoctoproject.org/meta-virtualization/tree/recipes-kernel/linux/linux-yocto_virtualization.inc.
The statements in this file don't each need to check DISTRO, etc.

There is more useful information in my Creating Friendly Layers
presentation:
  * 
https://pub.pbarker.dev/presentations/2022-12-01%20Yocto%20Project%20Summit%202022.11%20-%20Creating%20Friendly%20Layers%202022%20Edition/Friendly%20Layers%202022.pdf
  * https://www.youtube.com/watch?v=6iGuKViITjg

Thanks,

-- 
Paul Barker


OpenPGP_0x27F4B3459F002257.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62922): https://lists.yoctoproject.org/g/yocto/message/62922
Mute This Topic: https://lists.yoctoproject.org/mt/105397924/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Correct way for multiple recipes to install files in the same directory

2024-04-11 Thread Peter Marko via lists.yoctoproject.org

Obvious solution is to copy chmod command to your recipe.
Peter

From: linusnilsson via Lists.Yoctoproject.Org 

Sent: Thursday, April 11, 2024 14:38
To: Marko, Peter (ADV D EU SK BFS1) ; 
yocto@lists.yoctoproject.org
Subject: Re: [yocto] Correct way for multiple recipes to install files in the 
same directory

> Changing in recipe 2 from
> chown -R user1:user1 ${D}/home/user1/.config/
> to
> chown -R user1:user1 ${D}/home/user1
> actually seems to solve the problem with those particular recipes.
>
> After getting a bit further in the bitbake process I now have the same 
> problem with another recipe that wants to add custom files to 
> /etc/polkit-1/rules.d/ but this recipe doesn't contain any 'chown' statement 
> so I can't apply the same solution here.
> file /etc/polkit-1/rules.d conflicts between attempted installs of 
> disk-automount-0.1-r0.core2_64 and polkit-124-r0.core2_64
>
> disk-automount-0.1 recipe contains:
> do_install(){
>  install -d ${D}/${sysconfdir}/polkit-1/rules.d
>  install -m 0644 ${S}/00-mount-internal.rules 
> ${D}/${sysconfdir}/polkit-1/rules.d
> }
>
> polkit-124 recipe contains:
> do_install:append() {
>  #Fix up permissions on polkit rules.d to work with rpm4 constraints
>  chmod 700 ${D}/${datadir}/polkit-1/rules.d
>  chmod 700 ${D}/${sysconfdir}/polkit-1/rules.d
>  chown polkitd:root ${D}/${datadir}/polkit-1/rules.d
>  chown polkitd:root ${D}/${sysconfdir}/polkit-1/rules.d
> }
>
> Since polkit is maintained by yocto I want to avoid making changes to it but 
> rather adapt my disk-automount recipe somehow since the problem probably is 
> on my end.
> IIRC install -d will set the permissions to 0755 unless otherwise specified 
> which might conflict with polkit's chmod 700 so I might try copying chmod 700 
> ${D}/${sysconfdir}/polkit-1/rules.d to my disk-automount recipe.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62921): https://lists.yoctoproject.org/g/yocto/message/62921
Mute This Topic: https://lists.yoctoproject.org/mt/105458437/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Wic Image Generation

2024-04-11 Thread SIMON BABY

I am also looking to format my eMMC card with 6 partitions with different
primary and secondary images. How can I achieve this using the wks file ?

Regards
Simon

On Thu, Apr 11, 2024 at 12:38 AM Bratiranjan Acharya <
bratiranja...@gmail.com> wrote:

> Hi,
> I want to create a Wic image from total scratch. Like, i have a "gpt.bin"
> which creates the partition and put the required images in it. But, i want
> to reate a wic image which will do the same. So, for that do i need that
> "gpt.bin"? like, as per my knowledge wic cannot create the gpt
> partition please do correct me if am wrong. And i dont even have any
> .bbclass file which can help to create the wic image so please help me to
> generate this wic image from total scratch, what are the steps i need to
> follow, where i need to put the wks file and how i can write in the wks
> file.
>
> FOR Eg: I need to have 6 partitions where i have a active and backup
> bootloader,kernel,rootfs so for that how we can write the wks file.
>
> Thanks & Regards
> Brati
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62920): https://lists.yoctoproject.org/g/yocto/message/62920
Mute This Topic: https://lists.yoctoproject.org/mt/105458322/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Correct way for multiple recipes to install files in the same directory

2024-04-11 Thread linusnilsson

After adding
chmod 700 ${D}/${sysconfdir}/polkit-1/rules.d
chown polkit:root ${D}/${sysconfdir}/polkit-1/rules.d
to the disk-automount recipe I get error with chown not knowing about the 
polkit user, even though I've added polkit to both DEPENDS and RDEPENDS of 
disk-automount recipe so now I've got figure out how to make it aware that the 
user polkit exists.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62919): https://lists.yoctoproject.org/g/yocto/message/62919
Mute This Topic: https://lists.yoctoproject.org/mt/105458437/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Correct way for multiple recipes to install files in the same directory

2024-04-11 Thread linusnilsson

Changing in recipe 2 from
chown -R user1:user1 ${D}/home/user1/.config/
to
chown -R user1:user1 ${D}/home/user1
actually seems to solve the problem with those particular recipes.

After getting a bit further in the bitbake process I now have the same problem 
with another recipe that wants to add custom files to /etc/polkit-1/rules.d/ 
but this recipe doesn't contain any 'chown' statement so I can't apply the same 
solution here.
file /etc/polkit-1/rules.d conflicts between attempted installs of 
disk-automount-0.1-r0.core2_64 and polkit-124-r0.core2_64

disk-automount-0.1 recipe contains:
do_install(){
install -d ${D}/${sysconfdir}/polkit-1/rules.d
install -m 0644 ${S}/00-mount-internal.rules ${D}/${sysconfdir}/polkit-1/rules.d
}

polkit-124 recipe contains:
do_install:append() {
#Fix up permissions on polkit rules.d to work with rpm4 constraints
chmod 700 ${D}/${datadir}/polkit-1/rules.d
chmod 700 ${D}/${sysconfdir}/polkit-1/rules.d
chown polkitd:root ${D}/${datadir}/polkit-1/rules.d
chown polkitd:root ${D}/${sysconfdir}/polkit-1/rules.d
}

Since polkit is maintained by yocto I want to avoid making changes to it but 
rather adapt my disk-automount recipe somehow since the problem probably is on 
my end.
IIRC install -d will set the permissions to 0755 unless otherwise specified 
which might conflict with polkit's chmod 700 so I might try copying chmod 700 
${D}/${sysconfdir}/polkit-1/rules.d to my disk-automount recipe.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62918): https://lists.yoctoproject.org/g/yocto/message/62918
Mute This Topic: https://lists.yoctoproject.org/mt/105458437/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] Trial merge of v5.15.154 v6.1.85 v6.6.26 for linux-yocto

2024-04-11 Thread Kevin Hao

Hi Bruce,

This is a trial merge of the stable kernel v5.15.154 v6.1.85 v6.6.26 for the 
following branches in the linux-yocto.
  5925e69a8f2a  v5.15/standard/sdkv5.10/axxia
  5bf35db75320  v5.15/standard/preempt-rt/sdkv5.10/axxia
 #Have textual conflicts
  f1612b786de6  v5.15/standard/base
  8363ea6d87e8  v5.15/standard/preempt-rt/base  
 #Have textual conflicts
  347b61fa360d  v5.15/standard/cn-sdkv5.4/octeon
 #Have textual conflicts
  e64df8cfa8eb  v5.15/standard/preempt-rt/cn-sdkv5.4/octeon 
 #Have textual conflicts
  bc767f3e7825  v5.15/standard/cn-sdkv5.15/octeon   
 #Have textual conflicts
  90eb13df6482  v5.15/standard/preempt-rt/cn-sdkv5.15/octeon
 #Have textual conflicts
  1cabfc8f2dbc  v5.15/standard/ti-sdk-5.10/ti-j72xx 
 #Have semantic conflicts
  4d083daef3ed  v5.15/standard/preempt-rt/ti-sdk-5.10/ti-j72xx  
 #Have textual and semantic conflicts
  06e883c42fe2  v5.15/standard/nxp-sdk-5.15/nxp-soc
  e0ace473d4b2  v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc  
 #Have textual conflicts
  769a2392ad3d  v5.15/standard/bcm-2xxx-rpi 
 #Have textual conflicts
  1deb8e9ba48e  v5.15/standard/preempt-rt/bcm-2xxx-rpi  
 #Have textual conflicts
  cf618629fe57  v5.15/standard/nxp-sdk-5.15/nxp-s32g
  cf11e0f71c72  v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g 
 #Have textual conflicts
  a18708278a1d  v5.15/standard/intel-sdk-5.15/intel-socfpga
  bb504ab94f51  v5.15/standard/preempt-rt/intel-sdk-5.15/intel-socfpga  
 #Have textual conflicts
  74ed73ae4e31  v5.15/standard/x86
  977d037e28ee  v5.15/standard/preempt-rt/x86   
 #Have textual conflicts
  2dd9e704edd6  v5.15/standard/sdkv5.15/xlnx-soc
  2a10f2529c31  v5.15/standard/preempt-rt/sdkv5.15/xlnx-soc 
 #Have textual conflicts
  30f61df8ab5a  v6.1/standard/sdkv5.10/axxia
  1a4ab3c1207d  v6.1/standard/preempt-rt/sdkv5.10/axxia
  92979a1bf2dc  v6.1/standard/base
  44805c4a2678  v6.1/standard/preempt-rt/base
  a87a14225944  v6.1/standard/ti-sdk-6.1/ti-j7xxx
  c829d63cc5b3  v6.1/standard/preempt-rt/ti-sdk-6.1/ti-j7xxx
  7ed1b193352b  v6.1/standard/nxp-sdk-6.1/nxp-soc   
 #Have textual conflicts
  0ad42edcaeeb  v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc
 #Have textual conflicts
  7b70f4712dbd  v6.1/standard/cn-sdkv5.15/octeon
  4ce7dd8f0122  v6.1/standard/preempt-rt/cn-sdkv5.15/octeon
  6c4e1ea6cee0  v6.1/standard/cn-sdkv6.1/octeon
  3228b493dee6  v6.1/standard/preempt-rt/cn-sdkv6.1/octeon
  c44ef81828df  v6.1/standard/microchip-polarfire-soc
  735431c8ee60  v6.1/standard/preempt-rt/microchip-polarfire-soc
  321bb8234822  v6.1/standard/bcm-2xxx-rpi
  6d266c65f08c  v6.1/standard/preempt-rt/bcm-2xxx-rpi
  a40c5221ae3c  v6.1/standard/nxp-sdk-5.15/nxp-s32g
  11d890c265bb  v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g
  5401d6047150  v6.1/standard/intel-sdk-6.1/intel-socfpga
  9203c9ba2bc3  v6.1/standard/preempt-rt/intel-sdk-6.1/intel-socfpga
  745e34c08a7e  v6.1/standard/x86
  019e525b1a09  v6.1/standard/preempt-rt/x86
  35b64bc7999d  v6.1/standard/sdkv6.1/xlnx-soc
  a5dc8336cb79  v6.1/standard/preempt-rt/sdkv6.1/xlnx-soc
  5c452b703c5a  v6.6/standard/base
  f8319f489059  v6.6/standard/preempt-rt/base
  0757ab7120c5  v6.6/standard/nxp-sdk-6.6/nxp-soc   
 #Have semantic conflicts
  65d9bccac0ed  v6.6/standard/preempt-rt/nxp-sdk-6.6/nxp-soc
 #Have semantic conflicts

Most of the merge conflicts come from v5.15 kernel.

- There is a merge conflict on the v5.15 rt kernel. It is caused by
  stable commit 9bd2f11ac9ef ("printk: Update @console_may_schedule in 
console_trylock_spinning()")
  rt commit 2d440f3f2ee5 ("printk: move console printing to kthreads")

  We just need to drop the changes introduced by stable commit 9bd2f11ac9ef 
because the original
  console_trylock_spinning() function was already delete by rt commit 
2d440f3f2ee5.

- There is a semantic conflict on v5.15 j72xx branches. We need to drop the 
umin() function
  in drivers/media/platform/vxe-vxd/decoder/h264_secure_parser.c because an 
umin() macro
  was introduce by stable commit cf716d5a0dd8 ("minmax: add umin(a, b) and 
umax(a, b)")

- There is also a semantic conflict on v6.6 nxp branches. We need adjust the 
change of
  stable commit e1e4a5cbb0a1 ("ASoC: fsl_sai: Fix no frame sync clock issue on 
i.MX8MP")
  based on the changes introduced by sdk commit ce4d3e93d18f ("ASoC: fsl_sai: 
add fsl,txm-rxs
  property support")

All the branches have passed my build test. I have pushed all these branches to:
https://github.com/haokexin/linux

You can use this as a reference for the linux-yocto stable kernel bump.

Thanks,
Kevin

[linux-yocto] net/can: llce: Drop unused label in register_devlink_params()

2024-04-11 Thread Kevin Hao

From: Kevin Hao 

This unused label was introduced by sdk commit 6f13f0d7b7a7 ("net/can:
llce: Add self-recv devlink parameter").

Signed-off-by: Kevin Hao 
---
Hi Bruce,

Please help me merge this into the following two branches:
  v6.1/standard/nxp-sdk-5.15/nxp-s32g
  v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g

 drivers/net/can/llce/llce_can.c | 1 -
 1 file changed, 1 deletion(-)

diff --git a/drivers/net/can/llce/llce_can.c b/drivers/net/can/llce/llce_can.c
index 8d059ae6626f..57336d06d369 100644
--- a/drivers/net/can/llce/llce_can.c
+++ b/drivers/net/can/llce/llce_can.c
@@ -816,7 +816,6 @@ static int register_devlink_params(struct llce_can *llce, 
struct device *dev)
 unreg_devlink:
if (ret)
devlink_unregister(devlink);
-free_devlink:
if (ret)
devlink_free(devlink);
 
-- 
2.44.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13794): 
https://lists.yoctoproject.org/g/linux-yocto/message/13794
Mute This Topic: https://lists.yoctoproject.org/mt/105460526/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [PATCH 2/2] media: vxe-vxd: Fix the incorrect indentation in topaz_video_destroy_context()

2024-04-11 Thread Kevin Hao

From: Kevin Hao 

This was introduced by sdk commit 79a372458bdf ("vxe-vxd: encoder: Fix
memory leak in vxe encoder driver").

Signed-off-by: Kevin Hao 
---
 drivers/media/platform/vxe-vxd/encoder/topaz_api.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/media/platform/vxe-vxd/encoder/topaz_api.c 
b/drivers/media/platform/vxe-vxd/encoder/topaz_api.c
index 66e073478cb0..7c70457b2483 100644
--- a/drivers/media/platform/vxe-vxd/encoder/topaz_api.c
+++ b/drivers/media/platform/vxe-vxd/encoder/topaz_api.c
@@ -3116,8 +3116,8 @@ static int topaz_video_destroy_context(struct 
topaz_stream_context *str_ctx)
  
>coded_package[i]->header_buffer->mem_info))
IMG_DBG_ASSERT("Free failed" == NULL);
 
-   kfree(video->coded_package[i]->header_buffer);
-   video->coded_package[i]->header_buffer = NULL;
+   kfree(video->coded_package[i]->header_buffer);
+   video->coded_package[i]->header_buffer = NULL;
 
kfree(video->coded_package[i]);
video->coded_package[i] = NULL;
-- 
2.44.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13793): 
https://lists.yoctoproject.org/g/linux-yocto/message/13793
Mute This Topic: https://lists.yoctoproject.org/mt/105459980/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [PATCH 1/2] media: vxe-vxd: Drop unused variable and function in vxd_v4l2.c

2024-04-11 Thread Kevin Hao

From: Kevin Hao 

These unused variable and function were introduced by following two SDK
commit:
f8e6ff41424e ("decoder: separate V4L2 node implementation from common driver")
441f9ae2b664 ("vxe-vxd: decoder: allowing vb mapping to change for buffer 
importing")

Signed-off-by: Kevin Hao 
---
 .../media/platform/vxe-vxd/decoder/vxd_v4l2.c| 16 
 1 file changed, 16 deletions(-)

diff --git a/drivers/media/platform/vxe-vxd/decoder/vxd_v4l2.c 
b/drivers/media/platform/vxe-vxd/decoder/vxd_v4l2.c
index f325f3812214..2867db8f431e 100644
--- a/drivers/media/platform/vxe-vxd/decoder/vxd_v4l2.c
+++ b/drivers/media/platform/vxe-vxd/decoder/vxd_v4l2.c
@@ -364,21 +364,6 @@ static void return_worker(void *work)
kfree(res);
 }
 
-static void vxd_error_recovery(struct vxd_dec_ctx *ctx)
-{
-   int ret = -1;
-
-   /*
-* In the previous frame decoding fatal error has been detected
-* so we need to reload the firmware to make it alive.
-*/
-   pr_debug("Reloading the firmware because of previous error\n");
-   vxd_clean_fw_resources(ctx->dev);
-   ret = vxd_prepare_fw(ctx->dev);
-   if (ret)
-   pr_err("Reloading the firmware failed!!");
-}
-
 static struct vxd_dec_q_data *get_q_data(struct vxd_dec_ctx *ctx,
 enum v4l2_buf_type type)
 {
@@ -894,7 +879,6 @@ static void vxd_dec_stop_streaming(struct vb2_queue *vq)
struct list_head *list;
struct list_head *temp;
struct vxd_buffer *buf = NULL;
-   struct vxd_mapping *mapping = NULL;
 
if (V4L2_TYPE_IS_OUTPUT(vq->type))
ctx->dst_streaming = FALSE;
-- 
2.44.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13792): 
https://lists.yoctoproject.org/g/linux-yocto/message/13792
Mute This Topic: https://lists.yoctoproject.org/mt/105459978/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[linux-yocto] [linux-yocto 0/2] Fix two build warnings on v5.15 j72xx branches

2024-04-11 Thread Kevin Hao

From: Kevin Hao 

Hi Bruce,

These two patches fix several build warnings on v5.15 j72xx branches.
Please help me merge them into the following two branches:
  v5.15/standard/ti-sdk-5.10/ti-j72xx
  v5.15/standard/preempt-rt/ti-sdk-5.10/ti-j72xx

Kevin Hao (2):
  media: vxe-vxd: Drop unused variable and function in vxd_v4l2.c
  media: vxe-vxd: Fix the incorrect indentation in
topaz_video_destroy_context()

 .../media/platform/vxe-vxd/decoder/vxd_v4l2.c| 16 
 .../media/platform/vxe-vxd/encoder/topaz_api.c   |  4 ++--
 2 files changed, 2 insertions(+), 18 deletions(-)

-- 
2.44.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13791): 
https://lists.yoctoproject.org/g/linux-yocto/message/13791
Mute This Topic: https://lists.yoctoproject.org/mt/105459977/21656
Group Owner: linux-yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [ANNOUNCEMENT] Yocto Project 4.3.4 is Released

2024-04-11 Thread Michael Opdenacker via lists.yoctoproject.org


Hi Lee

On 4/10/24 at 10:51, Lee Chee Yang wrote:


Hi

We are pleased to announce the Yocto Project 4.3.4 Release is now 
available for download.




Can we expect a last 4.3.5 release, or was this the last one?
I'm asking to know whether the documentation branch for "nanbield" still 
needs maintaining for a few more weeks.


Thanks in advance
Cheers
Michael.

--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62917): https://lists.yoctoproject.org/g/yocto/message/62917
Mute This Topic: https://lists.yoctoproject.org/mt/105438322/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Correct way for multiple recipes to install files in the same directory

2024-04-11 Thread Peter Marko via lists.yoctoproject.org

From: yocto@lists.yoctoproject.org  On Behalf Of 
linusnilsson via lists.yoctoproject.org
Sent: Thursday, April 11, 2024 9:53
To: yocto@lists.yoctoproject.org
Subject: [yocto] Correct way for multiple recipes to install files in the same 
directory


> Hi!
> How/can I let multiple recipes install files in the same directory without 
> getting a conflict during bitbake process?
>
> Recipe 1 creates a user and its homedir:
> inherit useradd
> USERADD_PACKAGES = "${PN}"
> USERADD_PARAM:${PN} = "-u 1000 -d /home/user1 -m -s /bin/bash -p 'XXX' user1"
> do_install(){
>  install -d ${D}/home/user1
>  chown -R user1:user1 ${D}/home/user1
> }
>
> Recipe 2 wants to install some config-files inside /home/user1/.config/.
> DEPENDS = "recipe1"
> RDEPENDS:${PN} = "recipe1"
> do_install(){
>  install -d ${D}/home/user1/.config/
>  install -m 0644 sourcefile ${D}/home/user1/.config/
>  chown -R user1:user1 ${D}/home/user1/.config/

Have you tried to change this line to

chown -R user1:user1 ${D}/home/user1

The error may come from fact that directory /home/user1 has different ownership 
in both recipes
> }
>
> There is also FILES directives at the end of each recipe for the 
> corresponding files. For better readability I've removed everything that I 
> deemed was irrelevant.
> The problem I get when trying to bitbake the image is during the do_rootfs 
> stage:
> file /home/user1 conflicts between attempted installs of  and 
> 
>
> If I comment out the "chown" line from both recipes it seems to work but then 
> I guess those directories will be owned by root during runtime, which will be 
> a problem for user1.
>
> Is there a proper way to do this?
>
> Kind regards, Linus

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62916): https://lists.yoctoproject.org/g/yocto/message/62916
Mute This Topic: https://lists.yoctoproject.org/mt/105458437/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Correct way for multiple recipes to install files in the same directory

2024-04-11 Thread Markus Volk

On Thu, Apr 11 2024 at 12:52:49 AM -07:00:00, linusnils...@hotmail.com 
wrote:

Is there a proper way to do this?

Kind regards, Linus


Hi,
can't tell if this would be a proper way, but this is how I do it and 
what works for me:


Create a main user:


Inherit a main-user class for every recipe that wants to write stuff to 
/home/user



You can override the values set in main-user.bbclass to fit your needs 
in e.g. local.conf


Regards,
Markus



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62915): https://lists.yoctoproject.org/g/yocto/message/62915
Mute This Topic: https://lists.yoctoproject.org/mt/105458437/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Correct way for multiple recipes to install files in the same directory

2024-04-11 Thread linusnilsson

Hi!
How/can I let multiple recipes install files in the same directory without 
getting a conflict during bitbake process?

Recipe 1 creates a user and its homedir:
inherit useradd
USERADD_PACKAGES = "${PN}"
USERADD_PARAM:${PN} = "-u 1000 -d /home/user1 -m -s /bin/bash -p 'XXX' user1"
do_install(){
install -d ${D}/home/user1
chown -R user1:user1 ${D}/home/user1
}

Recipe 2 wants to install some config-files inside /home/user1/.config/.
DEPENDS = "recipe1"
RDEPENDS:${PN} = "recipe1"
do_install(){
install -d ${D}/home/user1/.config/
install -m 0644 sourcefile ${D}/home/user1/.config/
chown -R user1:user1 ${D}/home/user1/.config/
}

There is also FILES directives at the end of each recipe for the corresponding 
files. For better readability I've removed everything that I deemed was 
irrelevant.
The problem I get when trying to bitbake the image is during the do_rootfs 
stage:
file /home/user1 conflicts between attempted installs of  and 

If I comment out the "chown" line from both recipes it seems to work but then I 
guess those directories will be owned by root during runtime, which will be a 
problem for user1.

Is there a proper way to do this?

Kind regards, Linus

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62914): https://lists.yoctoproject.org/g/yocto/message/62914
Mute This Topic: https://lists.yoctoproject.org/mt/105458437/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Wic Image Generation

2024-04-11 Thread Bratiranjan Acharya

Hi,
I want to create a Wic image from total scratch. Like, i have a "gpt.bin"
which creates the partition and put the required images in it. But, i want
to reate a wic image which will do the same. So, for that do i need that
"gpt.bin"? like, as per my knowledge wic cannot create the gpt
partition please do correct me if am wrong. And i dont even have any
.bbclass file which can help to create the wic image so please help me to
generate this wic image from total scratch, what are the steps i need to
follow, where i need to put the wks file and how i can write in the wks
file.

FOR Eg: I need to have 6 partitions where i have a active and backup
bootloader,kernel,rootfs so for that how we can write the wks file.

Thanks & Regards
Brati

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62913): https://lists.yoctoproject.org/g/yocto/message/62913
Mute This Topic: https://lists.yoctoproject.org/mt/105458322/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [ANNOUNCEMENT] Yocto Project 4.3.4 is Released

[linux-yocto] [linux-yocto std kernel]: update std kernel for nxp-imx9

[linux-yocto] [linux-yoct rt kernel]: update rt kernel for nxp-imx9

Re: [yocto] Any recommendation to make software layer Yocto Compatible?

Re: [yocto] Correct way for multiple recipes to install files in the same directory

Re: [yocto] Wic Image Generation

Re: [yocto] Correct way for multiple recipes to install files in the same directory

Re: [yocto] Correct way for multiple recipes to install files in the same directory

[linux-yocto] Trial merge of v5.15.154 v6.1.85 v6.6.26 for linux-yocto

[linux-yocto] net/can: llce: Drop unused label in register_devlink_params()

[linux-yocto] [PATCH 2/2] media: vxe-vxd: Fix the incorrect indentation in topaz_video_destroy_context()

[linux-yocto] [PATCH 1/2] media: vxe-vxd: Drop unused variable and function in vxd_v4l2.c

[linux-yocto] [linux-yocto 0/2] Fix two build warnings on v5.15 j72xx branches

Re: [yocto] [ANNOUNCEMENT] Yocto Project 4.3.4 is Released

Re: [yocto] Correct way for multiple recipes to install files in the same directory

Re: [yocto] Correct way for multiple recipes to install files in the same directory

[yocto] Correct way for multiple recipes to install files in the same directory

[yocto] Wic Image Generation

18 matches

Site Navigation

Mail list logo

Footer information