Announcement

Collapse
No announcement yet.

Mesa 17.0.4 Released, Mesa 17.1 Has Been Branched & 17.1-RC1 Released

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

  • #11
    Originally posted by smitty3268 View Post

    Compat profile is for backwards compatibility with programs that aren't updated to use the new API. The GL library itself provides both, it's up to the app to pick one or the other.

    It's a way of changing OpenGL without breaking everything.

    TL;DR
    If your app says you still have 3.0, then your app is junk and needs to be updated.
    I think the solution is simple:

    1) spread a directive stating that all programs have to implement the core profile (because compliant profile is deprecated and will be dismissed);

    2) a linux team which approve or not approve the programs classifying them and able to reject the programs in order to make them compliant with the protocol requested.

    I think that one of the weakness of linux is the huge variability which affects the reliability: developers are forced to make the system extremely flexible (because of utilities, software, programs) in an ambient sufficiently rigid (because of dependencies).
    Last edited by Azrael5; 18 April 2017, 08:01 AM.

    Comment


    • #12
      So will Mesa actually pay attention to Blender [hint AMD as you have invested in it and use it as a benchmark system] when they work on OpenCL?

      Platform Name Clover
      Number of devices 1
      Device Name AMD POLARIS10 (DRM 3.8.0 / 4.9.0-2-amd64, LLVM 4.0.0)
      Device Vendor AMD
      Device Vendor ID 0x1002
      Device Version OpenCL 1.1 Mesa 17.0.4
      Driver Version 17.0.4
      Device OpenCL C Version OpenCL C 1.1


      Blender requires OpenCL 1.2. Raise your hand if you see the problem.

      Comment

      Working...
      X