From: Paul Kocialkowski <paul.kocialkowski@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH i-g-t] docs/chamelium: Explain that the Chamelium should only target one DUT
Date: Tue, 29 Aug 2017 18:11:33 +0300 [thread overview]
Message-ID: <20170829151133.21290-1-paul.kocialkowski@linux.intel.com> (raw)
This adds an explanation about why the Chamelium should only be
connected to one target device at once to the in-tree documentation.
Signed-off-by: Paul Kocialkowski <paul.kocialkowski@linux.intel.com>
---
docs/chamelium.txt | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/docs/chamelium.txt b/docs/chamelium.txt
index 77594284..ae7ac34a 100644
--- a/docs/chamelium.txt
+++ b/docs/chamelium.txt
@@ -54,6 +54,12 @@ CI system with a shared testlist) to remove the Chamelium configuration from the
hosts that shouldn't connect to the Chamelium so that they can be skipped, which
is faster than a network timeout.
+It should also be noted that each Chamelium platform should only be used for
+testing a single target device at a time. This is because the reset call issued
+by the IGT tests is common to all connectors and thus one machine running a test
+on a given connector may reset the chamelium while another machine is running
+a test on another connector.
+
An example fully-featured configuration follows:
[Common]
FrameDumpPath=/root/
--
2.14.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2017-08-29 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 15:11 Paul Kocialkowski [this message]
2017-08-29 15:30 ` ✓ Fi.CI.BAT: success for docs/chamelium: Explain that the Chamelium should only target one DUT Patchwork
2017-08-29 17:53 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-08-30 18:40 ` [PATCH i-g-t] " Lyude Paul
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=20170829151133.21290-1-paul.kocialkowski@linux.intel.com \
--to=paul.kocialkowski@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