summaryrefslogtreecommitdiffstats
path: root/scripts/lib/recipetool/create.py
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@gmail.com>2019-07-05 12:14:03 -0400
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-07-11 09:32:50 +0100
commitee8481f3b61c9788c90390d945ff93e52ab68cea (patch)
treedf62cd69c12d528b63e0300e1aba60b28ab76e26 /scripts/lib/recipetool/create.py
parenta66702f8973aaf0bdbcadf14c44a5cb103e03f06 (diff)
downloadpoky-ee8481f3b61c9788c90390d945ff93e52ab68cea.tar.gz
linux-yocto: bsp/beaglebone: support qemu -machine virt
While we don't normally do a dual h/w and virt BSP (since they tend to have conflicting requirements over time). A minimal overhead option to do this was submitted to linux-yocto. Since it has no impact on the h/w reference, has SDK testing value and can serve as a template on how to do this for other arm boards, it is worth making the configuration available. The original commit log follows: [ If the kernel supports Qemu's virt machine, runqemu works almost for free. The device tree for machine virt is included in Qemu, which simplifies everything quite a bit. This change adds ARCH_VIRT=y and some drivers to the beaglebone kernel configuration which allows to: export MACHINE="beaglebone-yocto" bitbake core-image-minimale runqemu This also works out of an eSDK. Whithout this feature usually two different SDKs need to be compiled and maintained. One SDK is used for development in Qemu, another one is used to develop for the real target hardware. Signed-off-by: Adrian Freihofer <adrian.freihofer@siemens.com> ] (From OE-Core rev: cc1fca6d464775daa15032f11c02d16b99759407) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/lib/recipetool/create.py')
0 files changed, 0 insertions, 0 deletions