CaROS/poky
3
1
Fork 0
mirror of https://git.yoctoproject.org/git/poky synced 2026-01-04 16:10:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

ref-manual: Added some new test variables:

Browse Source 
* TEST_SERIALCONTROL_CMD
 * TEST_SERIALCONTROL_EXTRA_ARGS
 * TEST_POWERCONTROL_CMD
 * TEST_POWERCONTROL_EXTRA_ARGS

(From yocto-docs rev: 25f196cc03178f07201ef183fb309721d412e971)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2014-10-28 09:48:17 -07:00 committed by Richard Purdie
parent e95863cee0
commit 1a6c3a385c
1 changed files with 68 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

68
documentation/ref-manual/ref-variables.xml
View File

@ -9122,6 +9122,37 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
</glossdef>
</glossentry>
<glossentry id='var-TEST_POWERCONTROL_CMD'><glossterm>TEST_POWERCONTROL_CMD</glossterm>
<glossdef>
<para>
For automated hardware testing, specifies the command to
use to control the power of the target machine under test.
Typically, this command would point to a script that
performs the appropriate action (e.g. interacting
with a web-enabled power strip).
The specified command should expect to receive as the last
argument "off", "on" or "cycle" specifying to power off,
on, or cycle (power off and then power on) the device,
respectively.
</para>
</glossdef>
</glossentry>
<glossentry id='var-TEST_POWERCONTROL_EXTRA_ARGS'><glossterm>TEST_POWERCONTROL_EXTRA_ARGS</glossterm>
<glossdef>
<para>
For automated hardware testing, specifies additional
arguments to pass through to the command specified in
<link linkend='var-TEST_POWERCONTROL_CMD'><filename>TEST_POWERCONTROL_CMD</filename></link>.
Setting <filename>TEST_POWERCONTROL_EXTRA_ARGS</filename>
is optional.
You can use it if you wish, for example, to separate the
machine-specific and non-machine-specific parts of the
arguments.
</para>
</glossdef>
</glossentry>
<glossentry id='var-TEST_QEMUBOOT_TIMEOUT'><glossterm>TEST_QEMUBOOT_TIMEOUT</glossterm>
<glossdef>
<para>
@ -9142,6 +9173,43 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
</glossdef>
</glossentry>
<glossentry id='var-TEST_SERIALCONTROL_CMD'><glossterm>TEST_SERIALCONTROL_CMD</glossterm>
<glossdef>
<para>
For automated hardware testing, specifies the command
to use to connect to the serial console of the target
machine under test.
This command simply needs to connect to the serial console
and forward that connection to standard input and output
as any normal terminal program does.
</para>
<para>
For example, to use the Picocom terminal program on
serial device <filename>/dev/ttyUSB0</filename> at
115200bps, you would set the variable as follows:
<literallayout class='monospaced'>
TEST_SERIALCONTROL_CMD = "picocom /dev/ttyUSB0 -b 115200"
</literallayout>
</para>
</glossdef>
</glossentry>
<glossentry id='var-TEST_SERIALCONTROL_EXTRA_ARGS'><glossterm>TEST_SERIALCONTROL_EXTRA_ARGS</glossterm>
<glossdef>
<para>
For automated hardware testing, specifies additional
arguments to pass through to the command specified in
<link linkend='var-TEST_SERIALCONTROL_CMD'><filename>TEST_SERIALCONTROL_CMD</filename></link>.
Setting <filename>TEST_SERIALCONTROL_EXTRA_ARGS</filename>
is optional.
You can use it if you wish, for example, to separate the
machine-specific and non-machine-specific parts of the
command.
</para>
</glossdef>
</glossentry>
<glossentry id='var-TEST_SERVER_IP'><glossterm>TEST_SERVER_IP</glossterm>
<glossdef>
<para>