From: Gyorgy Sarvari <skandigraun@gmail.com>
To: "חיים בכר" <haimbachar2008@gmail.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] How to set real time patch correctly? #honister
Date: Sat, 26 Oct 2024 16:23:10 +0200 [thread overview]
Message-ID: <d8d28f79-8b34-4309-8778-49bae8267cf8@gmail.com> (raw)
In-Reply-To: <CAOJpL53RCmNZY=dS+Wm14z=HqUbeNd9Qt0fJ6Oansy6mor8NXw@mail.gmail.com>
On 10/26/24 15:59, חיים בכר wrote:
> Hi and what if the recipe is linux-xlnx then set
> PREFFERED_PROVIDER_virtual/kernel = “linux-xlnx-rt”?
>
> By the way what the different between linux-yocto and linux-xlnx?
>
linux-yocto (and its -rt variant) is the default kernel coming with
Yocto. linux-xlnx comes from Xilinx, with their own modifications, and
looking at meta-xilinx layer, there doesn't seem to be a recipe with the
RT patch available.
If you are not using the default kernel, then possibly the simplest
would be to create a bbappend for your kernel recipe, where you add the
patch's uri to SRC_URI (assuming it applies cleanly on the vendor's
kernel still), e.g:
SRC_URILappend = "
https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.15/older/patch-5.15.36-rt41.patch.gz"
After fetching the source bitbake will extract the patch and apply it
automatically before compiling.
(If the patch doesn't apply on the xlnx kernel, then maybe Xilinx
support has some extra info on this? Adapting that patch could be a
non-trivial task)
next prev parent reply other threads:[~2024-10-26 14:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 11:26 How to set real time patch correctly? #honister Haimbach
2024-10-26 13:55 ` [yocto] " Gyorgy Sarvari
2024-10-26 13:59 ` חיים בכר
2024-10-26 14:23 ` Gyorgy Sarvari [this message]
2024-10-26 17:10 ` Haimbach
2024-10-27 20:01 ` Gyorgy Sarvari
2024-10-27 20:39 ` codusnocturnus
2024-10-28 7:53 ` Haimbach
2024-10-27 22:20 ` Bruce Ashfield
2024-10-27 22:49 ` codusnocturnus
2024-10-27 23:46 ` Bruce Ashfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8d28f79-8b34-4309-8778-49bae8267cf8@gmail.com \
--to=skandigraun@gmail.com \
--cc=haimbachar2008@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.