[linux-yocto] [PATCH] usb: dwc2: add new compatible for Intel SoCFPGA Stratix10 platform

Intel Stratix10 is very the same with Agilex platform, the DWC2 IP on the Stratix platform also does not support clock-gating. The commit 3d8d3504d233("usb: dwc2: Add platform specific data for Intel's Agilex") had fixed this issue. So, add the essential compatible to also use the specific data on

Re: [linux-yocto] [PATCH] usb: dwc2: combine platform specific data for Intel Agilex and Stratix10

Hi Bruce, Sorry! I send the wrong patch, it is the old one. Please discard this patch. I will send the new one in later. Thanks, LImeng > -Original Message- > From: linux-yocto@lists.yoctoproject.org > On Behalf Of Meng Li via lists.yoctoproject.org > Sent: Tuesday, July 18, 2023 11:50

[linux-yocto] [PATCH] usb: dwc2: combine platform specific data for Intel Agilex and Stratix10

Intel Stratix10 is very the same with Agilex platform, the DWC2 IP on the Stratix platform also does not support clock-gating. So, based on commit 3d8d3504d233("usb: dwc2: Add platform specific data for Intel's Agilex"), combine platform specific data for Intel Agilex and Stratix10 together. In

[linux-yocto]: [kernel for intel-socfpga]: usb: dwc2: add new compatible for Intel SoCFPGA Stratix10 platform

From: Limeng Hi Bruce, This patch is used to add new compatible for Intel SoCFPGA Stratix10 platform Could you please help to merge it into linux-ycoto kernel repo, both standard and rt branches v6.1/standard/intel-sdk-6.1/intel-socfpga v6.1/standard/preempt-rt/intel-sdk-6.1/intel-socfpga

Re: [linux-yocto]: [kernel for intel-socfpga]: usb: dwc2: combine platform specific data for Intel Agilex and Stratix10

On Mon, Jul 17, 2023 at 1:31 AM Meng Li wrote: > > From: Limeng > > Hi Bruce, > > This patch is used to combine platform specific data for Intel Agilex and > Stratix10. > Could you please help to merge it into linux-ycoto kernel repo, both standard > and rt branches >

Re: [linux-yocto][v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH] ARM: imx: use raw_spin_lock instead of spin_lock

merged. Bruce In message: [linux-yocto][v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc][PATCH] ARM: imx: use raw_spin_lock instead of spin_lock on 17/07/2023 Xiaolei Wang wrote: > CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW > 5.15.78-rt48-yocto-preempt-rt #1 > Hardware name:

Re: [linux-yocto][v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc & v6.1/standard/nxp-sdk-6.1/nxp-soc][PATCH 1/2] LF-8851: dmaengine: imx-sdma: sdma driver code optimization

merged. Bruce In message: [linux-yocto][v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc & v6.1/standard/nxp-sdk-6.1/nxp-soc][PATCH 1/2] LF-8851: dmaengine: imx-sdma: sdma driver code optimization on 17/07/2023 Xiaolei Wang wrote: > From: Joy Zou > > commit

Re: [linux-yocto][linux-yocto v6.1] add s25fl064l support for marvell cn96xx

In message: [linux-yocto][linux-yocto v6.1] add s25fl064l support for marvell cn96xx on 17/07/2023 Ruiqiang Hao wrote: > Hi Bruce, > > These 2 patches are for Cypress flash s25fl064l used by customer. > Please help to merge them into our linux-yocto repo. > > repo: >

Re: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx6: set CONFIG_CC_OPTIMIZE_FOR_SIZE to n

merged. Bruce In message: [linux-yocto][yocto-kernel-cache yocto-6.1][PATCH] nxp-imx6: set CONFIG_CC_OPTIMIZE_FOR_SIZE to n on 13/07/2023 Xiaolei Wang wrote: > Disable CONFIG_CC_OPTIMIZE_FOR_SIZE to fix the warning when > do_kernel_configcheck: > > WARNING:

[yocto] M+ & H bugs with Milestone Movements WW28

All, YP M+ or high bugs which moved to a new milestone in WW28 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 15025 Rust build failure on arm architecture. randy.macl...@windriver.com

[yocto] Enhancements/Bugs closed WW28!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count randy.macl...@windriver.com 4 yoann.con...@smile.fr 1 quaresma.j...@gmail.com 1 bruce.ashfi...@gmail.com 1 Grand Total 7 Thanks, Stephen K. Jolley Yocto Project Program Manager *

