From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH i-g-t 0/4] New pipe level color management tests
Date: Thu, 21 Jan 2016 15:11:52 +0000 [thread overview]
Message-ID: <1453389116-3598-1-git-send-email-lionel.g.landwerlin@intel.com> (raw)
Hi,
This series enables testing pipe level color management using kernel patches
from this serie :
http://lists.freedesktop.org/archives/intel-gfx/2016-January/085922.html
Most of the tests use pipe CRCs to check the results by comparing the output
with the expected output drawn using cairo.
Cheers,
Lionel
Lionel Landwerlin (4):
lib: kms: add crtc_id to igt_pipe_t
lib: kms: add helpers for color management properties on pipes
lib: fb: add igt_paint_color_gradient_range
tests/kms_color: New test for pipe level color management
lib/igt_fb.c | 34 ++
lib/igt_fb.h | 3 +
lib/igt_kms.c | 75 ++++
lib/igt_kms.h | 18 +-
tests/Makefile.sources | 1 +
tests/kms_pipe_color.c | 986 +++++++++++++++++++++++++++++++++++++++++++++++++
6 files changed, 1116 insertions(+), 1 deletion(-)
create mode 100644 tests/kms_pipe_color.c
--
2.6.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2016-01-21 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 15:11 Lionel Landwerlin [this message]
2016-01-21 15:11 ` [PATCH i-g-t 1/4] lib: kms: add crtc_id to igt_pipe_t Lionel Landwerlin
2016-01-21 15:11 ` [PATCH i-g-t 2/4] lib: kms: add helpers for color management properties on pipes Lionel Landwerlin
2016-01-21 15:11 ` [PATCH i-g-t 3/4] lib: fb: add igt_paint_color_gradient_range Lionel Landwerlin
2016-01-21 15:11 ` [PATCH i-g-t 4/4] tests/kms_color: New test for pipe level color management Lionel Landwerlin
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=1453389116-3598-1-git-send-email-lionel.g.landwerlin@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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.