From: gmane@reliableembeddedsystems.com
To: yocto@yoctoproject.org, armccurdy@gmail.com
Cc: robert.berger@reliableembeddedsystems.com
Subject: Re: [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support
Date: Wed, 31 May 2017 14:01:51 -0500 [thread overview]
Message-ID: <dcfc77e90f187d33412b0d451333653d@reliableembeddedsystems.com> (raw)
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
next reply other threads:[~2017-05-31 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 19:01 gmane [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-30 18:44 [PATCH] yocto-bsp: Fix QEMUARM based bsps to not offer SMP support Alejandro Hernandez
2017-05-30 19:59 ` Leonardo Sandoval
2017-05-30 20:12 ` Alejandro Hernandez
2017-05-30 22:32 ` Andre McCurdy
2017-05-30 22:52 ` Alejandro Hernandez
2017-05-31 1:11 ` Andre McCurdy
2017-05-31 1:15 ` Bruce Ashfield
2017-05-31 18:20 ` Andre McCurdy
2017-05-31 18:46 ` Khem Raj
2017-06-01 0:41 ` Alejandro Hernandez
2017-06-01 0:57 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dcfc77e90f187d33412b0d451333653d@reliableembeddedsystems.com \
--to=gmane@reliableembeddedsystems.com \
--cc=armccurdy@gmail.com \
--cc=robert.berger@reliableembeddedsystems.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.