From: Andrei Gherzan <andrei@gherzan.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Carles.SoleMendi@de.bosch.com, yocto@lists.yoctoproject.org
Subject: Re: [yocto] [meta-raspberrypi] Is Preempt-rt still supported in master / latest releases? #raspberrypi
Date: Mon, 23 Jan 2023 16:03:57 +0000 [thread overview]
Message-ID: <Y86v7Z+p68WpY13k@qwirkle> (raw)
In-Reply-To: <CANNYZj-yRKXP+eyEFavNthO6VmNfTnCbAbV3RnbwZq0iaT2siw@mail.gmail.com>
On Mon, Jan 23, 2023 at 11:47:59AM +0100, Alexander Kanavin wrote:
> meta-raspberrypi kernel comes from
> https://github.com/raspberrypi/linux and they stopped providing -rt
> options some time ago.
>
> Your options are to apply the -rt patchset to regular rpi kernel and
> enable needed options via custom .bbappend, or take linux-yocto-rt and
> see how far you get.
That would be correct. There is no support out of the box in the BSP layer and
I am not aware of any layers providing that. If we find a person who wants to
maintain a fork with the RT patches, I'm happy to bring it as an optional
kernel provider in the layer.
--
Andrei Gherzan
next prev parent reply other threads:[~2023-01-23 16:04 UTC|newest]
Thread overview: 15+ 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 [this message]
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
2023-03-06 18:53 ` 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=Y86v7Z+p68WpY13k@qwirkle \
--to=andrei@gherzan.com \
--cc=Carles.SoleMendi@de.bosch.com \
--cc=alex.kanavin@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.