Announcement

Collapse
No announcement yet.

GLX_ARB_create_context Called For Pulling

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

  • GLX_ARB_create_context Called For Pulling

    Phoronix: GLX_ARB_create_context Called For Pulling

    The GLX extension for specifying at context-creation time what OpenGL version and context properties will be used may finally enter the X.Org Server, which is important in supporting newer versions of OpenGL under Linux...

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

  • #2
    Using Ubuntu 12.04 with proprietary nVidia drivers and the command "glxinfo" reports lots of "GLX_ARB_create_context" extensions. So what's the problem?

    Comment


    • #3
      Originally posted by mark45 View Post
      Using Ubuntu 12.04 with proprietary nVidia drivers and the command "glxinfo" reports lots of "GLX_ARB_create_context" extensions. So what's the problem?
      The "proprietary" is the keyword here. ^^

      Comment


      • #4
        This is a really good thing to have since now we can have applications that explicitly say what version they want.

        We can change things in the api and have old applications still working with old api versions while having new applications working with new api conventions. Great possibilities.
        About OpenGL ES on desktop: http://www.g-truc.net/post-0457.html
        Like Nvidia's approach more. Like the modularity.

        Would like to see being able to integrated OpenGL ES context creation into OpenGL as something you can set during context creation.
        Just like the core or compatibility profile.
        Last edited by plonoma; 06-09-2012, 05:00 PM.

        Comment


        • #5
          Originally posted by Hirager View Post
          The "proprietary" is the keyword here. ^^
          Yes, but the article talks about X.org functionality, not drivers. So I'm still wondering.

          Comment


          • #6
            Originally posted by mark45 View Post
            Yes, but the article talks about X.org functionality, not drivers. So I'm still wondering.
            Code:
            $ cat /var/log/Xorg.0.log | grep glx
            [    11.758] (II) "glx" will be loaded by default.
            [    11.770] (II) LoadModule: "glx"
            [    11.770] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
            [    11.775] (II) Module glx: vendor="Advanced Micro Devices, Inc."
            So the proprietary AMD driver uses its own version of glx and I'm pretty sure the proprietary Nvidia driver does that, too. The patch which is talked about here patches xorgs glx module so it's in fact for the open source drivers only.

            //EDIT: glx is a part of the OpenGL implementation:
            Code:
            $ cat /var/log/Xorg.0.log | grep GLX
            [    11.776] (II) Loading extension GLX
            [    12.487] (II) AIGLX: Loaded and initialized OpenGL driver(II) GLX: Initialized DRI GL provider for screen 0
            Last edited by V10lator; 06-10-2012, 07:10 AM.

            Comment


            • #7
              Originally posted by mark45 View Post
              Yes, but the article talks about X.org functionality, not drivers. So I'm still wondering.
              The proprietary drivers replace large portions of the x server, in addition to all the other libs, kernel modules, etc. they add to your system.

              Comment


              • #8
                Originally posted by mark45 View Post
                Yes, but the article talks about X.org functionality, not drivers. So I'm still wondering.
                When you use nvidia's binary drivers, you are not using X.org functionality for the most part. Their drivers re-implement much of X functionality.

                Same goes for the kernel.

                It's a parallel operating system with a bit of GNU and Linux thrown in.

                Comment

                Working...
                X