diff options
| author | Paul Kocialkowski <paul.kocialkowski@linux.intel.com> | 2017-08-29 18:11:33 +0300 |
|---|---|---|
| committer | Lyude <lyude@redhat.com> | 2017-08-30 14:39:54 -0400 |
| commit | 2af28e0d34e2d5b3e85070944b4e4e792ec2fed2 (patch) | |
| tree | b44457c7be7573158da1f3d402112a0decc4032f /docs | |
| parent | a23ef519a6bf5b504b9ad67537339f4af4c058de (diff) | |
docs/chamelium: Explain that the Chamelium should only target one DUT
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>
[with one small style change]
Reviewed-by: Lyude Paul <lyude@redhat.com>
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/chamelium.txt | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/docs/chamelium.txt b/docs/chamelium.txt index 77594284..ecfd52b4 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/ |