On 12/12/22 10:30, Alistair Leslie-Hughes wrote:
Hi Alois,
On 11/12/22 22:23, Alois Schlögl wrote:
Dear Alistair,
thanks for the information. I see that the nvcuda patches are still disabled, that means cuda applications (e.g. cuda-z, and warpem) do not run anymore on wine-staging. In the announcement for wine-staging 7 22 you wrote:
The number is quiet lower compared to the previous version due to the disabling of the nvidia dll patchesets.
which broke the cuda support in wine-staging. I'm wondering what the reason for disabling these patches is? Is it to much work to maintain, and rebase these? Or is there a technical reason ? Most importantly, can we expect to have cuda supported again anytime soon ?
The basic, is that the nvcuda and the other nv dll's need to be converted to the unix function call syntax. Considering, the first patch that implement the nvcuda has around 245 functions, that is a huge amount of effort (Time) to change over.
We are still trying to workout, if we will convert it over. This dll and the other nv* at present, are never going to be upstreamed (at this stage).
There has been some talk that these nv*/amd_ags* dlls should be external project(s) and be maintained there. These are vendor specific DLL's after all, so windows doesn't have them by default. So technically wine shouldn't either. There is already a project for nvapi but that wont help in this case.
On the other side of things, some games and applications expect them to be there in certain scenarios. There is a balance that need to be found, which is the hard part.
FWIW games usually try to load them based on GPU vendor ID, maybe upstream Wine should hide it and use a Wine-specific ID to solve that.