From: Pavel Machek <pavel@nabladev.com>
To: jan.kiszka@siemens.com
Cc: Stephen Ecker <stephenecker240@gmail.com>, cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] i915 in 6.12 kernel
Date: Wed, 25 Feb 2026 10:54:23 +0100 [thread overview]
Message-ID: <aZ7Gz00emqLIThnm@duo.ucw.cz> (raw)
In-Reply-To: <9927e980-b0d0-43a0-913c-cff2bda757e3@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Hi!
> > Has anyone been able to apply the patches for the i915 module in 6.12
> > with RT? It was working ok in 6.11 when it RT was still an out-of-tree
> > patch
>
> You can pick them up from
> https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git/log/?h=v6.12-rt-rebase,
> they should apply.
>
> But CIP decided to maintain only a single tree with 6.12, and that means
> that we can only accept backports from newer kernels. Unfortunately, the
> i915 patches are still not ready for being proposed upstream. I'm not
> into their details, you may ask for more details on the linux-rt-users list.
Yes, applying the patches should be relatively easy.
Impression from RT meetings was that cleaning them up so they are of
suitable quality for the merge may be more of a challenge. Suggestion
would be to avoid i915 hardware if you care about realtime and
long-term maintenance.
Best regards,
Pavel
--
In cooperation with Nabla.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-02-25 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 18:39 i915 in 6.12 kernel Stephen Ecker
2026-02-24 21:32 ` Jan Kiszka
2026-02-25 9:54 ` Pavel Machek [this message]
2026-02-25 11:47 ` [cip-dev] " Jan Kiszka
2026-02-25 17:18 ` Pavel Machek
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=aZ7Gz00emqLIThnm@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=stephenecker240@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox