Skip to content
New issue

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

linux-testing-drm-next: init at 5.5-2019-11-27 #74717

Closed
wants to merge 1 commit into from

Conversation

Enzime
Copy link
Member

@Enzime Enzime commented Nov 30, 2019

Motivation for this change

drm-next is a Linux kernel branch that contains the newest changes for graphics drivers and would be especially useful for people with newer graphics cards and want the most up to date drivers.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.
Notify maintainers

cc @NeQuissimus

@Mic92
Copy link
Member

Mic92 commented Nov 30, 2019

How do you intend to keep this up to date? cc @NeQuissimus

@Mic92
Copy link
Member

Mic92 commented Nov 30, 2019

I am not a fan of having many testing kernels in nixpkgs. When testing new out-of-tree kernel modules with nix-review, I constantly get breakages from linux-testing.nix, linux-libre.nix. I honestly don't want to have yet another kernel target that breaks...

@Enzime Enzime changed the title linux-testing-drm-next: init at 5.5-2019-11-22 linux-testing-drm-next: init at 5.5-2019-11-27 Nov 30, 2019
@Enzime
Copy link
Member Author

Enzime commented Nov 30, 2019

How do you intend to keep this up to date? cc @NeQuissimus

I was thinking manually however having some automated way would be a good idea, I was just planning to follow new tags @ https://cgit.freedesktop.org/drm/drm/

I am not a fan of having many testing kernels in nixpkgs. When testing new out-of-tree kernel modules with nix-review, I constantly get breakages from linux-testing.nix, linux-libre.nix. I honestly don't want to have yet another kernel target that breaks...

I'm not too familiar with nix-review, I just think this might be a useful kernel for people, maybe if there's somewhere else to put it that's outside of nixpkgs that wouldn't be too hard to find/too obscure.

@NeQuissimus
Copy link
Member

hmmm, to be honest, I am with @Mic92 here.
Could you just keep this derivation local? Following linux-next would be quite the maintenance investment.

@Mic92
Copy link
Member

Mic92 commented Dec 1, 2019

I created https://github.com/nix-community/NUR at some point for people to share their packages. Discoverability could be improved, but I have not yet managed to automate updating the search index. However you could maybe put a link on the wiki for people to find it.

@Enzime
Copy link
Member Author

Enzime commented Dec 2, 2019

Seeing as people don't seem to be too interested, I'll look into moving it onto the NUR or just keeping it locally.

Does anyone have any good suggestions on some good ways of keeping this derivation locally?

@Enzime Enzime closed this Dec 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants