Compute Shader Support Patches For NVIDIA Fermi On Nouveau

[phoronix]

Phoronix: Compute Shader Support Patches For NVIDIA Fermi On Nouveau

Samuel Pitoiset has published a set of twelve patches for implementing compute shaders support within the Nouveau NVC0 Gallium3D driver for the GeForce 400/500 "Fermi" graphics processors...

http://www.phoronix.com/scan.php?page=news_item&px=Nouveau-Fermi-Compute-Shader

[rabcor]

Wish I could make use of that, but my 550-Ti is freezing and crashing on nouveau on the latest kernels (don't know how far back it started, most likely somewhere in 4.x) works fine on proprietary drivers.

[SethDusek]

Hi Michael, can you cover this patch? https://lists.x.org/archives/xorg-de...ry/048677.html

Its from a nvidia dev and it fixes frame tearing on nvidia optimus by adding proper synchronization to xorg

[rabcor]

That is indeed something that should be known.

[Nightbane112]

Hi Michael, can you cover this patch? https://lists.x.org/archives/xorg-de...ry/048677.html

Its from a nvidia dev and it fixes frame tearing on nvidia optimus by adding proper synchronization to xorg

In addition, you could also the following link for reference : https://devtalk.nvidia.com/default/t...set=53#4799068

Hey everybody,

Thanks so much for following my work so closely! It means a lot to see you so excited about the changes.

As you may know, I recently sent out v3 of my upstream X patches: http://lists.x.org/archives/xorg-dev...ry/048677.html . It's hard to say how many revisions it will take before they are finally accepted, but hopefully it will be soon.

Once the pieces land in their respective mainlines, and we release a driver to take advantage of it, I'll post here with a recipe for what versions of what software components are needed, if people want to try it out before the bits propagate to their distros.

[Nightbane112]

Hi Michael, can you cover this patch? https://lists.x.org/archives/xorg-de...ry/048677.html

Its from a nvidia dev and it fixes frame tearing on nvidia optimus by adding proper synchronization to xorg

In addition, you could add the following link for reference too : https://devtalk.nvidia.com/default/t...set=53#4799068

Hey everybody,

Thanks so much for following my work so closely! It means a lot to see you so excited about the changes.

As you may know, I recently sent out v3 of my upstream X patches: http://lists.x.org/archives/xorg-dev...ry/048677.html . It's hard to say how many revisions it will take before they are finally accepted, but hopefully it will be soon.

Once the pieces land in their respective mainlines, and we release a driver to take advantage of it, I'll post here with a recipe for what versions of what software components are needed, if people want to try it out before the bits propagate to their distros.

[Adriannho]

Hi Michael, can you cover this patch? https://lists.x.org/archives/xorg-de...ry/048677.html

Its from a nvidia dev and it fixes frame tearing on nvidia optimus by adding proper synchronization to xorg

Now this is a real piece of news here. Wonder if next release of the proprietary nvidia driver will finally give proper optimus support or at least allow manually turnining the discrete card on/of (via DRI_PRIME).

I would like to point out that these patches are only for xorg, nothing about wayland. Does anybody know if PRIME double buffering is available on wayland or not? Does wayland even have sth similar to xrand?

[rob11311]

I would like to point out that these patches are only for xorg, nothing about wayland. Does anybody know if PRIME double buffering is available on wayland or not? Does wayland even have sth similar to xrand?

From http://wayland.freedesktop.org/faq.html : What is the drawing API?

"Whatever you want it to be, honey". Wayland doesn't render on behalf of the clients, it expects the clients to use whatever means they prefer to render into a shareable buffer.

More info at https://en.wikipedia.org/wiki/Waylan...er_protocol%29

There's more info on how near Wayland is for desktop readiness at https://www.phoronix.com/scan.php?pa...Status-January , I think for Nvidia binary blob drivers there's an issue that they don't support KMS

[SethDusek]

From http://wayland.freedesktop.org/faq.html : What is the drawing API?

"Whatever you want it to be, honey". Wayland doesn't render on behalf of the clients, it expects the clients to use whatever means they prefer to render into a shareable buffer.

More info at https://en.wikipedia.org/wiki/Waylan...er_protocol%29

There's more info on how near Wayland is for desktop readiness at https://www.phoronix.com/scan.php?pa...Status-January , I think for Nvidia binary blob drivers there's an issue that they don't support KMS

The unfortunate thing about wayland rendering (I asked some wayland guys) is that the client gets to decide which gpu to use, not the compositor. One solution could be providing one single

[blackout23]

Wish I could make use of that, but my 550-Ti is freezing and crashing on nouveau on the latest kernels (don't know how far back it started, most likely somewhere in 4.x) works fine on proprietary drivers.

You probably need to use the proprietary firmware extracted from the NVIDIA driver with your 550Ti on nouveau. On Arch you can install: https://aur.archlinux.org/packages/nouveau-fw/
And then tell nouveau to load the external firmware.