There's a lot that could be done.
The hipify and rocdbgapi packages could be migrated to unstable. The former is required to update rccl, while the latter is relatively unimportant until gdb takes it as a dependency.
If you wanted to update a few libraries to ROCm 6.1.3, I would suggest rocfft and hipfft, as they're straightforward and the issues preventing the creation of hipfft autopkgtests were fixed upstream in ROCm 6.0.2. The addition of hipfft autopkgtests would be beneficial for the Debian ROCm CI.
If you want to update a lot of packages, I would be interested in adding MI300 (gfx942) to the AMDGPU_TARGETS of all the ROCm mathlibs, as there was experimental support in ROCm 5.7 which I believe we could enable even if it wasn't fully supported until ROCm 6.0.
If you want to begin the update of the whole stack to ROCm 6.1.3 to enable proper support, that would be helpful too.
If you want to create a new ROCm package, the rocm-smi utility has been deprecated in favour of amd-smi [1]. The latter needs to be packaged. It's probably a small and simple package.
If you want to investigate higher-level libraries built on ROCm, I'm curious about cupy [2]. It provides GPU-accelerated numpy and scipy and all dependencies are available on unstable.
If you want to work with Debian Multimedia, I would be excited to have GPU rendering enabled in Blender [3].
Sincerely,
Cory Bloor
[1]:
https://github.com/ROCm/amdsmi[2]:
https://lists.debian.org/debian-science/2024/06/msg00033.html[3]:
https://bugs.debian.org/1021646