On 2017-05-31 21:20, Andre McCurdy wrote:
Keeping the existing platform but updating the CPU would have the
advantage that qemuarm could then share binaries and sstate with real
world ARM targets.
It would also be a step towards defining an official "generic ARMv7"
tuning target within OE, which could be used as the default
DEFAULTTUNE for all ARMv7 targets.
I would highly appreciate a "generic ARMv7" target!
What I usually use on various boards is:
*) DEFAULTTUNE = "armv7a-neon"
include conf/machine/include/arm/arch-armv7a.inc
*) same rootfs binay for all boards
*) a kernel starting from a multi_v7_defconfig
*) a different device tree for each board
*) a different u-boot for each board
I even got such a kernel/rootfs to work with the qemu which comes with
the Yocto project with some ancient Yocto version by hacking the qemu
run script [1][2]. This uses the versatile expressa qemu target and uses
a device tree. I did not try, but nowadays runqemu is in Python and
something like this should be possible as well. Like this the same
binaries could run on qemu and on various boards.
[1]
https://github.com/RobertBerger/poky/blob/2015-03-20-dizzy%2B/scripts/runqemu
[2]
https://github.com/RobertBerger/poky/blob/2015-03-20-dizzy%2B/scripts/runqemu-internal
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
