| 9 Jul 2024 |
 hacker1024 | * Yep, luckily Jetpack-NixOS has all the samples packaged | 06:49:06 |
| hacker1024 | Just needs some overlay weirdness to use CUDA from Nixpkgs now | 06:49:37 |
| hacker1024 | Speaking of which, is tensorrt supposed to work on aarch64? Because it's evaluating as both broken and unsupported
` nix-instantiate -I nixpkgs=channel:nixos-unstable '<nixpkgs>' --argstr localSystem aarch64-linux --arg config '{ cudaSupport = true; allowUnfree = true; }' -A cudaPackages.tensorrt` | 06:50:38 |
| hacker1024 | * Speaking of which, is tensorrt supposed to work on aarch64? Because it's evaluating as both broken and unsupported when running the following
`nix-instantiate -I nixpkgs=channel:nixos-unstable '<nixpkgs>' --argstr localSystem aarch64-linux --arg config '{ cudaSupport = true; allowUnfree = true; }' -A cudaPackages.tensorrt` | 06:50:57 |
 SomeoneSerge (matrix works sometimes) | Not sure, tensorrt isn't receiving enough love:) | 07:11:44 |
| SomeoneSerge (matrix works sometimes) | https://github.com/NixOS/nixpkgs/issues/323124 | 07:12:14 |
| SomeoneSerge (matrix works sometimes) | Jonas Chevalier hexa (UTC+1) a question about release-lib.nix: my impression is that supportedPlatforms is the conventional way to describe a "matrix" of jobs; for aarch64-linux, I'd like to define a matrix over individual capabilities because aarch64-linux mostly means embedded/jetson SBCs; currently this means importing nixpkgs with different config.cudaCapabilities values... any thoughts on how to express this in a not-too-ad-hoc way? | 18:07:33 |
