public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Lyude Paul <lyude@redhat.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t v4 0/5] Add support for the Chamelium
Date: Mon, 16 Jan 2017 14:29:22 -0500	[thread overview]
Message-ID: <1484594962.5861.6.camel@redhat.com> (raw)
In-Reply-To: <20170116192653.4740-1-lyude@redhat.com>

(CCing Tomeu Vizoso <tomeu@tomeuvizoso.net> here since it looks like I
somehow had suppresscc turned on by accident)

On Mon, 2017-01-16 at 14:26 -0500, Lyude wrote:
> This adds basic support for using the Chamelium in hotplugging tests,
> along
> with checking video outputs.
> 
> So far there's still definitely some bugs with video capturing,
> however they
> seem to mostly be the Chamelium's fault. Since we really need to try
> to at
> least get basic support for this into igt, we're going to have to fix
> those
> later. Currently the issues I've observed are:
> 
>  - Quick and successive resolution changes make the HDMI rx on the
> Chamelium
>    barf pretty badly, and the WaitForVideoInputStable RPC call
> doesn't do it's
>    job properly and immediately fails as a result of the video input
> not being
>    stable.
>  - DisplayPort video capturing is not reliable, and occasionally
> results in
>    single pixel mismatches between the fb and the actual video
> output.
> 
> Lyude (5):
>   igt_aux: Add igt_set_autoresume_delay()
>   igt_kms: Add helpers for watching for sysfs hotplug events
>   igt_kms: Add igt_output_from_connector
>   igt_kms: Add kmstest_set_connector_broadcast_rgb()
>   Add support for hotplug testing with the Chamelium
> 
>  configure.ac                                       |   4 +
>  .../intel-gpu-tools/intel-gpu-tools-docs.xml       |   1 +
>  lib/Makefile.am                                    |   6 +
>  lib/Makefile.sources                               |   2 +
>  lib/igt.h                                          |   1 +
>  lib/igt_aux.c                                      |  46 ++++++
>  lib/igt_aux.h                                      |   1 +
>  lib/igt_kms.c                                      | 171
> +++++++++++++++++++++
>  lib/igt_kms.h                                      |  25 +++
>  tests/Makefile.am                                  |   5 +-
>  tests/Makefile.sources                             |   1 +
>  11 files changed, 262 insertions(+), 1 deletion(-)
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2017-01-16 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16 19:26 [PATCH i-g-t v4 0/5] Add support for the Chamelium Lyude
2017-01-16 19:26 ` [PATCH i-g-t v2 1/5] igt_aux: Add igt_set_autoresume_delay() Lyude
2017-01-16 19:26 ` [PATCH i-g-t v3 2/5] igt_kms: Add helpers for watching for sysfs hotplug events Lyude
2017-01-16 19:26 ` [PATCH i-g-t 3/5] igt_kms: Add igt_output_from_connector Lyude
2017-01-16 19:26 ` [PATCH i-g-t 4/5] igt_kms: Add kmstest_set_connector_broadcast_rgb() Lyude
2017-01-16 19:26 ` [PATCH i-g-t v4 5/5] Add support for hotplug testing with the Chamelium Lyude
2017-01-16 19:29 ` Lyude Paul [this message]

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=1484594962.5861.6.camel@redhat.com \
    --to=lyude@redhat.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