From: Stuart Summers via igt-dev <igt-dev@lists.freedesktop.org>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/2] Enhance debug capability in kms_chamelium
Date: Thu, 14 Feb 2019 16:40:41 -0800 [thread overview]
Message-ID: <20190215004043.21500-1-stuart.summers@intel.com> (raw)
The first patch in the series cleans up the missed requirement for VGA
tests in CI due to lack of support in later hardware.
The second patch adds a new libssh interface to extract chameleond
daemon logs from the Chamelion board. Over time, it might be interesting
to add new remote logging capability into the Python daemon itself or to
move this ssh based log capture into the existing xmlrpc interface. For
the short term, I am hoping to extract some additional logs from CI with
this patch.
Stuart Summers (2):
i915/kms_chamelium: Require gen < 9 for VGA testing
i915/kms_chamelium: Pull chameleond logs for debugging
Dockerfile.debian | 1 +
Dockerfile.fedora | 1 +
lib/igt_chamelium.c | 150 +++++++++++++++++++++++++++++++++++++++++-
lib/meson.build | 4 ++
meson.build | 4 +-
tests/kms_chamelium.c | 2 +
6 files changed, 160 insertions(+), 2 deletions(-)
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-02-15 0:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 0:40 Stuart Summers via igt-dev [this message]
2019-02-15 0:40 ` [igt-dev] [PATCH i-g-t 1/2] i915/kms_chamelium: Require gen < 9 for VGA testing Stuart Summers via igt-dev
2019-02-18 10:57 ` Petri Latvala
2019-02-19 16:18 ` Summers, Stuart
2019-02-15 0:40 ` [igt-dev] [PATCH i-g-t 2/2] i915/kms_chamelium: Pull chameleond logs for debugging Stuart Summers via igt-dev
2019-02-21 15:37 ` Arkadiusz Hiler
2019-02-21 16:08 ` Summers, Stuart
2019-02-15 8:58 ` [igt-dev] ✗ Fi.CI.BAT: failure for Enhance debug capability in kms_chamelium Patchwork
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=20190215004043.21500-1-stuart.summers@intel.com \
--to=igt-dev@lists.freedesktop.org \
--cc=stuart.summers@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox