Conversation
Signed-off-by: LosCrossos <165311345+loscrossos@users.noreply.github.com>
|
@johnnynunez does this PR partially obviate #45 ? |
11.0 is thor |
|
i think this PR and #45 do not collide that much. #45 does a lot of thinks and heavy refactoring. This PR is only about adding CUDA capabilities according to latest documentation from CTK: for 12.8: https://docs.nvidia.com/cuda/archive/12.8.0/cuda-features-archive/index.html
and 12.9:
@johnnynunez thor is afaik: 101 and not "110" :) 103 is GB200
https://docs.nvidia.com/cuda/pdf/CUDA_Toolkit_Release_Notes.pdf
Also upon inspection on #45: it seems you are adding support for Cuda Toolkit 13. but the latest official release is afaik 12.9.1 Also i think sm_110 does not exist in the official CUDATK documentation Also it seems #45 does not include support for Cuda 12.9? |
Hello, there is a confusion here. Why? CUDA 13 comes mid of July Jetson Orin will receive CUDA SBSA support Q1 2026 |
|
I dont think there is much of confusion: my PR is based only on official documentation for CUDAtk. Therefore i can not comment on unreleased or undocumented features. Do you have sources for that? it seems you guys have more insights into nvidia development. I would be very interested in new developments :) But the actual point is: our PRs "collide" by like 3 lines (where we both actually fully agree): 12.8 supports 100, 101, 120. Then my PR is about 12.9 which is not touched by #45 on the other side #45 is about CUDAtk 13, which is not touched by me and also that PR does a lot of refactoring and improvements which does not affect my PR at all. |
it is internal information, sorry, 10.1 will disappear |


this PR enabled full cuda support with the correct compute levels to leverage all kernels provided by the toolkit, CUDA 12.8 adds: 100, 101 and 120 (see https://docs.nvidia.com/cuda/archive/12.8.1/cuda-toolkit-release-notes/index.html ) and for CUDA 12.9 adds 103, 121 see https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html