On Sun, 2024-09-15 at 21:27 +0200, Petter L. H. Eide wrote:
> My understanding is that it is possible to manually trigger the binding (by
> adding eg. i915.force_probe=!56a0 xe.force_probe=56a0 as kernel
> parameters). Would the fact that its does not bind to hardware by default
> not mitigate the
My understanding is that it is possible to manually trigger the binding (by
adding eg. i915.force_probe=!56a0 xe.force_probe=56a0 as kernel
parameters). Would the fact that its does not bind to hardware by default
not mitigate the experimentalness somewhat?
In case you are not aware, there are oth
Control: notfound -1 6.10.9
Control: found -1 6.10.9-1
On Thu, 2024-09-12 at 21:35 +0200, Petter L. H. Eide wrote:
> Package: src:linux
> Version: 6.10.9
> Severity: wishlist
>
> Dear Maintainer,
>
> Since kernel 6.8, the xe driver for intel GPUs has been available as a kernel
> module. Please
Processing control commands:
> notfound -1 6.10.9
Bug #1081563 [src:linux] Please consider adding the new Xe Graphics driver for
Intel GPUs
The source 'linux' and version '6.10.9' do not appear to match any binary
packages
Ignoring request to alter found versions of bug #1081563 to the same valu
Package: src:linux
Version: 6.10.9
Severity: wishlist
Dear Maintainer,
Since kernel 6.8, the xe driver for intel GPUs has been available as a
kernel module. Please consider including this by enabling CONFIG_DRM_XE.
See following references for more information:
- https://docs.kernel.org/next
5 matches
Mail list logo
