All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Syrjala, Ville" <ville.syrjala@intel.com>,
	"Peres, Martin" <martin.peres@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v10] lib/igt_fb: Added XYUV format support for testing
Date: Tue, 23 Oct 2018 15:54:23 +0200	[thread overview]
Message-ID: <72e51cb3-c919-9dbc-48d7-e6673785fa2b@linux.intel.com> (raw)
In-Reply-To: <a6968cc36efede8658fe4b7e1ac6323a108669ce.camel@intel.com>

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@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. :)

~Maarten
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2018-10-23 13:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08  8:18 [igt-dev] [PATCH i-g-t v10] lib/igt_fb: Added XYUV format support for testing Stanislav Lisovskiy
2018-10-08  9:19 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/igt_fb: Added XYUV format support for testing (rev11) Patchwork
2018-10-08 10:31 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-10-23 11:33 ` [igt-dev] [PATCH i-g-t v10] lib/igt_fb: Added XYUV format support for testing Maarten Lankhorst
2018-10-23 13:51   ` Lisovskiy, Stanislav
2018-10-23 13:54     ` Maarten Lankhorst [this message]
2018-10-24  6:42       ` Lisovskiy, Stanislav
2018-10-24  7:35         ` Maarten Lankhorst
  -- strict thread matches above, loose matches on Subject: below --
2018-10-08  8:13 Stanislav Lisovskiy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=72e51cb3-c919-9dbc-48d7-e6673785fa2b@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=martin.peres@intel.com \
    --cc=stanislav.lisovskiy@intel.com \
    --cc=ville.syrjala@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.