From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Sipke Vriend <sipke.vriend@xilinx.com>
Cc: "paul.eggleton@linux.intel.com" <paul.eggleton@linux.intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC OE-core/meta/lib] BSP Specific Qemurunner
Date: Tue, 07 Jan 2014 13:59:37 +0000 [thread overview]
Message-ID: <1389103177.6899.28.camel@ted> (raw)
In-Reply-To: <9bd39deb-0a32-437a-9f50-89abfe43d7d6@CO1EHSMHS004.ehs.local>
On Tue, 2014-01-07 at 03:09 +0000, Sipke Vriend wrote:
> Hi,
>
> This RFC is a proposal to allow BSP layers to setup qemu with their specific
> requirements for the testimage oe-core functionality.
> The suggested changes will be exercised by the
> bitbake -c testimage <image>
> command.
> Similarly to the oeqa test cases this proposal extends the meta/lib/oeqa
> python modules to allow inclusion of python utility scripts in the BSP
> layers.
> Any BSP layer wishing to supply their own qemu setup would need to create
> an appropriate meta-bsplayer/lib/oeqa/utils/<machine>starter.py
> The effect is that the lib/oeqa/utils/qemurunner will either allow the
> bsp layer provided <machine>starter to spawn qemu or if not provided,
> spawn qemu via runqemu as currently.
> An example bsp layer is available here:
> https://github.com/sipke/meta-xilinx/tree/sipke/qemurunner
> with all required additions in the meta-xilinx/lib directory.
>
> This RFC is triggered by and indirectly related to
> Bugzilla report "runqemu shouldn't hard-code machine knowledge"
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=4827
Why would we do this rather than improve runqemu to be extendable from
BSP layers?
Cheers,
Richard
next prev parent reply other threads:[~2014-01-07 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 3:09 [RFC OE-core/meta/lib] BSP Specific Qemurunner Sipke Vriend
2014-01-07 13:59 ` Richard Purdie [this message]
2014-01-07 22:59 ` Sipke Vriend
2014-01-08 13:12 ` Richard Purdie
2014-01-08 13:52 ` Paul Eggleton
2014-01-09 0:01 ` Sipke Vriend
2014-01-09 12:19 ` Stanacar, StefanX
2014-01-09 23:29 ` Sipke Vriend
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=1389103177.6899.28.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=sipke.vriend@xilinx.com \
/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.