AMD Announces The AMDGPU Composition Stack "ACS" For Advanced Linux Desktop Features

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • microcode
    Senior Member
    • Mar 2013
    • 2364

    #21
    Originally posted by ms178 View Post
    How will this integrate into the Wayland compositor landscape? Is it yet another one, will features eventually trickle down to most of the other's? I care particularly about adoption in KWin.
    Essentially they seem to be looking to show how to use their compositing/overlay/DRM stuff if you are a compositor implementor; so if there's useful stuff in here it'll end up in wlroots or similar libraries, or it'll end up in specific products (set top boxes [as long as those exist] and perhaps automotive infotainment).

    And to put it clearly, the point isn't that the code they put in this compositor branch will be copyable/directly usable elsewhere, but that it will be a reference for the techniques.

    Comment

    • Quackdoc
      Senior Member
      • Oct 2020
      • 5054

      #22


      YAY

      Comment

      • anda_skoa
        Senior Member
        • Nov 2013
        • 1192

        #23
        Originally posted by mdedetrich View Post
        So I am kind of confused here, is this meant to be something akin to gamescope where the intended target is meant to be for end users
        One of their goals seems this to be a part of a full stack solution should a B2B customer want engage them for a product in which AMD delivers hardware and the full software stack, e.g. kiosk systems, digital signage, etc.

        To be utilised in full stack opensource delivery vehicle for AMDs commercial solutions and products.
        So user facing of a sort but not as a separately recognizable component like on a desktop system.

        Originally posted by mdedetrich View Post
        is it just a test/reference compositor so they can test stuff before submitting it upstream as a wayland protocol?
        This seems also to be one of the use cases

        To act as a staging area for Wayland features to be open-sourced to mainline Weston project.
        And the announcement has two more additional use cases:

        To act as a reference compositor for AMD's advanced graphics and display feature development.
        Likely as a sort of show case of advanced features for application developers to test against if they want to use those.

        To provide a middleware compositor which extracts the best out of AMD Display and Graphics HW
        That ones is no quite so clear to me though.

        Comment

        • anda_skoa
          Senior Member
          • Nov 2013
          • 1192

          #24
          Originally posted by Danny3 View Post
          Bastards would do everything except except giving us SR-IOV, CEC support and a graphical control panel that would pull in a lot of dependencies that are in the drivers
          I would say that is pretty much the target of one of their stated goals

          To act as a reference compositor for AMD's advanced graphics and display feature development.
          Enabling them to show what kind of support compositors need to have so that applications can make full use of the driver and hardware capabilities

          Comment

          • Nocifer
            Senior Member
            • Jun 2018
            • 224

            #25
            Originally posted by microcode View Post

            Essentially they seem to be looking to show how to use their compositing/overlay/DRM stuff if you are a compositor implementor; so if there's useful stuff in here it'll end up in wlroots or similar libraries, or it'll end up in specific products (set top boxes [as long as those exist] and perhaps automotive infotainment).

            And to put it clearly, the point isn't that the code they put in this compositor branch will be copyable/directly usable elsewhere, but that it will be a reference for the techniques.
            Not only a reference, but as skeevy420 said, they're also probably looking to showcase, then implement on their end, then propose as protocols, and finally help upstream and integrate into the actual production compositors (e.g. Kwin, and possibly Mutter as well) the missing functionality that Wayland should have before they're able to in turn begin porting over to Linux the missing driver features like Super Resolution, Anti Lag, etc.

            And the best way to do that is to use the reference compositor, which is as unopinionated and universal as it can get.

            Comment

            • royce
              Senior Member
              • Aug 2018
              • 655

              #26
              Originally posted by Espionage724 View Post
              Does this mean AMD is essentially depreciating any Xorg support going forward?

              I don't like the way this sounds, and I still find it odd a HDMI Full/Limited RGB option was never re-added since years ago with amdgpu when radeonsi/previous had it. Now it sounds like the option still won't come for anything other than specific DE support (afaik only Plasma 6 GUI or monitors.xml GNOME).
              There's been basically no development effort on X11 for years now. Except Xwayland.

              Comment

              • Saigu
                Junior Member
                • Sep 2023
                • 8

                #27
                Originally posted by Kjell View Post
                Wish they would have gone with wlroots
                Fork it to a living thing right alongside and plan a convergence of the optimality of Lisa Su Love and Intel Graphics etc. fallback!

                I'm just here for the Penrose Tiling Manager and side-aligned object handles, rollup and stacking controls (σ,φ) plus 4 GL clipboard managers and mouse didactyly.

                Comment

                • DanL
                  Senior Member
                  • Oct 2007
                  • 3122

                  #28
                  Originally posted by Venemo View Post
                  I just wish they named it something else. "AMDGPU" is already an overloaded term and means a bunch of different things in this context. This is just going to confuse users.
                  I remember having this same conversation with bridgman a while back.

                  Comment

                  • DanL
                    Senior Member
                    • Oct 2007
                    • 3122

                    #29
                    Originally posted by Danny3 View Post
                    Bastards would do everything except except giving us SR-IOV, CEC support and a graphical control panel that would pull in a lot of dependencies that are in the drivers
                    Would it be possible for you to stay on topic instead of saying this over and over, every time you see AMD mentioned in an article? Same thing with your Snap rant every time Canonical or Ubuntu is mentioned...

                    Comment

                    • CharlieB
                      Junior Member
                      • Dec 2024
                      • 4

                      #30
                      I like it.
                      AMD has been pretty much #1 choice in Linux world so their ACS is very likely to lead the wayland crowd.
                      USers will get leadin g performance edge with new features on AMD cards that are yet to be incorporated into vanilla open-source projects.

                      It wouldn't surprise me if some of the most aggressive Linux distros wholeheartedly adopt the project.

                      Comment

                      Working...
                      X