Lines Matching full:board
77 - The staging location (`/build/${board}/usr/local/autotest/`) may not be
164 in the host chroot and on the target board to properly support the test. Any
176 $ emerge-${board} ${test_ebuild}
205 $ TESTS="test1 test2" emerge-${board} ${ebuild}
212 $ USE="test_to_be_enabled -test_to_be_disabled" emerge-${board} \
264 --board=x86-generic
273 $ test_that --board=x86-generic localhost:9222 'f:.*platform_BootPerf/control'
328 importantly, that is the BVT (board verification tests) and Smoke (a subset of
375 means, eg. in a config for a particular board only.
432 $ board=<the board on which to develop>
436 $ cros_workon --board=${board} start ${EBUILD}
446 $ emerge-$board $EBUILD
455 $ cros_workon --board=${board} stop ${EBUILD}
466 $ cros_workon --board=${board} start <package>
471 $ TESTS=<test> emerge-$board <package>
482 $ cros_workon --board=${board} stop <package>
523 1. Choose which board you want to build for (we'll refer to this as ${BOARD},
528 $ ./build_packages --board=${BOARD}
532 $ ./build_image --board=${BOARD} test
545 $ ./image_to_usb.sh --to /dev/sdX --board=${BOARD} \
555 --board=${BOARD}`/chromiumos_test_image.bin
565 Note that the list of ebuilds may differ per board, as each board has
566 potentially different list of overlays. To find all autotest ebuilds for board
569 $ board=foo
570 $ for dir in $(portageq-${board} envvar PORTDIR_OVERLAY); do
588 $ equery-$board hasuse $use_search
609 $ ebuild $(equery-$board which $ebuild_search) info
620 $ emerge-$board -pv ${ebuild_name}
624 [ebuild R ] foo-foo_version to /build/$board/ USE="autox hardened tpmtools
632 $ equery-$board uses ${ebuild_name}
652 is installed in `/build/$board/usr/local/autotest/` and would like know which
656 $ equery-$board belongs /build/${board}/usr/local/autotest/client/site_tests/foo_bar/foo_bar.py
661 DON?T forget to do equery-$board. Just equery will also work, only never
