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

All, YP M+ or high bugs which moved to a new milestone in WW40 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 14263 AB-INT PTEST: lttng-tools ptest intermittent failure

[yocto] Enhancements/Bugs closed WW40!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.pur...@linuxfoundation.org 7 oobit...@cisco.com 1 alexandre.bell...@bootlin.com 1 Grand Total 9 Thanks, Stephen K. Jolley Yocto Project Program Manager *Cell:

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

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

[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:

[yocto] Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am on the first Tuesday (PDT)

All, Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (10/5) Yocto Project Technical Team Meeting: We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional):

Re: [yocto] virtual/egl on Raspberry Pi 4

It should have automatically found user land package as one of providers but if it is not doing so that means it’s being ignored because it’s not compatible arch or something Are you compiling 32bit mode ? On Mon, Oct 4, 2021 at 4:08 PM Greg Wilson-Lindberg wrote: > Hi Khem, > Yes, the

Re: [yocto] virtual/egl on Raspberry Pi 4

Hi Khem, Yes, the Raspberry Pi boards do use closed source drivers. What I need is how do I include the proper package that will bring in the necessary virtual/egl for the Raspberry Pi 4. Greg > -Original Message- > From: Khem Raj > Sent: Monday, October 4, 2021 14:17 > To: Greg

Re: [yocto] Meta-raspberrypi - how to configure device tree for MCP251x

Hi Khem, There is nothing in /boot once the system has started, but if I mount /dev/mmcblk0p1 I can see a config.txt that includes: dtparam=spi=on dtoverlay=mcp2515-can0,oscillator=1600,interrupt=25 dtoverlay=mcp2515-can1,oscillator=1600,interrupt=23 This is what I

Re: [yocto] virtual/egl on Raspberry Pi 4

On 10/4/21 12:39 PM, Greg Wilson-Lindberg wrote: Hello list, I'm working on a Qt supplied boot2qt Yocto build currently based on Zeus that is running on a Raspberry Pi 4. I recently updated the qt version to 5.15.6 and Qt changed something in the Yocto configuration that they are using and

[yocto] virtual/egl on Raspberry Pi 4

Hello list, I'm working on a Qt supplied boot2qt Yocto build currently based on Zeus that is running on a Raspberry Pi 4. I recently updated the qt version to 5.15.6 and Qt changed something in the Yocto configuration that they are using and now one of the recipes that we use is failing saying

[yocto] Building a native package that includes tools + u-boot binaries

I am trying to create a first install package for our device, which would contain an install tool binary, and the required files to install. In our case, that would be >From imx-usb_loader recipe: imx_usb imx_usb.conf mx6_usb_rom.conf mx6_usb_sdp_spl.conf >From u-boot recipe: u-boot.img SPL

Re: [yocto] Meta-raspberrypi - how to configure device tree for MCP251x

can you check boot/config.txt and see fi your changes are there in your target ? On Mon, Oct 4, 2021 at 1:21 AM Chris Tapp wrote: > > Sorry, I meant to add that I have tried adding the following to local.conf: > > RPI_EXTRA_CONFIG = ' \n \ > dtparam=spi=on \n \ >

[yocto] [meta-security][PATCH] sssd: FIX QA error

ERROR: sssd-2.5.2-r0 do_package_qa: QA Issue: sssd rdepends on dbus-dev [dev-deps] ERROR: sssd-2.5.2-r0 do_package_qa: QA Issue: sssd rdepends on ding-libs-dev [dev-deps] Signed-off-by: Armin Kuster --- recipes-security/sssd/sssd_2.5.2.bb | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [yocto] Shared lib symlinks in target image

On Sun, 2021-10-03 at 01:55 +, Lijun Chen wrote: > Hi, > > When I build a yocto image, I added some packages into IMAGE_INSTALL, such as > boost, thrift, etc. I notice in the target OS image, the shared libs don't the > symlinks. But in the SDK image, the symlinks are there. For example, >

Re: [yocto] Shared lib symlinks in target image

Libraries have another symlink which looks something like libfoo.so.1 and 2 etc that is the one which should be used by apps On Mon, Oct 4, 2021 at 6:12 AM Lijun Chen wrote: > I have an app built in a different environment that has lower versioned > libs, such as boost. I was wondering if on the

Re: [yocto] Shared lib symlinks in target image

I have an app built in a different environment that has lower versioned libs, such as boost. I was wondering if on the target there are symlinks to those libs, whether the app can be run on a target that has newer libs without resbuild against a matched env. Seems that is not viable.

Re: [yocto] Meta-raspberrypi - how to configure device tree for MCP251x

Sorry, I meant to add that I have tried adding the following to local.conf: RPI_EXTRA_CONFIG = ' \n \ dtparam=spi=on \n \ dtoverlay=mcp2515-can0,oscillator=1600,interrupt=25 \n \ dtoverlay=mcp2515-can1,oscillator=1600,interrupt=23 \n \ ' However, this did not make any