Yeah, that’s understandable; there’s probably a lot a proprietary stuff in the cuda sdk / driver.
sonymegadrive
joined 1 year ago
If/when NVK becomes the defacto driver for nv GPUs, what would it mean for cuda?
I absolutely plan to support team red/blue GPUs. I just don’t have access to the h/w right now
The pfp is goofy af. It stays 😂
Just by “eyeballing” the two, there’s very little, if any difference on my setup.
Haha. There’s no Wayland support… yet. Check out gpu-screen-recorder for a very similar project with Wayland support
Thank you for your kind words!
I haven’t made the jump to Wayland yet. I basically live in the terminal (when I’m not playing games!) so haven’t been in any rush. I definitely want to support Wayland going forward because it seems everyone has switched but me!
I’d be surprised if it doesn’t do something similar. I haven’t used OBS so I can’t really comment to it’s performance
That means cryptographic keys under one government’s control could be used to intercept HTTPS communication
Could someone smarter than me explain how this would be possible? Wouldn’t the browser still be able to enforce privacy between the client and origin? Or is it the case that certificates issued by these CAs could in theory only support weaker cyphers?
Edit: Some really useful explanations. Thank you!
Does this compile with -Wall -Werror? (might not be an option if your dependencies’ headers contain warnings)
Looks like it may be embedded code for a SoC or similar. The only things I can think of is that the tool chain you’re using maybe non-standard… or you’re invoking the dreaded Undefined Behaviour somewhere :(
Are you personally working on NVK? Terrific work if you are BTW! This is really positive progress