Announcement

Collapse
No announcement yet.

Patches Revised Taking RadeonSI OpenGL Compatibility Profile To v4.0

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

  • #11
    Originally posted by shmerl View Post

    Shouldn't the reference rather be AMD's closed driver? That's the most common use case for compat profile on AMD now (various legacy CAD applications and the like), and replacing it with Mesa can avoid this code duplication. So why should Nvidia be emulated instead?
    Because Nvidia is the reference for market.

    Comment


    • #12
      One step closer to deprecate the proprietary drivers. That's only good news.

      Comment


      • #13
        ...but the ARB_vertex_attrib_64bit extension is the lingering blocker that will take a while to address.
        There isn't any blocker anylonger:

        https://gitlab.freedesktop.org/tarce...pu_shader_fp64

        fix enable ARB_vertex_attrib_64bit
        https://gitlab.freedesktop.org/tarce...8ab8f3ede6f81a

        And now:

        OpenGL vendor string: X.Org
        OpenGL renderer string: Radeon RX 580 Series (POLARIS10, DRM 3.26.0, 4.17.0-rc5-1.g7262353-default+, LLVM 7.0.0)
        OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.0-devel (git-6e8bf98e7e)
        OpenGL core profile shading language version string: 4.50
        OpenGL core profile context flags: (none)
        OpenGL core profile profile mask: core profile
        OpenGL core profile extensions:
        OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.0-devel (git-6e8bf98e7e)
        OpenGL shading language version string: 4.40
        OpenGL context flags: (none)
        OpenGL profile mask: compatibility profile
        OpenGL extensions:
        OpenGL ES profile version string: OpenGL ES 3.1 Mesa 18.2.0-devel (git-6e8bf98e7e)
        OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10
        OpenGL ES profile extensions:

        https://lists.freedesktop.org/archiv...ne/198633.html
        and
        https://lists.freedesktop.org/archiv...ne/198635.html

        Comment


        • #14
          Originally posted by chithanh View Post
          I think bridgman explained a number of times that the problem was not getting compatibility profile to be supported. The problem is that a lot of behavior isn't defined by the spec, but rather implementation-dependent. In order to usefully support compatibility profiles, the behavior of the NVidia proprietary driver needs to be emulated.
          NO! MESA is all about writing code to OpenGl spec standards. If they emulate the NVIDIA driver nothing would work. It's long known that NVIDIA's driver is broken when it comes to OpenGL and thats why a lot of FOSS does not run good with Nvidia hardware, because Nvidia ships broken Opengl speced drivers.

          Comment


          • #15
            Originally posted by Rallos Zek View Post
            NO! MESA is all about writing code to OpenGl spec standards. If they emulate the NVIDIA driver nothing would work.
            As I wrote, and bridgman repeated many times I think, the OpenGL spec is often silent on the interaction between core features and compatibility features when used in combination. So support for OpenGL compatibility profiles it is not about writing code to spec.

            Comment

            Working...
            X