bajspulver

joined 2 months ago
11
submitted 2 months ago* (last edited 2 months ago) by bajspulver@lemmy.world to c/nix@programming.dev
 

Maaaybe a stupid question as it might just be the same thing done differently. I'm not bright enough to understand the differences.

hardware.graphics was recently introduced which replaced hardware.opengl. Now, I've got my amdvlk, libva and such configured via hardware.graphics โ€” recently I came across hardware.amdgpu which offers a bunch of options.

Should one combine, use one or the other, or does it make any difference at all?

hardware.amdgpu.opencl.enable
hardware.amdgpu.legacySupport.enable
hardware.amdgpu.initrd.enable
hardware.amdgpu.amdvlk.supportExperimental.enable
hardware.amdgpu.amdvlk.support32Bit.package
hardware.amdgpu.amdvlk.support32Bit.enable
hardware.amdgpu.amdvlk.settings
hardware.amdgpu.amdvlk.package
hardware.amdgpu.amdvlk.enable
hardware.graphics.extraPackages32
hardware.graphics.extraPackages
hardware.graphics.enable32Bit
hardware.graphics.enable

That is, are these two examples the same for all intents and purposes or do either bring anything else?

hardware.amdgpu.amdvlk = {
  enable = true;
  support32Bit.enable = true;
};

# VS.

hardware.graphics = {
  enable = true;
  enable32Bit = true;
  extraPackages = with pkgs; [
    amdvlk
  ];
  extraPackages32 = with pkgs; [
    driversi686Linux.amdvlk
  ];
};