Open orowith2os opened 1 year ago
Not everything is upstream yet, so I want to keep this patch going until it is, at which point this can be removed and newer builds can just use the Wine upstream that contains the driver.
If I recall correctly Alexandros should be rebasing his wayland patches on top of what he has upstream already in this branch: https://gitlab.winehq.org/afrantzis/wine/-/tree/wayland?ref_type=heads
Currently part4 got merged, so we would have to wait for it to be rebased on that.
Not all is upstream already. So one would have to update the community patch every time upstream gets a patch in and the downstream was rebased.
@Riesi That branch hasn't been updated in over 3 months now though (so I'm doing my own rebases)
Is there any chance this can be rebased (ideally in some Proton-compatible way)? I've tried several ways myself, but I don't know enough about Wine/Proton's internals to make it work.
I did manage to get a normal Wine build working (based on the original wine-8.2 branch). In my testing, it improves the NVIDIA+Wayland experience a lot.
The full upstreaming is still a long ways off, and then some more time for it to trickle down to Proton.
@gnusenpai I'm not at home, and won't be until the end of the month, so if I do rebase these, it'll probably take a while (unless the original patch creator rebases this themselves, and I generate one).
For now, it's not the best workaround, but just use an Xorg session.
winewayland driver development's future is upstream - see https://github.com/wine-mirror/wine/commits/master/dlls/winewayland.drv So that part can be dropped as it's unlikely that repo will get updated anymore. The only possibly useful case would be to check and - if needed - rebase the patchset against Proton 8. But that's about it for winewayland :)