Announcement

Collapse
No announcement yet.

The Khronos Group Announces "Kamaros" As Their Newest Forthcoming API

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

  • The Khronos Group Announces "Kamaros" As Their Newest Forthcoming API

    Phoronix: The Khronos Group Announces "Kamaros" As Their Newest Forthcoming API

    The Khronos Group that is known as the standards body behind OpenGL, OpenCL, Vulkan, SPIR-V, glTF, OpenXR, and other industry APIs announced that their next API will be called Kamaros...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    So.. will this be good or bad for libcamera?

    Comment


    • #3
      So many APIs, they will soon need a special API for all them APIs.

      One API to rule them all!

      Comment


      • #4
        Originally posted by Neuro-Chef View Post
        So.. will this be good or bad for libcamera?
        Time will tell.

        Libcamera, although great for sure, is made by the raspberry pi folks. That on it's own is just fine but for camera vendors probably not that appealing to use. An open industry standard build by a standards body like kronos is likely to see much more adoption. At least that's how i see it.

        Then again, kronos also tried to make standards for video encoding/decoding (like OpenMax) which thus far gained traction on mobile but don't really seem to be present on the desktop side (there it's still mostly VA-API and NVENC). So.... again, time will tell

        Comment


        • #5
          Originally posted by ddriver View Post
          So many APIs, they will soon need a special API for all them APIs.

          One API to rule them all!
          That's basically what this is... an adapter/condom API so OEM developers can use a variety of APIs behind the scenes if that will save them work, and provide a standards-compliant API to application developers. That's what the OEMs want to do - make their hardware available to the widest software market with the least effort. It's what the Application Developers want - to have a single reliable API with backwards-compatibility guarantees (Khronos will take care of enforcing that contract.)

          Comment


          • #6
            Originally posted by ddriver View Post
            So many APIs, they will soon need a special API for all them APIs.

            One API to rule them all!
            One API to rule them all, one API to find them,

            One API to bring th...the hell is a Kamaros?

            Situation: There are two competing standards.​


            20 Rings. My girlfriend forged 20 Rings.
            Try not to forge any more rings on your way across the parking lot.

            Comment


            • #7
              Originally posted by markg85 View Post
              An open industry standard build by a standards body like kronos is likely to see much more adoption. At least that's how i see it.

              Then again, kronos also tried to make standards for video encoding/decoding (like OpenMax) which thus far gained traction on mobile but don't really seem to be present on the desktop side (there it's still mostly VA-API and NVENC). So.... again, time will tell
              Yeah it is always a question: will it go the way of OpenVG or the way of Vulkan? Vulkan and OpenGL are the Kronos greatest hits, and rather than coming from a committee/consortium, they were both born from industry just trying something. OpenGL from SGI IRIS GL, and Vulkan from Mantle.
              Last edited by microcode; 09 November 2022, 11:52 AM.

              Comment


              • #8
                Just wanna let you know skeevy420 even if nobody else, literally nobody else, appreciates your poems; I appreciate them bro.

                Comment

                Working...
                X