summaryrefslogtreecommitdiffstats
path: root/scripts/yocto-bsp
Commit message (Collapse)AuthorAgeFilesLines
* scripts/yocto-bsp: Exit successfully when asking for helpLeonardo Sandoval2015-10-011-1/+1
| | | | | | | | | | When user asks for help, the command should not exit with non-zero status (failure), so removing the non-zero value on the system exit call. (From meta-yocto rev: 98970326fb2f08e684cfc856103b2f9110c9f4fb) Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: add basic git connectivity checkTom Zanussi2013-01-161-0/+13
| | | | | | | | | | | | | | | | | | | | | | | | yocto-bsp create does a 'git ls-remote git://git.yoctoproject.org/linux-yocto-3.4.git *heads*' to get the set of existing branches from the kernel repo. If the user isn't connected to the network, or if git isn't configured sanely, yocto-bsp fails with an ugly Python backtrace. We should try to avoid this by doing a basic sanity check for those things before actually running the command. The sanity check can be avoided by specifying -s on the yocto-bsp command-line: $ yocto-bsp create -s test qemu Fixes [YOCTO #3279] (From meta-yocto rev: 496e76f9bed2ed5a04ef757724d2e63d05c7a601) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: new scriptTom Zanussi2012-03-221-0/+143
Implementation of the 'yocto-bsp' command-line tool, for creating BSPs and listing BSP properties. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>