public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@nabladev.com>
To: jan.kiszka@siemens.com
Cc: Pavel Machek <pavel@nabladev.com>,
	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 18:18:25 +0100	[thread overview]
Message-ID: <aZ8u4fd1dcBZ88O5@duo.ucw.cz> (raw)
In-Reply-To: <4eb6eda3-2ceb-4f72-9bc7-f30a1974afe8@siemens.com>

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

      reply	other threads:[~2026-02-25 17:18 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   ` [cip-dev] " Pavel Machek
2026-02-25 11:47     ` Jan Kiszka
2026-02-25 17:18       ` Pavel Machek [this message]

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=aZ8u4fd1dcBZ88O5@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