]> code.ossystems Code Review - openembedded-core.git/commit
linux-yocto: bsp/beaglebone: support qemu -machine virt
authorBruce Ashfield <bruce.ashfield@gmail.com>
Tue, 29 Oct 2019 09:47:18 +0000 (10:47 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 30 Oct 2019 13:47:04 +0000 (13:47 +0000)
commit61eed761a51fcb5ac293b76b4dc6edbd6dbbb32f
treed95a580b19976157534d66f287360ed4f284b3f7
parent6c2c6bed0bd5f0a303b9aacfab7db6daec3ee878
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>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/recipes-kernel/linux/linux-yocto-rt_5.0.bb
meta/recipes-kernel/linux/linux-yocto-tiny_5.0.bb
meta/recipes-kernel/linux/linux-yocto_5.0.bb