i915 in 6.12 kernel

i915 in 6.12 kernel

[Stephen Ecker]

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

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

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

Re: i915 in 6.12 kernel

[Jan Kiszka]

On 24.02.26 19:39, Stephen Ecker wrote:
> 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.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

Re: [cip-dev] i915 in 6.12 kernel

[Pavel Machek]

[-- 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 --]

Re: [cip-dev] i915 in 6.12 kernel

[Jan Kiszka]

On 25.02.26 10:54, Pavel Machek wrote:
> 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.

For some (or all) newer Intel SoCs, the Xe driver seems to be the
alternative that does not need downstream patches. I do not fully
understand if it is the driver for current and future SoCs or if there
is only partial overlap. Anyway, trying it out if it claims to support a
given platform would make a lot of sense.

Other than that, it seems the discussion in [1] didn't lead to things
moving forward for the i915 yet. Maybe time to ask again, also because
of what may happen once distros take the same path as CIP did (see Ben's
opening of the thread).

Jan

[1]
https://lore.kernel.org/linux-rt-users/2d4a5031-307d-4f29-8875-13b8b599b220@linux.intel.com/T/#m5155ecf06d57ea0bc4a71e1583b250abff6cf209
-- 
Siemens AG, Foundational Technologies
Linux Expert Center

Re: [cip-dev] i915 in 6.12 kernel

[Pavel Machek]

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

Hi!

> >> 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.
> 
> For some (or all) newer Intel SoCs, the Xe driver seems to be the
> alternative that does not need downstream patches. I do not fully
> understand if it is the driver for current and future SoCs or if there
> is only partial overlap. Anyway, trying it out if it claims to support a
> given platform would make a lot of sense.

According to chatgpt, anything Tiger lake and newer should be
supported by i915 and Xe drivers. 

Best regards,
							Pavel
-- 
In cooperation with Nabla.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]