From: "Carles Sole" <Carles.SoleMendi@de.bosch.com>
To: yocto@lists.yoctoproject.org
Subject: Re: [meta-raspberrypi] Is Preempt-rt still supported in master / latest releases?
Date: Sun, 05 Feb 2023 23:38:05 -0800 [thread overview]
Message-ID: <32073.1675669085179357281@lists.yoctoproject.org> (raw)
In-Reply-To: <CABKMkP+Z=3FSNGxbcVbrEtw2wvdJ07EbDtFSiW+tCUzn-iFGDg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
Hi Joel,
thanks for creating the issue.
Does the solution from Aleksandr work for you with raspberrypi4-64? The funny thing is for me it doesn't. As I mentioned above if I use his solution:
for MACHINE = "raspberrypi4-64" in local.conf, the .config file has following configs:
CONFIG_HAVE_PREEMPT_LAZY=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
If in the local.conf I replace the machine to MACHINE = "raspberrypi4" and I bitbake again, the .config file looks as follow:
CONFIG_HAVE_PREEMPT_LAZY=y
CONFIG_PREEMPT_LAZY=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT_COUNT=y
CONFIG_PREEMPTION=y
Meaning when the machine is set to raspberrypi4-64 and CONFIG_PREEMPT_RT is requested via the .cfg file in the file .config in work directory CONFIG_PREEMPT_NONE=y is getting set. Whereas with Machine raspberrypi4 it works as expected.
[-- Attachment #2: Type: text/html, Size: 1082 bytes --]
next prev parent reply other threads:[~2023-02-06 7:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 9:57 [meta-raspberrypi] Is Preempt-rt still supported in master / latest releases? #raspberrypi Carles Sole
2023-01-23 10:47 ` [yocto] " Alexander Kanavin
2023-01-23 16:03 ` Andrei Gherzan
2023-01-25 12:49 ` [meta-raspberrypi] Is Preempt-rt still supported in master / latest releases? Carles Sole
2023-01-30 22:59 ` [yocto] " Lukasz Majewski
2023-01-31 6:57 ` Kuzemko Aleksandr
2023-01-31 20:43 ` Carles Sole
2023-02-01 13:26 ` [yocto] " Joel Winarske
2023-02-02 10:24 ` Carles Sole
2023-02-03 0:00 ` [yocto] " Joel Winarske
2023-02-03 7:18 ` Carles Sole
2023-02-03 13:18 ` [yocto] " Joel Winarske
[not found] ` <174052FEBB286E1B.4349@lists.yoctoproject.org>
2023-02-03 16:40 ` Joel Winarske
2023-02-06 7:38 ` Carles Sole [this message]
2023-03-06 18:53 ` Carles Sole
-- strict thread matches above, loose matches on Subject: below --
2023-01-19 13:00 Carles Sole
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=32073.1675669085179357281@lists.yoctoproject.org \
--to=carles.solemendi@de.bosch.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.