[igt-dev] [PATCH i-g-t v10] lib/igt_fb: Added XYUV format support for testing

[Maarten Lankhorst]

Op 24-10-18 om 08:42 schreef Lisovskiy, Stanislav:
> On Tue, 2018-10-23 at 15:54 +0200, Maarten Lankhorst wrote:
>> Op 23-10-18 om 15:51 schreef Lisovskiy, Stanislav:
>>> On Tue, 2018-10-23 at 13:33 +0200, Maarten Lankhorst wrote:
>>>> Op 08-10-18 om 10:18 schreef Stanislav Lisovskiy:
>>>>> XYUV format support has been added to DRM, modified
>>>>> IGT to reflect those changes.
>>>>>
>>>>> v2: Fixed merge conflict, started to use new yuv<=>rgb
>>>>>     conversion functions.
>>>>>
>>>>> v3: Fixed kms_available_modes_crc test to support new XYUV
>>>>>     format. Fixed a problem, where test complains that two
>>>>>     outputs might use same pipe at the same time.
>>>>>
>>>>> v4: Fixed convertion procedure in igt_fb to support XYUV
>>>>>     properly.
>>>>>
>>>>> v5: Fixed a coding typo.
>>>>>
>>>>> v6: Set depth equal to -1 for XYUV format in order to prevent
>>>>>     it to be used by igt_bpp_depth_to_drm_format, as we do not
>>>>>     want YUV formats to be used in that case.
>>>>>
>>>>> v7: Fix "black" color initialization for create_bo_for_fb with
>>>>>     proper value. Changed naming "planar_stride" to
>>>>> "xyuv_stride".
>>>>>
>>>>> v8: Change naming from DRM_FORMAT_XYUV to DRM_FORMAT_XYUV8888
>>>>>
>>>>> v9: Fixed compilation errors by rebasing to recent master.
>>>>>
>>>>> v10: Adding reference to correspondent kernel commit with the
>>>>> new
>>>>> format
>>>>>      in include/drm-uapi
>>>>>
>>>>> drm-tip:
>>>>> 	commit f75df2cad986f40e190ee97fe3b49dd17174f1af
>>>>> 	Author: Stanislav Lisovskiy <stanislav.lisovskiy at intel.
>>>>> com>
>>>>> 	Date:   Fri Jul 6 11:57:27 2018 +0300
>>>>>
>>>>> 	    drm: Introduce new DRM_FORMAT_XYUV
>>>> In what tree is this commit included? I don't see it in drm-tip,
>>>> drm-
>>>> intel or drm-misc.
>>> The patch is under review still. It got "Reviewed-by" just last
>>> week.
>> Then there's no sense in linking to a commit, a commit ID only exists
>> if it's in drm-misc or drm-intel. :)
>>
> Totally agree :) I was asked to include the commit id, but probably I
> misunderstood the request. Should it be included once, the kernel code
> is in drm-tip?
>
>> ~Maarten

Yes, before that you cannot include it since it only exists on your own machine. :)