[linux-yocto] [PATCH] net: ethernet: stmmac: fix argument of dwmac4_rx_watchdog_e50082
From: Quanyang Wang In mainline commit db2f2842e6f5 ("net: stmmac: add per-queue TX & RX coalesce ethtool support"), the argument "number_chan" of the function "rx_watchdog" in stmmac_dma_ops has been changed to "queue", so apply the same change to the function "dwmac4_rx_watchdog_e50082". Signed-off-by: Quanyang Wang Signed-off-by: Zhantao Tang --- .../net/ethernet/stmicro/stmmac/dwmac4_dma.c | 23 +-- 1 file changed, 11 insertions(+), 12 deletions(-) diff --git a/drivers/net/ethernet/stmicro/stmmac/dwmac4_dma.c b/drivers/net/ethernet/stmicro/stmmac/dwmac4_dma.c index f870bb025861..3f03ada8b4d7 100644 --- a/drivers/net/ethernet/stmicro/stmmac/dwmac4_dma.c +++ b/drivers/net/ethernet/stmicro/stmmac/dwmac4_dma.c @@ -272,22 +272,21 @@ static void dwmac4_dump_dma_regs(void __iomem *ioaddr, u32 *reg_space) static void dwmac4_rx_watchdog(void __iomem *ioaddr, u32 riwt, u32 queue) { + writel(riwt, ioaddr + DMA_CHAN_RX_WATCHDOG(queue)); } -static void dwmac4_rx_watchdog_e50082(void __iomem *ioaddr, u32 riwt, u32 number_chan) +static void dwmac4_rx_watchdog_e50082(void __iomem *ioaddr, u32 riwt, u32 queue) { - u32 chan, temp; - - for (chan = 0; chan < number_chan; chan++) { - temp = readl(ioaddr + DMA_CHAN_RX_WATCHDOG(chan)); - /* Update only RWT first */ - temp = (temp & ~DMA_CHAN_RX_WATCHDOG_RWT) | (riwt & DMA_CHAN_RX_WATCHDOG_RWT); - writel(temp, ioaddr + DMA_CHAN_RX_WATCHDOG(chan)); - /* Update RWTU */ - temp = (temp & ~DMA_CHAN_RX_WATCHDOG_RWTU) | (riwt & DMA_CHAN_RX_WATCHDOG_RWTU); - writel(temp, ioaddr + DMA_CHAN_RX_WATCHDOG(chan)); - } + u32 temp; + + temp = readl(ioaddr + DMA_CHAN_RX_WATCHDOG(queue)); + /* Update only RWT first */ + temp = (temp & ~DMA_CHAN_RX_WATCHDOG_RWT) | (riwt & DMA_CHAN_RX_WATCHDOG_RWT); + writel(temp, ioaddr + DMA_CHAN_RX_WATCHDOG(queue)); + /* Update RWTU */ + temp = (temp & ~DMA_CHAN_RX_WATCHDOG_RWTU) | (riwt & DMA_CHAN_RX_WATCHDOG_RWTU); + writel(temp, ioaddr + DMA_CHAN_RX_WATCHDOG(queue)); } static void dwmac4_dma_rx_chan_op_mode(void __iomem *ioaddr, int mode, -- 2.25.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12368): https://lists.yoctoproject.org/g/linux-yocto/message/12368 Mute This Topic: https://lists.yoctoproject.org/mt/98234466/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 std/preempt-rt kernel v5.15]: nxp-s32g: fix gmac0 not-work issue when set to speed 10M/100M using one rx/tx queue
Hi Bruce, There is one patch to fix gmac0 not-work issue when set to speed 10M/100M using one rx/tx queue. Would you please help to merge the patch into v5.15/standard/nxp-sdk-5.15/nxp-s32g v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g branches? Thanks, Zhantao -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12367): https://lists.yoctoproject.org/g/linux-yocto/message/12367 Mute This Topic: https://lists.yoctoproject.org/mt/98234465/21656 Group Owner: linux-yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] QA notification for completed autobuilder build (yocto-4.0.9.rc1)
A build flagged for QA (yocto-4.0.9.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-4.0.9.rc1 Build hash information: bitbake: 2802adb572eb73a3eb2725a74a9bbdaafc543fa7 meta-agl: 535bc8f54ce5fcb4a94204df5f2b3317beb53f23 meta-arm: a0216a41bde3f191037332a9238648bedfbc61bd meta-aws: 3f7ab5912239d667764e7df885776b267eddf265 meta-gplv2: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a meta-intel: 4c6cc14669d0e9de36e1a050ce4084ca14181722 meta-mingw: a90614a6498c3345704e9611f2842eb933dc51c1 meta-openembedded: 571e36e20e9d1f27af0eb4545291beeb64f280e2 meta-virtualization: bfa6727718bc4eb550c24e2c03a4118b4e7bc842 oecore: ff4b57903a93b710284c7c7f916ddd74712f poky: 09def309f91929f47c6cce386016ccb777bd2cfc This is an automated message from the Yocto Project Autobuilder Git: git://git.yoctoproject.org/yocto-autobuilder2 Email: richard.pur...@linuxfoundation.org -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59699): https://lists.yoctoproject.org/g/yocto/message/59699 Mute This Topic: https://lists.yoctoproject.org/mt/98230058/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Adding SSH access to runqemu script
runqemu slirp was indeed enough to access via ssh -p root@localhost StrictHostKeyChecking=No Thanks! From: Alexander Kanavin Sent: Wednesday, April 12, 2023 5:45 PM To: Edgar Mobile Cc: yocto@lists.yoctoproject.org Subject: Re: [yocto] Adding SSH access to runqemu script You can probably just add 'slirp' parameter to runqemu? Alex On Wed, 12 Apr 2023 at 19:31, Edgar Mobile wrote: > > Greetings, > > I built an Aarch64 client image with core-image-weston from master. Now I > want to access the running machine via ssh. Usually, I would do this by > adding the following to the qemu call when not using the runqemu script: > > -device virtio-net-device,netdev=user0 -netdev > user,id=user0,hostfwd=tcp::-:22 > > Is it possible to add this to the runqemu script via local.conf or so? > > Regards > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59698): https://lists.yoctoproject.org/g/yocto/message/59698 Mute This Topic: https://lists.yoctoproject.org/mt/98224416/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Adding SSH access to runqemu script
You can probably just add 'slirp' parameter to runqemu? Alex On Wed, 12 Apr 2023 at 19:31, Edgar Mobile wrote: > > Greetings, > > I built an Aarch64 client image with core-image-weston from master. Now I > want to access the running machine via ssh. Usually, I would do this by > adding the following to the qemu call when not using the runqemu script: > > -device virtio-net-device,netdev=user0 -netdev > user,id=user0,hostfwd=tcp::-:22 > > Is it possible to add this to the runqemu script via local.conf or so? > > Regards > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59697): https://lists.yoctoproject.org/g/yocto/message/59697 Mute This Topic: https://lists.yoctoproject.org/mt/98224416/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] libcrypto.so.1.0.0 and libssl.so.1.0.0 - any easy way to include these into a kirkstone build along with the newer versions? #kirkstone #libcrypto #libssl
Using poky/kirkstone as a base, I am sideloading an app that requires libcrypto.so.1.0.0 and libssl.so.1.0.0 which are not present by default. I have seen suggestions to include various "10" packages such as libcrypto10 etc but they don't seem to be present or at least not in poky /meta-openembedded. Is there a (straightforward) way to get yocto to include multiple versions of libssl.so /libcrypto.so ( (via IMAGE_INSTALL:append etc..).short of manually copying them in? Thanks, Bruce -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59696): https://lists.yoctoproject.org/g/yocto/message/59696 Mute This Topic: https://lists.yoctoproject.org/mt/98224561/21656 Mute #kirkstone:https://lists.yoctoproject.org/g/yocto/mutehashtag/kirkstone Mute #libcrypto:https://lists.yoctoproject.org/g/yocto/mutehashtag/libcrypto Mute #libssl:https://lists.yoctoproject.org/g/yocto/mutehashtag/libssl Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Adding SSH access to runqemu script
Greetings, I built an Aarch64 client image with core-image-weston from master. Now I want to access the running machine via ssh. Usually, I would do this by adding the following to the qemu call when not using the runqemu script: -device virtio-net-device,netdev=user0 -netdev user,id=user0,hostfwd=tcp::-:22 Is it possible to add this to the runqemu script via local.conf or so? Regards -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59695): https://lists.yoctoproject.org/g/yocto/message/59695 Mute This Topic: https://lists.yoctoproject.org/mt/98224416/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [RFC][yocto][meta-lts-mixins][kirkstone/go] Backport golang from master to kirkstone
Hi, Just to inform the mailing list that the branch is available on the meta-lts-mixins yocto repo. https://git.yoctoproject.org/meta-lts-mixins/log/?h=kirkstone/go Thanks for the help and feedback. Jose Alexander Kanavin escreveu no dia sexta, 31/03/2023 à(s) 18:49: > You need to send your public ssh key to Michael (cc) and explain what > access should be granted with that (which repo, which branch(es)). > > In this case, > https://git.yoctoproject.org/meta-lts-mixins/ > kirkstone/go > > Alex > > On Fri, 31 Mar 2023 at 18:15, Jose Quaresma > wrote: > > > > Hi Alex, > > > > I don't have any account/keys that allow me to push directly > git.yoctoproject.org > > maybe I need to setup my keys somewhere like with poky-contrib [1] > > > > I will send all the patches to the yocto mailing list as recommended. > > > > [1] https://wiki.yoctoproject.org/wiki/Poky_Contributions > > > > Jose > > > > Alexander Kanavin escreveu no dia quinta, > 30/03/2023 à(s) 11:08: > >> > >> I think I pushed the work directly to the respecitve branches in > >> meta-lts-mixins. I'd suggest you send the patches here, and we'll sort > >> out the technicalities (I can publish the branch on > >> git.yoctoproject.org, or maybe you'll be able to push directly as > >> well, provided you also send the patches here). There's no autobuilder > >> testing; for mixin items the contributors are trusted :) > >> > >> Alex > >> > >> > >> On Thu, 30 Mar 2023 at 11:20, Jose Quaresma > wrote: > >> > > >> > Hi, > >> > > >> > The golang version in kirkstone is the 1.17 and because of this is > not possible to use some recent version of other projects like docker that > requires a more recent version of the language. > >> > > >> > I have a kirkstone branch [1] available at Foundries.io with the > golang backported from the oe-core master that I liked to submit to the > meta-lts-mixins [2]. > >> > Alex is the maintainer of the dunfell golang backport and this > kirkstone branch is based on that version. > >> > > >> > Would that be interesting for the project? How should I proceed? > >> > > >> > [1] https://github.com/foundriesio/meta-lts-mixins/tree/kirkstone/go > >> > [2] https://git.yoctoproject.org/meta-lts-mixins > >> > > >> > Jose > >> > > >> > -- > >> > Best regards, > >> > > >> > José Quaresma > > > > > > > > -- > > Best regards, > > > > José Quaresma > -- Best regards, José Quaresma -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59694): https://lists.yoctoproject.org/g/yocto/message/59694 Mute This Topic: https://lists.yoctoproject.org/mt/97946990/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] create-layers-setup Yaml support #bitbake
Here is the pull request if curious: https://github.com/renovatebot/renovate/pull/17077 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59693): https://lists.yoctoproject.org/g/yocto/message/59693 Mute This Topic: https://lists.yoctoproject.org/mt/98196703/21656 Mute #bitbake:https://lists.yoctoproject.org/g/yocto/mutehashtag/bitbake Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] create-layers-setup Yaml support #bitbake
Yeah, actually, my colleague found a pull request in their Github. It seems to be blocked, and inactive for months. But, anyway, I guess we will need to wait. We have been considering setup-layers feature as a mid-to-late future solution anyway. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59692): https://lists.yoctoproject.org/g/yocto/message/59692 Mute This Topic: https://lists.yoctoproject.org/mt/98196703/21656 Mute #bitbake:https://lists.yoctoproject.org/g/yocto/mutehashtag/bitbake Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-parsec][langdale][PATCH] Fix PACKAGECONFIG check in Parsec OEQA tests
From: Anton Antonov If PACKAGECONFIG is not defined in local.conf then its default value is not included in cls.tc.td map. Signed-off-by: Anton Antonov Signed-off-by: Armin Kuster --- meta-parsec/lib/oeqa/runtime/cases/parsec.py | 13 +++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/meta-parsec/lib/oeqa/runtime/cases/parsec.py b/meta-parsec/lib/oeqa/runtime/cases/parsec.py index 6be84ba..c6e7893 100644 --- a/meta-parsec/lib/oeqa/runtime/cases/parsec.py +++ b/meta-parsec/lib/oeqa/runtime/cases/parsec.py @@ -61,9 +61,18 @@ class ParsecTest(OERuntimeTestCase): def check_packageconfig(self, prov): """ Check that the require provider is included in Parsec """ -if prov not in self.tc.td['PACKAGECONFIG:pn-parsec-service']: + +if 'PACKAGECONFIG:pn-parsec-service' in self.tc.td.keys(): +providers = self.tc.td['PACKAGECONFIG:pn-parsec-service'] +else: +# PACKAGECONFIG is not defined in local.conf +# Let's use the default value +providers = "PKCS11 MBED-CRYPTO" +if 'tpm2' in self.tc.td['DISTRO_FEATURES']: +providers += " TPM" +if prov not in providers: self.skipTest('%s provider is not included in Parsec. Parsec PACKAGECONFIG: "%s"' % \ - (prov, self.tc.td['PACKAGECONFIG:pn-parsec-service'])) + (prov, providers)) def check_packages(self, prov, packages): """ Check for the required packages for Parsec providers software backends """ -- 2.25.1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59691): https://lists.yoctoproject.org/g/yocto/message/59691 Mute This Topic: https://lists.yoctoproject.org/mt/98221139/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] create-layers-setup Yaml support #bitbake
You should first take this issue up with 'renovate' upstream, not with yocto. Ask them, how is one supposed to handle updating json files using that tool? Maybe you need to write a custom extension specific to that format that doesn't require placing metadata inside the json? Alex On Wed, 12 Apr 2023 at 13:12, wrote: > > Renovate normally doesn't require to make changes in other files. > It supports many package files, and detects them automatically. > It parses them, and finds the dependencies without needing any change. > But, for package files which is not supported by Renovate, a regular > expression > is needed inside the file to let Renovate know where to look while parsing > the file. > As far as I know, there is no other way than adding a new line to the file. > > We are also using Renovate the same way with bb files as well. > > We have got a lot of projects, and potential projects that have several > different > dependencies. They are hosted in different repositories, and the idea is to > update > their dependencies (or not it depends on the project) regularly, and do it > automatically. > Like I said, with the package files that Renovate supports such as npm, > Dockerfiles, etc. it is easy to do, > but for our case we need to modify the json file with an added comment. For > this reason, Yaml files are > an ideal solution for us. > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59690): https://lists.yoctoproject.org/g/yocto/message/59690 Mute This Topic: https://lists.yoctoproject.org/mt/98196703/21656 Mute #bitbake:https://lists.yoctoproject.org/g/yocto/mutehashtag/bitbake Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] create-layers-setup Yaml support #bitbake
Renovate normally doesn't require to make changes in other files. It supports many package files, and detects them automatically. It parses them, and finds the dependencies without needing any change. But, for package files which is not supported by Renovate, a regular expression is needed inside the file to let Renovate know where to look while parsing the file. As far as I know, there is no other way than adding a new line to the file. We are also using Renovate the same way with bb files as well. We have got a lot of projects, and potential projects that have several different dependencies. They are hosted in different repositories, and the idea is to update their dependencies (or not it depends on the project) regularly, and do it automatically. Like I said, with the package files that Renovate supports such as npm, Dockerfiles, etc. it is easy to do, but for our case we need to modify the json file with an added comment. For this reason, Yaml files are an ideal solution for us. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59689): https://lists.yoctoproject.org/g/yocto/message/59689 Mute This Topic: https://lists.yoctoproject.org/mt/98196703/21656 Mute #bitbake:https://lists.yoctoproject.org/g/yocto/mutehashtag/bitbake Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Error at do package stage
Hi team, I am trying to build an executable for my yocto dunfell. I am new to yocto so dont have much knowledge on this. I am running to commands presently. $ bitbake zigbee (builds successfully). $ bitbake lib32-amlogic-yocto (do_package error). The error message is *ERROR: lib32-zigbee-0.1-r0 do_package: Fatal errors occurred in subprocesses:Command '['arm-pokymllib32-linux-gnueabi-objcopy', '--only-keep-debug', '/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3', '/home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/.debug/hostforEdge3']' returned non-zero exit status 1.Subprocess output:arm-pokymllib32-linux-gnueabi-objcopy: /home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3: file format not recognizedERROR: Logfile of failure stored in: /home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/temp/log.do_package.31632ERROR: Task (virtual:multilib:lib32:/home/mohan/amlogic/meta-c/recipes-example/zigbee/zigbee_0.1.bb:do_package) failed with exit code '1'NOTE: Tasks Summary: Attempted 6233 tasks of which 6220 didn't need to be rerun and 1 failed.* I tried file command on the executable file and this is the result. *$ file /home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3 /home/mohan/amlogic/build/tmp/work/armv7at2hf-neon-pokymllib32-linux-gnueabi/lib32-zigbee/0.1-r0/package/usr/bin/hostforEdge3: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-aarch64.so.1, BuildID[sha1]=2533a98d31a7a00404b3ecf98cc24e43aafd3b33, for GNU/Linux 3.14.0, with debug_info, not stripped* *$ file /home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/package/usr/bin/hostforEdge3* */home/mohan/amlogic/build/tmp/work/aarch64-poky-linux/zigbee/0.1-r0/package/usr/bin/hostforEdge3: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-aarch64.so.1, BuildID[sha1]=2533a98d31a7a00404b3ecf98cc24e43aafd3b33, for GNU/Linux 3.14.0, stripped* I have attached the bb file, makefile and logs for your reference. Also I am not sure how to add the proper compiler,linker,archive flags to the makefile. If possible please guide me on that as well. Thanks and Regards, Hassan Makefile Description: Binary data zigbee_0.1.bb Description: Binary data log.do_package Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59688): https://lists.yoctoproject.org/g/yocto/message/59688 Mute This Topic: https://lists.yoctoproject.org/mt/98214685/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] QA notification for completed autobuilder build (yocto-4.2.rc2)
Hi All, QA for yocto-4.2.rc2 is completed. This is the full report for this release: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults === Summary No high milestone defects. No new issue found. Thanks, Jing Hui > -Original Message- > From: yocto@lists.yoctoproject.org On > Behalf Of Pokybuild User > Sent: Friday, April 7, 2023 2:16 AM > To: yocto@lists.yoctoproject.org > Cc: qa-build-notificat...@lists.yoctoproject.org > Subject: [yocto] QA notification for completed autobuilder build (yocto- > 4.2.rc2) > > > A build flagged for QA (yocto-4.2.rc2) was completed on the autobuilder > and is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-4.2.rc2 > > > Build hash information: > > bitbake: ae2efb05196f9e29ef56ad9a84e2eae5fbdd8030 > meta-agl: 09135164a21a216c6e3e75d7decce896b92962f0 > meta-arm: 8acd61c427bc13024df59cdf3d8217e6e2bd2ce4 > meta-aws: d243fc1ad45dde57b4caa182a92b685540475cb2 > meta-intel: ec3147abdd0727fedc707330d58593097357f944 > meta-mingw: 250617ffa524c082b848487359b9d045703d59c2 > meta-openembedded: 2e0a581bee7fc15a78f6e19ba1e596930edee414 > meta-virtualization: 48c07a48a0e7d56266f20a01bb0c8ebc1085453b > oecore: 2bcb015b6fe72aa4c928741285c49d3d9ec55e85 > poky: 09bdad16f3a835eaa5b6158a2f8bfb180aa4cde0 > > > > This is an automated message from the Yocto Project Autobuilder > Git: git://git.yoctoproject.org/yocto-autobuilder2 > Email: richard.pur...@linuxfoundation.org > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59687): https://lists.yoctoproject.org/g/yocto/message/59687 Mute This Topic: https://lists.yoctoproject.org/mt/98110926/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Missing .o files.
> > you need to build for 32bit as well. I think you are building these > binaries outside yocto and then weirdly mixing the install. So perhaps > that should be fixed first maybe. I think the makefile is using the default compiler present in my laptop. Can you share the file paths for compiler present in my yocto build. Thanks and regards, Hassan -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59686): https://lists.yoctoproject.org/g/yocto/message/59686 Mute This Topic: https://lists.yoctoproject.org/mt/98191767/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] i.MX6DL dm-verity support on Yocto build
Hi Team, We are working on an imx6dl sabresd board with yocto linux 5.15 version. We want to use the dm-verity feature, but didn't find proper steps to do. Can you please help me how to do it properly?. Regards, Aravinthkumar, Mb:8508139500. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59685): https://lists.yoctoproject.org/g/yocto/message/59685 Mute This Topic: https://lists.yoctoproject.org/mt/98214082/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-