[yocto] Current high bug count owners for Yocto Project 4.3

All, Below is the list as of top 29 bug owners as of the end of WW28 of who have open medium or higher bugs and enhancements against YP 4.3. There are 72 possible work days left until the final release candidates for YP 4.3 needs to be released. Who Count michael.opdenac...@bootlin.com 32

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

Re: [yocto] How does SOURCEFORGE_MIRROR work?

For gSOAP? On Mon, Jul 17, 2023 at 8:21 PM Ross Burton wrote: > On 14 Jul 2023, at 21:08, Tom Isaacson via lists.yoctoproject.org > wrote: > > > > Ah, I didn't realise there was a logfile for that. > > > > For future reference, it uses > > >

Re: [yocto] Request for Quotations for development work

On Tue, 2023-07-18 at 09:00 +1200, Tom Isaacson wrote: > I read this and the linked articles and one piece in > https://www.linux.com/audience/maintainer-confidential-opportunities-and-challenges-of-the-ubiquitous-but-under-resourced-yocto-project/ > caught my eye: > > One question that comes up

Re: [yocto] Request for Quotations for development work

I read this and the linked articles and one piece in https://www.linux.com/audience/maintainer-confidential-opportunities-and-challenges-of-the-ubiquitous-but-under-resourced-yocto-project/ caught my eye: > One question that comes up a lot is the project’s development model. We’re > an “old

Re: [yocto] libgcc dependency

On Mon, Jul 17, 2023 at 6:38 AM Martin Townsend wrote: > > Hi, > > I am trying to remove all GPLv3 packages from my image. The clang > toolchain is used where possible and currently there are no > dependencies on libstdc++ and as far as I can see none on libgcc but > this library is installed in

Re: [yocto] libgcc dependency

On 17 Jul 2023, at 14:37, Martin Townsend via lists.yoctoproject.org wrote: > I am trying to remove all GPLv3 packages from my image. I’ve never encountered anyone consider the license of libgcc to be an issue here because it has the ‘GCC exception’ clauses. I suggest you speak to your

[yocto] [ptest-runner][PATCH 4/4] Change test timeout to be total elapsed time

Changes the way that tests time out to be the total elapsed time for the test, not just the time between receiving output from the test. This matches the implementation before 8259375 ("runner: Remove threads and mutexes"). Also update the timeout test case to test for this correctly.

[yocto] [ptest-runner][PATCH 0/4] Stop running ptests in parallel

07d8a67 ("runner: Correctly handle running parallel tests") made an incorrect assumption that it was OK to run ptests in parallel and interleave the output. This is not correct since OE selftest expects all text between a BEGIN and END block to be for a single ptest. Revert the commit to run in

[yocto] [ptest-runner][PATCH 3/4] Report if child dies from a signal

Tests can exit due to a signal, which should also be reported in the test output. Signed-off-by: Joshua Watt --- tests/data/signal/ptest/run-ptest | 10 tests/utils.c | 39 +++--- utils.c | 40

[yocto] [ptest-runner][PATCH 2/4] Recreate pipe for each test

The write end of the pipe has to be closed by ptest-runner to make sure that it will get EOF when the child process is done with it. This means that a new pipe needs to be opened for each child so that the write ends can be passed to it. Fixes the problem where tests would be reported with no

[yocto] [ptest-runner][PATCH 1/4] Revert "runner: Correctly handle running parallel tests"

This reverts commit 07d8a676aa962ecc5ec264ec33b0074adf2a8733. This commit incorrectly assumed that ptest ran tests in parallel, which is not true. Doing so interleaves the test output in the log file, which the OE selftest parser cannot handle and thus breaks the test cases. Signed-off-by:

[yocto] libgcc dependency

Hi, I am trying to remove all GPLv3 packages from my image. The clang toolchain is used where possible and currently there are no dependencies on libstdc++ and as far as I can see none on libgcc but this library is installed in the rootfs. I've created a script to parse all elf binaries to see

Re: [yocto] How does SOURCEFORGE_MIRROR work?

On 14 Jul 2023, at 21:08, Tom Isaacson via lists.yoctoproject.org wrote: > > Ah, I didn't realise there was a logfile for that. > > For future reference, it uses > https://github.com/yoctoproject/poky/blob/kirkstone/bitbake/lib/bb/fetch2/__init__.py#L1116 > to run through a list of atlernates,