AMD Sends Out 100 Patches, Enabling Vega Support In AMDGPU DRM

[pal666]

Hm, that's more differences than I thought there would be. I imagined it would just be a beefier Polaris.

it was well known vega has extensive changes

Now I wish there were lower-end Vegas...

it is called vega 11

[dungeon]

https://lists.freedesktop.org/archiv...ch/148795.html
140 mesa patches

He, he, first 60 seems aren't about Vega, but various fixes/cleanps in addrlib - so affect non Vega also.

[Marc Driftmeyer]

100 patches amounting to over fourty thousand lines of code was sent out today for review in order to provide "Vega 10" support within the AMDGPU DRM driver.

forty thousand

[Marc Driftmeyer]

You can, but on my RX480, I can only do it with H.264 (and to be honest, it's glitching horribly in ffmpeg). No VPx support there (or any other free codec for that matter).

That's what I get:

$ vainfo
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_0_39
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.39 (libva 1.7.3)
vainfo: Driver version: mesa gallium vaapi
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc

Here's my vdpauinfo for the RX-480 I own:

$ vdpauinfo
display: :0   screen: 0
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

Decoder capabilities:

name                        level macbs width height
----------------------------------------------------
MPEG1                          --- not supported ---
MPEG2_SIMPLE                    3 65536  4096  4096
MPEG2_MAIN                      3 65536  4096  4096
H264_BASELINE                  52 65536  4096  4096
H264_MAIN                      52 65536  4096  4096
H264_HIGH                      52 65536  4096  4096
VC1_SIMPLE                      1 65536  4096  4096
VC1_MAIN                        2 65536  4096  4096
VC1_ADVANCED                    4 65536  4096  4096
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 ---
HEVC_MAIN                      186 65536  4096  4096
HEVC_MAIN_10                   186 65536  4096  4096
HEVC_MAIN_STILL                --- not supported ---
HEVC_MAIN_12                   --- not supported ---
HEVC_MAIN_444                  --- not supported ---

Output surface:

name              width height nat types
----------------------------------------------------
B8G8R8A8         16384 16384    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8
R8G8B8A8         16384 16384    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8
R10G10B10A2      16384 16384    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8
B10G10R10A2      16384 16384    y  NV12 YV12 UYVY YUYV Y8U8V8A8 V8U8Y8A8 A8I8 I8A8

Bitmap surface:

name              width height
------------------------------
B8G8R8A8         16384 16384
R8G8B8A8         16384 16384
R10G10B10A2      16384 16384
B10G10R10A2      16384 16384
A8               16384 16384

Video mixer:

feature name                    sup
------------------------------------
DEINTERLACE_TEMPORAL             y
DEINTERLACE_TEMPORAL_SPATIAL     -
INVERSE_TELECINE                 -
NOISE_REDUCTION                  y
SHARPNESS                        y
LUMA_KEY                         y
HIGH QUALITY SCALING - L1        y
HIGH QUALITY SCALING - L2        -
HIGH QUALITY SCALING - L3        -
HIGH QUALITY SCALING - L4        -
HIGH QUALITY SCALING - L5        -
HIGH QUALITY SCALING - L6        -
HIGH QUALITY SCALING - L7        -
HIGH QUALITY SCALING - L8        -
HIGH QUALITY SCALING - L9        -

parameter name                  sup      min      max
-----------------------------------------------------
VIDEO_SURFACE_WIDTH              y        48     4096
VIDEO_SURFACE_HEIGHT             y        48     4096
CHROMA_TYPE                      y  
LAYERS                           y         0        4

attribute name                  sup      min      max
-----------------------------------------------------
BACKGROUND_COLOR                 y  
CSC_MATRIX                       y  
NOISE_REDUCTION_LEVEL            y      0.00     1.00
SHARPNESS_LEVEL                  y     -1.00     1.00
LUMA_KEY_MIN_LUMA                y  
LUMA_KEY_MAX_LUMA                y

[eydee]

it is called vega 11

Doesn't mean it's low-end. According to current rumors, there's going to be a successor to Fury, and one for Fury X, and that's it. The rest will be rebranded Polaris. I wouldn't expect a full Vega line before RX 600 series.

[LinuxID10T]

LLVM 5.0 required and currently limited to OpenGL 3.1 because geometry and tesselation shaders aren't finished yet. Wow, they are definitely digging deep into the changes...

[pixo]

Does the consumer Vega support MxGPU?
If yes I would buy it the moment it would come out and dont care if the support is mainlined.
This would be the biggest win for me as for VR there is only Windows for now.

EDIT: Acording to Guru3D Vega support SR-IOV that is needed for MxGPU.

http://www.guru3d.com/news-story/amd-gpu-linux-driver-patches-is-listing-seven-vega-10-ids.html

Now to find good MB for Ryzen with AMD-Vi support that can support APUs too.
Never know if AMD will have 8core APU with the ability to use the iGPU as physic accelerator.

[shmerl]

Here's my vdpauinfo for the RX-480 I own:

vdpau is only good for decoding. For encoding you need vaapi.

[You-]

Hm, that's more differences than I thought there would be.

Vega is using a tile based approach, which is a huge change.

(nVidia went this route a couple of years ago, when it suddenly jumped ahead of AMD in graphics.)

[tomtomme]

Vega is using a tile based approach, which is a huge change.

(nVidia went this route a couple of years ago, when it suddenly jumped ahead of AMD in graphics.)

interesting. wikipedia says this was 2014 with nvidia maxwell. this explains something. they have the smaller / more energy efficient gpu ever since.