Re: xf86-video-intel is broken and with MRs disables we can't fix it

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2025-02-07 23:25, Ville Syrjälä wrote:
> 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?

For the record, the build failure was some weird missing autotools
dependency causing a weird error. Redoing the test after `apt build-dep
xserver-xorg-video-intel` fixed the problem. Again, sorry for the wrong
email.

>>
>> 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@xxxxxxxxxxxxxxxxxxxxx
>> 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@xxxxxxxxxxxxxxx>
> AuthorDate: Sat Mar 18 15:45:44 2023 +0200
> Commit:     Ville Syrjälä <ville.syrjala@xxxxxxxxxxxxxxx>
> 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.
> 




[Index of Archives]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux