[FFmpeg-trac] #10188(avdevice:new): kmsgrab pixel formats missing DRM_FORMAT_ARGB2101010 and others

[FFmpeg]

#10188: kmsgrab pixel formats missing DRM_FORMAT_ARGB2101010 and others
-------------------------------------+-------------------------------------
             Reporter:  jean         |                    Owner:  (none)
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  avdevice
              Version:  git-master   |               Resolution:
             Keywords:  kmsgrab      |               Blocked By:
  pixfmt                             |
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
Comment (by bermond):

 It looks like that format `30334241` is DRM format
 `DRM_FORMAT_ABGR2101010`. Although missing the `0x` prefix, the number is
 actually in hexadecimal, and not in decimal as it may suggest.

 The following 32bpp-RGB DRM formats are missing:

 - `DRM_FORMAT_XBGR2101010`
 - `DRM_FORMAT_RGBX1010102`
 - `DRM_FORMAT_BGRX1010102`
 - `DRM_FORMAT_ARGB2101010`
 - `DRM_FORMAT_ABGR2101010`
 - `DRM_FORMAT_RGBA1010102`
 - `DRM_FORMAT_BGRA1010102`

 Among these formats, `DRM_FORMAT_ARGB2101010` and `DRM_FORMAT_ABGR2101010`
 seems to be more common, and they are also the ones informed here in the
 user commands above. A [https://lists.ffmpeg.org/pipermail/ffmpeg-
 devel/2019-September/250501.html patch was proposed] in 2019 for adding
 them, but it was rejected.

 But it looks like the solution is not so simple as just adding these
 formats. VAAPI/libva/Mesa also needs to support them, and it appears the
 support is equally missing there. An
 [https://github.com/intel/libva/issues/343 issue is opened] in the libva
 repository requesting them since 2019, without any answer from upstream.
 There seems to be some complexity involved, and the problem is also
 discussed in ticket #8542, being described there as
 [https://trac.ffmpeg.org/ticket/8542#comment:6 not being a ffmpeg bug] in
 the current situation.
-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/10188#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker