From 1a6c3a385c48c0548abda2e1800904a1d8edae0e Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 28 Oct 2014 09:48:17 -0700 Subject: ref-manual: Added some new test variables: * TEST_SERIALCONTROL_CMD * TEST_SERIALCONTROL_EXTRA_ARGS * TEST_POWERCONTROL_CMD * TEST_POWERCONTROL_EXTRA_ARGS (From yocto-docs rev: 25f196cc03178f07201ef183fb309721d412e971) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/ref-manual/ref-variables.xml | 68 ++++++++++++++++++++++++++++++ 1 file changed, 68 insertions(+) diff --git a/documentation/ref-manual/ref-variables.xml b/documentation/ref-manual/ref-variables.xml index a14d67bfd9..b22c661421 100644 --- a/documentation/ref-manual/ref-variables.xml +++ b/documentation/ref-manual/ref-variables.xml @@ -9122,6 +9122,37 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" + TEST_POWERCONTROL_CMD + + + 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. + + + + + TEST_POWERCONTROL_EXTRA_ARGS + + + For automated hardware testing, specifies additional + arguments to pass through to the command specified in + TEST_POWERCONTROL_CMD. + Setting TEST_POWERCONTROL_EXTRA_ARGS + is optional. + You can use it if you wish, for example, to separate the + machine-specific and non-machine-specific parts of the + arguments. + + + + TEST_QEMUBOOT_TIMEOUT @@ -9142,6 +9173,43 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3" + TEST_SERIALCONTROL_CMD + + + 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. + + + + For example, to use the Picocom terminal program on + serial device /dev/ttyUSB0 at + 115200bps, you would set the variable as follows: + + TEST_SERIALCONTROL_CMD = "picocom /dev/ttyUSB0 -b 115200" + + + + + + TEST_SERIALCONTROL_EXTRA_ARGS + + + For automated hardware testing, specifies additional + arguments to pass through to the command specified in + TEST_SERIALCONTROL_CMD. + Setting TEST_SERIALCONTROL_EXTRA_ARGS + is optional. + You can use it if you wish, for example, to separate the + machine-specific and non-machine-specific parts of the + command. + + + + TEST_SERVER_IP -- cgit v1.2.3-54-g00ecf