Announcement

Collapse
No announcement yet.

Mesa 22.2 Released With AMD RDNA3 Prep, Intel Arc Graphics, Many Vulkan Improvements

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

  • Mesa 22.2 Released With AMD RDNA3 Prep, Intel Arc Graphics, Many Vulkan Improvements

    Phoronix: Mesa 22.2 Released With AMD RDNA3 Prep, Intel Arc Graphics, Many Vulkan Improvements

    The belated Mesa 22.2 was unexpectedly released today for providing the very latest open-source Linux graphics driver support not only for Intel and AMD Radeon graphics hardware but also the reverse-engineered Nouveau (NVIDIA) driver and the many smaller drivers like Etnaviv, Mali, Panfrost, the new PowerVR Vulkan driver, and the software drivers like LLVMpipe and Zink...

    https://www.phoronix.com/news/Mesa-22.2-Released

  • #2
    I wonder if we will soon be able to use zink on windows as a drop in ogl dll currently you "Can" as in, you can force it, but iirc it does not work at all

    Comment


    • #3
      Is there any solution for being able to know about these changes during an update on a distro? I vaguely recall something in GNOME Software showing this.

      When I download a graphics driver from AMD or NVIDIA, they list a general changelog before you download the driver, and it lists major changes. I feel something like the R600g NIR re-write and RADV RT queries change would go unnoticed until they're either accidentally discovered, or you have to manually check news sites and/or commits to know about it.

      Comment


      • #4
        Originally posted by Espionage724 View Post
        Is there any solution for being able to know about these changes during an update on a distro? I vaguely recall something in GNOME Software showing this.

        When I download a graphics driver from AMD or NVIDIA, they list a general changelog before you download the driver, and it lists major changes. I feel something like the R600g NIR re-write and RADV RT queries change would go unnoticed until they're either accidentally discovered, or you have to manually check news sites and/or commits to know about it.
        https://docs.mesa3d.org/relnotes.html

        Although it doesn't look like they've been published for this release yet.

        Comment


        • #5
          Originally posted by smitty3268 View Post

          https://docs.mesa3d.org/relnotes.html

          Although it doesn't look like they've been published for this release yet.
          The release notes have not been updated in 30+ days (21.1.6 and 21.1.7 are missing for example).. Vacation time + priorization, maybe?

          Comment


          • #6
            updated https://www.youtube.com/watch?v=fiG5fbwcPaQ

            Comment


            • #7
              Radeon(SI)
              Can anyone please verify if most VA and VDPAU hardware accelerated modes didn't work for you any longer, too?

              Polaris 20, here.
              See it for several months.
              Due to LLVM 14/15 (git) and other toolchain things I haven't bisected it, yet.
              I've currently no idea which commit could be the culprit.
              ‚Äč
              vainfo
              libva info: VA-API version 1.15.0
              libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
              libva info: Found init function __vaDriverInit_1_15
              ATTENTION: default value of option mesa_glthread overridden by environment.
              ATTENTION: default value of option allow_draw_out_of_order overridden by environment.
              libva info: va_openDriver() returns 0
              vainfo: VA-API version: 1.15 (libva 2.15.0)
              vainfo: Driver version: Mesa Gallium driver 22.3.0-devel for AMD Radeon RX 580 Series (polaris10, L
              LVM 15.0.0, DRM 3.47, 5.19.10-3.g415f514-default)
              vainfo: Supported profile and entrypoints
              VAProfileMPEG2Simple : VAEntrypointVLD
              VAProfileMPEG2Main : VAEntrypointVLD
              VAProfileJPEGBaseline : VAEntrypointVLD
              VAProfileNone : VAEntrypointVideoProc

              vdpauinfo
              display: :0 screen: 0
              ATTENTION: default value of option mesa_glthread overridden by environment.
              ATTENTION: default value of option allow_draw_out_of_order overridden by environment.
              API version: 1
              Information string: G3DVL VDPAU Driver Shared Library version 1.0

              Video surface:

              name width height types
              -------------------------------------------
              420 16384 16384 NV12 YV12
              422 16384 16384 UYVY YUYV
              444 16384 16384 Y8U8V8A8 V8U8Y8A8
              420_16 16384 16384
              422_16 16384 16384
              444_16 16384 16384

              Decoder capabilities:

              name level macbs width height
              ----------------------------------------------------
              MPEG1 --- not supported ---
              MPEG2_SIMPLE 3 65536 4096 4096
              MPEG2_MAIN 3 65536 4096 4096
              H264_BASELINE --- not supported ---
              H264_MAIN --- not supported ---
              H264_HIGH --- not supported ---
              VC1_SIMPLE --- not supported ---
              VC1_MAIN --- not supported ---
              VC1_ADVANCED --- not supported ---
              MPEG4_PART2_SP 3 65536 4096 4096
              MPEG4_PART2_ASP 5 65536 4096 4096
              DIVX4_QMOBILE --- not supported ---
              DIVX4_MOBILE --- not supported ---
              DIVX4_HOME_THEATER --- not supported ---
              DIVX4_HD_1080P --- not supported ---
              DIVX5_QMOBILE --- not supported ---
              DIVX5_MOBILE --- not supported ---
              DIVX5_HOME_THEATER --- not supported ---
              DIVX5_HD_1080P --- not supported ---
              H264_CONSTRAINED_BASELINE --- not supported ---
              H264_EXTENDED --- not supported ---
              H264_PROGRESSIVE_HIGH --- not supported ---
              H264_CONSTRAINED_HIGH --- not supported ---
              H264_HIGH_444_PREDICTIVE --- not supported ---
              VP9_PROFILE_0 --- not supported ---
              VP9_PROFILE_1 --- not supported ---
              VP9_PROFILE_2 --- not supported ---
              VP9_PROFILE_3 --- not supported ---
              HEVC_MAIN --- not supported ---
              HEVC_MAIN_10 --- not supported ---
              HEVC_MAIN_STILL --- not supported ---
              HEVC_MAIN_12 --- not supported ---
              HEVC_MAIN_444 --- not supported ---
              HEVC_MAIN_444_10 --- not supported ---
              HEVC_MAIN_444_12 --- not supported ---
              AV1_MAIN --- not supported ---
              AV1_HIGH --- not supported ---
              AV1_PROFESSIONAL --- not supported ---

              Comment


              • #8
                Check if the mesa build you use adds
                Code:
                -D video-codecs=vc1dec,h264dec,h264enc,h265dec,h265enc
                to its meson command.

                See https://gitlab.freedesktop.org/mesa/...29c163e42c3600 and https://bugs.archlinux.org/task/74615 for more info.

                Comment


                • #9
                  Yes, thanks (I konw ;-) )
                  All fine for some days.
                  But I haven't had time for earlier posting.
                  More to come.

                  See here, too:
                  Fedora Linux Disabling Mesa's H.264 / H.265 / VC1 VA-API Support Over Legal Concerns
                  https://www.phoronix.com/news/Fedora-Disable-Bad-VA-API

                  Comment


                  • #10
                    wow, i knew it was sensible of RedHat to pull out those codecs from a finished distro release, but to see mesa devs deem it legally too risky to even let the option available for others to compile mesa with those codecs?!

                    it's horrible to see how patent law can be so pernicious and antagonic to technological advancement and adoption, and it's also a bit scary that this has been in there until now and only now did they wake up to such a big risk being taken...

                    Comment

                    Working...
                    X