RE: [yocto] preempt-rt

["Monsees, Steven C (US)" <steven.monsees@baesystems.com>]

[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]

Thanks…


From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf Of codusnocturnus via lists.yoctoproject.org
Sent: Wednesday, November 3, 2021 9:25 AM
To: yocto@lists.yoctoproject.org
Subject: Re: [yocto] preempt-rt

External Email Alert

This email has been sent from an account outside of the BAE Systems network.
Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros.  For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.




‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, November 3rd, 2021 at 5:43 AM, Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@lists.yoctoproject.org<mailto:steven.monsees=baesystems.com@lists.yoctoproject.org>> wrote:




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 applies the patch, doesn’t even have to be arm based… just looking for baseline I might use to carve out support for my platform.

There are a few details to sort out (like finding a patch compatible with the kernel recipe you want to use, or a compromise of the two), but basically a kernel .bbappend with the following will suffice to just patch the kernel.
FILES_EXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI_append = " https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.12/patch-5.12-rc3-rt3.patch.gz"

After that, you need a configuration fragment to enable PREEMPT-RT in the build.
CONFIG_PREEMPT_RT=y




Thanks,

Steve
Sent with ProtonMail<https://protonmail.com/> Secure Email.




[-- Attachment #2: Type: text/html, Size: 7360 bytes --]