From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Povilas Kanapickas <povilas@radix.lt>
Cc: "xorg-devel@lists.x.org" <xorg-devel@lists.x.org>,
intel-gfx@lists.freedesktop.org, chris@chris-wilson.co.uk
Subject: Re: xf86-video-intel is broken and with MRs disables we can't fix it
Date: Fri, 7 Feb 2025 23:25:07 +0200 [thread overview]
Message-ID: <Z6Z6My8FcaLaLPu0@intel.com> (raw)
In-Reply-To: <1e5b5275-d194-4af0-8927-f5b93416a407@radix.lt>
On Fri, Feb 07, 2025 at 08:57:34PM +0200, Povilas Kanapickas wrote:
> Hi,
>
> xf86-video-intel driver is currently cannot be compiled with released
> versions of X server. Simple reproduction steps: create Debian Bookworm
> container, download module sources and all required dependencies and try
> to build.
Builds fine on my Gentoo boxes here. What are the actual issues
you are seeing?
>
> Debian Bookworm is pretty much the least exciting configuration
> possible. And the fact that xf86-video-intel cannot be compiled there is
> not good.
>
> For almost any other driver this is not a problem, because it is
> possible to create a merge request on gitlab.freedesktop.org. Eventually
> simple maintenance and build-related merge requests are merged. However
> in the case of Intel driver, merge requests are disabled and the
> recommended way to submit patches is via intel-gfx@lists.freedesktop.org
> mailing list. Unfortunately, patches submitted so far are ignored there.
I've not seen any patches on the list. Care to point them out?
>
> Given that the last commit to xf86-video-intel was 22 months ago, I
> suspect there's little interest from Intel to spend time maintaining the
> project.
You must be looking at some stale repo. My last commit was
commit ce811e78882d9f31636351dfe65351f4ded52c74
Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
AuthorDate: Sat Mar 18 15:45:44 2023 +0200
Commit: Ville Syrjälä <ville.syrjala@linux.intel.com>
CommitDate: Tue May 7 00:32:24 2024 +0300
>
> What do you think about opening up merge requests on the repository so
> that at least the driver can be brought back to compilable state? Does
> anyone have other ideas how the current situation could be resolved?
I wouldn't want to deal with mrs for any high volume stuff, but
since this only gets the occasional fix I guess it could work.
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2025-02-07 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 18:57 xf86-video-intel is broken and with MRs disables we can't fix it Povilas Kanapickas
2025-02-07 21:25 ` Ville Syrjälä [this message]
2025-02-07 21:56 ` Povilas Kanapickas
2025-02-10 19:01 ` Povilas Kanapickas
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=Z6Z6My8FcaLaLPu0@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=povilas@radix.lt \
--cc=xorg-devel@lists.x.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.