From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Antti Koskipaa <antti.koskipaa@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t v2 0/8] kms_cursor_crc enhancements
Date: Fri, 25 Apr 2014 16:27:02 +0300 [thread overview]
Message-ID: <20140425132702.GT18465@intel.com> (raw)
In-Reply-To: <1397131692-2857-1-git-send-email-antti.koskipaa@linux.intel.com>
On Thu, Apr 10, 2014 at 03:08:04PM +0300, Antti Koskipaa wrote:
> This patch series enhances the cursor test to actually be useful.
>
> The old "black transparent cursor on black background" tests are
> replaced with a visible cursor and the framework is changed to
> be more flexible and extendable. This way cursor rotation tests
> can be added with ease in the future.
>
> Also adds a couple more tests to the current set.
>
> v2:
> - reinstate "go nuts" -test
> - Add background picture for better test coverage
>
> Antti Koskipaa (8):
> kms_cursor_crc: Remove some test cases and change cursor to color
> kms_cursor_crc: Move cursor enable and disable calls where they belong
> kms_cursor_crc: Use a function pointer to call test
> kms_cursor_crc: Separate onscreen and offscreen tests
> kms_cursor_crc: Add reference software rendering
> kms_cursor_crc: Add moving cursor test
> kms_cursor_crc: Add random cursor placement test
> kms_cursor_crc: Add background picture
I pushed the lot, and fixed the small issue in 2/8 that I pointed out.
I also pushed a pile of extra fixes, mainly to fix --list-subtests,
and I also tried to fix my gen2 LVDS vs. pipe B issue, which I
suppose is the same thing as this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=75131
>
> tests/kms_cursor_crc.c | 255 ++++++++++++++++++++++++++++---------------------
> 1 file changed, 146 insertions(+), 109 deletions(-)
>
> --
> 1.8.3.2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-04-25 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 12:08 [PATCH i-g-t v2 0/8] kms_cursor_crc enhancements Antti Koskipaa
2014-04-10 12:08 ` [PATCH i-g-t v2 1/8] kms_cursor_crc: Remove some test cases and change cursor to color Antti Koskipaa
2014-04-10 12:08 ` [PATCH i-g-t v2 2/8] kms_cursor_crc: Move cursor enable and disable calls where they belong Antti Koskipaa
2014-04-23 10:54 ` Ville Syrjälä
2014-04-10 12:08 ` [PATCH i-g-t v2 3/8] kms_cursor_crc: Use a function pointer to call test Antti Koskipaa
2014-04-10 12:08 ` [PATCH i-g-t v2 4/8] kms_cursor_crc: Separate onscreen and offscreen tests Antti Koskipaa
2014-04-10 12:08 ` [PATCH i-g-t v2 5/8] kms_cursor_crc: Add reference software rendering Antti Koskipaa
2014-04-10 12:08 ` [PATCH i-g-t v2 6/8] kms_cursor_crc: Add moving cursor test Antti Koskipaa
2014-04-10 12:08 ` [PATCH i-g-t v2 7/8] kms_cursor_crc: Add random cursor placement test Antti Koskipaa
2014-04-23 11:04 ` Ville Syrjälä
2014-04-10 12:08 ` [PATCH i-g-t v2 8/8] kms_cursor_crc: Add background picture Antti Koskipaa
2014-04-25 13:27 ` Ville Syrjälä [this message]
2014-04-25 14:07 ` [PATCH i-g-t v2 0/8] kms_cursor_crc enhancements Daniel Vetter
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=20140425132702.GT18465@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=antti.koskipaa@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox