We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There doesn't seem to be a consensus on whether Xe should be used on older platforms, like Tiger Lake
https://docs.kernel.org/next/gpu/rfc/xe.html#xe-platforms
The common/gpu/intel/tiger-lake/default.nix module enables Xe:
common/gpu/intel/tiger-lake/default.nix
nixos-hardware/common/gpu/intel/tiger-lake/default.nix
Line 5 in b12e314
But Xe won't be loaded unless something like this is configured:
boot.extraModprobeConfig = '' options xe force_probe=9a60 options i915 force_probe=!9a60 '';
The jury is still out on Xe stability, some call it trash, others call it perfect
So, should Xe be force_probe'd for Tiger Lake in nixos-hardware? or should it be avoided?
force_probe
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There doesn't seem to be a consensus on whether Xe should be used on older platforms, like Tiger Lake
https://docs.kernel.org/next/gpu/rfc/xe.html#xe-platforms
The
common/gpu/intel/tiger-lake/default.nix
module enables Xe:nixos-hardware/common/gpu/intel/tiger-lake/default.nix
Line 5 in b12e314
But Xe won't be loaded unless something like this is configured:
The jury is still out on Xe stability, some call it trash, others call it perfect
So, should Xe be
force_probe
'd for Tiger Lake in nixos-hardware? or should it be avoided?The text was updated successfully, but these errors were encountered: