https://wiki.yoctoproject.org/wiki/TipsAndTricks/Understanding_what_changed_(diffsigs_etc) On Tue, Feb 23, 2021 at 10:03 AM Monsees, Steven C (US)

<karthik.poduval@...> wrote: Because it's not a simple thing to solve (and there's a bugzilla around for it already, where the thoughts and issues are captured, but that one seems to have been

Hi, Please join us for the upcoming OpenEmbedded Happy Hour on February 24 for Asia/Pacific timezones @ 2100/9pm UTC (4pm

I am trying to understand the warnings/error as seen below… Building for zeus… Built kernel image clean updated my SSTATE_MIRRORS directory with the state_cache generated. Rebuilt my

Current Dev Position: YP 3.3 M3 development Next Deadline: 1st March 2021 YP 3.3 M3 build and YP 3.3 Feature Freeze Next Team Meetings: Bug Triage meeting Thursday Feb. 25th at 7:30am PDT

It looks like you are using the live option in hddimg image? Can you try adding "rootwait" to kernel parameters and see if that works? Not sure why it's not dropping to shell, but may be try adding

Hi, A kernel recipe will provide linux-libc-headers after a "make headers_install" call... So the SRC_URI of linux-libc-headers can be the same as from the linux kernel recipe, or linux kernel

Hi Mikko, Do you have an example on how you do that ? Do you bbapend the linux-libc-headers recipe file ? I have an application that uses dmabuf heap that potentially extends across multiple BSP's as

Yes, we're talking about the same thing :) A lot of yocto things don't work well if major changes happen and WORKDIR isn't completely cleaned in between. With various BSP layers things can be even

I mentioned that we remove that directory, and it does indeed solve a lot of problems. Not sure that it was clear from the original message, but whenever we get a random error on the first build

Hi, I know it's not the best or recommended approach, but I find it hard to avoid merging linux-libc-headers recipe with the actual kernel recipe that a distro is using. At least a static copy of

Hi, When both yocto update and your own changes are modifying the same recipes, then conflicts can occur. If builds are failing, then your environment is breaking something. It might even be the BSP

Hi All, This has not been reviewed yet and it is given since January 6th. Please review it and provide review comments if any as soon as possible to resolve this issue. Thanks & Regards, Milan Shah

Yocto Gatesgarth, using meta-intel to build core-image-minimal Intel D2700MUD mini-ITX mobo with D2700 Atom Ordinary USB 2.0 flash drive I followed the instructions in the meta-intel README, and had

Hi, We have a functioning image built for our device/platform based on Ti Processor SDK 04.03.00.05; at this point I'm trying to build an SDK for the image that I can distribute to other members of

RP, if you want to get this merged too that would be great. yifan

mostly changed the way to access request.GET also tested on python2.7 to be backward compatible Signed-off-by: Yi Fan Yu <yifan.yu@...> --- Post/parser.py | 2 +- Post/views.py | 14

Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.6.rc1 We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2.

Hi Khem and Bruce, I got the patch from raspberry pi github and it looked like it put the header into include/uapi/linux/dma-heap.h, for kernel 5.4 it doesn't look like there is a need for a Kbuild

<karthik.poduval@...> wrote: That's coming from the linux-libc-headers, your new upi header is not part of the libc-headers package, so it won't show up there. And no, it shouldn't be part of