Hi Trevor, Would sed -i "s/#define RK3399_BAUDRATE\s\+.*/#define RK3399_BAUDRATE plep/" ${S}/plat/rockchip/rk3399/rk3399_def.h work for you? This makes sure that only RK3399_BAUDRATE definition will

Hello everybody, I come today to try to solve my problem. I am building a bsp and sdk for a raspberry pi (MACHINE = raspberrypi4-64) in the form of a compute module. I'm trying to compile this app:

Hi Team, I am facing a problem libsdl2 while building the core-image-base. Can anybody know this please suggest me. NOTE: Resolving any missing task queue dependencies ERROR: Nothing

I think using qemux86-64 might be your best bet, its fairly automated with runqemu script all you would need to do is package up the gtests as ptest package with a runner

We are building our software with a Yocto SDK we created against our imx8m board. We would like to be able to execute unit tests (C++ tests written in Google Test) quickly without having to copy our

Am I correct in thinking a v2 is coming (or did it get swallowed up by my mail client)? Otherwise, I can just fixup your v2 and apply it if you wish? > >

Applied to meta-rockchip, master.

Hi Quentin/Khem, I apologize for not reviewing this patch in a timely manner; I'm sorry for the frustration it caused. Would this have been solved by (me) creating a honister branch? I

All, YP M+ or high bugs which moved to a new milestone in WW50 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 10693 Add a testcase for multilib eSDK on

All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.purdie@... 4 jon.mason@... 1 randy.macleod@... 1 Grand Total 6 Thanks, Stephen K.

All, Below is the list as of top 46 bug owners as of the end of WW50 of who have open medium or higher bugs and enhancements against YP 3.5. There are 94 possible work days left until the final

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

I agree with you that broken is not good as it was for sometime, but now with the latest supported release in 3.4 series ( which is 3.4.1) things should be good.

Hi José, The issue is that you masked a recipe whose packages are required by other recipes packages. Find where the RDEPENDS is set for this recipe package and remove the package which depends on

Hi Léon, Did you check that your kernel actually supports squashfs as rootfs? There is a Kconfig option for it IIRC. Since it's an image feature, it's not going to impact anything outside of the

Hi Khem, We need this patch for honister 3.4 but what I meant is that even though it's not needed for honister >= 3.4.1, I'm still interested in what the policy should be. Especially what we should

Do we still need this patch ? I think now that dot release is out it’s less of a problem. Version specific patching will set a different preset for the layer to carry unexcercised patches

Dear all, Currently I have created an image which upon boot mounts my rootfs as readonly in an overlay with my data partition. I set out to change the FS type of my rootfs to something that is

Hi all. I have added a recipe to BBMASK to skip the processing of this recipe for now, but when I try to compile the image i getERROR: Nothing RPROVIDES <recipe> error. It’s like I should say

ping