On Wed, Oct 27, 2021 at 10:04 AM Jason Andryuk via lists.yoctoproject.org <jandryuk=gmail.com@...> wrote: Ping? I'd like to unbreak meta-selinux dunfell. Other branches may also

Hello Steve, Depends, no mainline kernel? Vendor kernel? Can you share the machine name? Might be supported already in a layer with -rt. Regards, Leon-- -- Leon Woestenberg leon@... T: +31 40 711

I have a platform based off a aarm64 Xilinx based kernel, which is not a compliant mainline kernel… so, I will need to go the preemp-rt patch route. Can you supply an example Yocto recipe that

This, I think: http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next&id=164bb5e9287497b492f21985dd1a8d85e1a4ed23 Alex

Thanks. Can you provide links to these patches? I have no choice in using rocko. Note that the failure was in the do_packagedata task, where it is issuing a 'git -c core.fsyncobjectfiles=0

There are patches in master-next for this. You can backport them, but you really shouldn't be using rocko. Alex

My yocto builds started failing today (November 2, 2021) due to this (https://github.blog/2021-09-01-improving-git-protocol-security-github/#no-more-unauthenticated-git) issue.  Is there a fix for

Right, you can either build linux-yocto-rt or the Intel version with linux-intel-rt. linux-intel tree might have some platform specific patches that have either been backported or not upstreamed

And adding to that, besides the Yocto maintained kernel, meta-intel has it's own kernel GIT repo/branch for the kernel and -rt kernel maintained by Intel. (There might be some overlap in the

Correct. The rt patches are already integrated on the branches that that recipe will build out of the linux-yocto repository. Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness

Is it true that no patch work is required if out under …/poky/meta/recipes-kernel, there exists a yocto-linux-rt_##.##.bb recipe that matches your kernel release?, and that it will build the full

Current Dev Position: YP 3.5 M1 Next Deadline: 6th Dec. 2021 YP 3.5 M1 build Next Team Meetings: Bug Triage meeting Thursday Nov. 4th at 7:30am PDT

I will check... Would you have an example of a recipe that shows how to apply the rt path ? Thanks, Steve

Hello Steve, I have been running the PREEMPT_RT for Intel platforms for a few releases, I remember it fetched sources from a GIT branch for -rt (PREEMPT_RT). So it does not need to apply separate

I have an Intel based platform, and was looking to implement preempt-rt on it to test. For Intel, the meta-intel component recipe appears to supports “linux-intel-rt”, and I can build my intel

Hi Vishal, It looks like there is some problem with `u-boot-fw-utils` compilation. Are you using U-Boot in your system? Which target do you try to build? As you can

Signed-off-by: Naveen Saini <naveen.kumar.saini@...> --- README.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.txt b/README.txt index 5a0ccc7..9889b01

at one point, I had ppc64le working as SDKMACHINE target as well.

Not quite true, aarch64 is supported and tested as an SDKMACHINE value. Right, this sounds like MACHINE is wanted for raspberrypi. Cheers, Richard

(re-adding list as I messed up) Am Mo., 1. Nov. 2021 um 21:45 Uhr schrieb jchludzinski <jchludzinski@...>: MACHINE = "raspberrypi3" (for example, pick your specific one