Announcement

Collapse
No announcement yet.

NVIDIA 334.16 Beta Supports 64-bit EGL / OpenGL ES

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • NVIDIA 334.16 Beta Supports 64-bit EGL / OpenGL ES

    Phoronix: NVIDIA 334.16 Beta Supports 64-bit EGL / OpenGL ES

    NVIDIA announced their first public Linux graphics driver beta in the 334.xx series today and with it comes a splendid number of changes...

    http://www.phoronix.com/vr.php?view=MTU5NjI

  • #2
    Glad to see this finally get released. 2014, the year of Wayland?

    Comment


    • #3
      ......EGL support is critical in eventually having the NVIDIA driver support Wayland and Mir.....
      Hi
      Why 'eventually'? EGL isn't sufficient to support Wayland?

      Comment


      • #4
        Originally posted by sp82 View Post
        Hi
        Why 'eventually'? EGL isn't sufficient to support Wayland?
        You need to hide some specific way to connect the client to the server.
        For example in Mesa, the server advertises a wayland extension, which the client (internally, in Mesa) uses to get which device to use, and let the compositor know it buffers.

        And when you have finished rendering, you need some platform specific code to tell the server you have finished rendering.

        Nvidia tries (see the XDC talk) to have some EGL abstraction to connect the client and server a platform independant way, but it hasn't convinced up to now.

        Comment


        • #5
          what about kernel 3.13?

          what about kernel 3.13? it finally works without patchs and problems?

          Comment


          • #6
            Originally posted by Andrecorreia View Post
            what about kernel 3.13? it finally works without patchs and problems?
            No, it still doesn't support 3.13...

            Comment


            • #7
              wtf?!

              Originally posted by AnAkIn View Post
              No, it still doesn't support 3.13...

              the real important thing not work, even fglrx work...

              Comment


              • #8
                Originally posted by mannerov View Post
                You need to hide some specific way to connect the client to the server.
                For example in Mesa, the server advertises a wayland extension, which the client (internally, in Mesa) uses to get which device to use, and let the compositor know it buffers.

                And when you have finished rendering, you need some platform specific code to tell the server you have finished rendering.

                Nvidia tries (see the XDC talk) to have some EGL abstraction to connect the client and server a platform independant way, but it hasn't convinced up to now.
                also KMS

                Comment


                • #9
                  Originally posted by gens View Post
                  also KMS
                  IIRC KMS could be replaced with something completely vendor specific if necessary but would have to implemented in the compositor.

                  Anyways in the Wayland docs this is the relevant page:
                  http://wayland.freedesktop.org/docs/..._enabling.html

                  Comment


                  • #10
                    Originally posted by gens View Post
                    also KMS
                    Its my understanding that the proprietary drivers implement their own KMS. What is required exactly from in-kernel KMS that the binary blob doesn't do?

                    Comment


                    • #11
                      Originally posted by computerquip View Post
                      Its my understanding that the proprietary drivers implement their own KMS. What is required exactly from in-kernel KMS that the binary blob doesn't do?
                      haven't really gone that deep
                      it's a different API afaik from the kernels KMS

                      Comment


                      • #12
                        Originally posted by gens View Post
                        haven't really gone that deep
                        it's a different API afaik from the kernels KMS
                        Wayland doesn't depend on KMS. That's a popular myth.

                        I wondered in the past few days when they'd release a new beta driver. It's clear that they are working to get their drivers ready for Wayland and Mir with EGL. What will be interesting is if they implement XWayland support. From what I know the xf86-video-* DDXs all have their own XWayland patches so the closed drivers would need them aswell I guess. It would probably not be that hard for NVIDIA but, when there isn't even a version of Xwayland that is shipping with X.Org. I think they will only start working towards that once X11 1.16 ships with XWayland hopefully.

                        There seems to be a patch for 3.13 support.

                        https://projects.archlinux.org/svnto...s/nvidia-304xx
                        https://projects.archlinux.org/svnto...ackages/nvidia

                        Arch Linux has it built into the driver packages in [testing] which holds the 3.13 kernel.
                        Last edited by blackout23; 02-07-2014, 05:30 PM.

                        Comment


                        • #13
                          Originally posted by blackout23 View Post
                          Wayland doesn't depend on KMS. That's a popular myth.

                          I wondered in the past few days when they'd release a new beta driver. It's clear that they are working to get their drivers ready for Wayland and Mir with EGL. What will be interesting is if they implement XWayland support. From what I know the xf86-video-* DDXs all have their own XWayland patches so the closed drivers would need them aswell I guess. It would probably not be that hard for NVIDIA but, when there isn't even a version of Xwayland that is shipping with X.Org. I think they will only start working towards that once X11 1.16 ships with XWayland hopefully.

                          There seems to be a patch for 3.13 support.
                          mmm
                          good to know


                          if that patch breaks with multiple graphics card people can try
                          https://devtalk.nvidia.com/default/t...fset=2#4114295

                          Comment


                          • #14
                            Added 64-bit EGL and OpenGL ES libraries to 64-bit driver prackages
                            What is a prackage? A prank package?

                            Comment


                            • #15
                              Originally posted by gens View Post
                              haven't really gone that deep
                              it's a different API afaik from the kernels KMS
                              And KMS isn't needed for anything as long as the driver provides its own mechanism. As has been said mainy times before, the lack of KMS is a moot point in the NVidia driver.

                              Comment

                              Working...
                              X