[yocto] Extending runqemu/runqemu-internal with new machines

Andrew Jeffery andrew at aj.id.au
Wed May 18 18:13:50 AEST 2016


Hi Ross,

On Tue, 2016-05-17 at 14:20 +0100, Burton, Ross wrote:
> 
> On 17 May 2016 at 02:15, Andrew Jeffery <andrew at aj.id.au> wrote:
> > Is there a better way to work that might avoid these issues?
> > Alternatively, should we start looking at reworking the
> > runqemu/runqemu-internal scripts such that we don't have to patch
> > them
> > to support our use-case? If so, what sort of approach would the
> > community be happy with?
> > 
> Dig back a few weeks and you'll a RFC series by Robert Yang
> refactoring runqemu for exactly this problem.  I've not yet looked at
> it myself but if you could see if that solves your problems then that
> would be much appreciated.

Thanks for the pointer. Is this the patchset you're referring to?

http://lists.openembedded.org/pipermail/openembedded-core/2016-March/118982.html

A brief look suggests it might get us some of the way there, but I'll
take a more detailed look in the next day or so.

Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20160518/5638ecfd/attachment.sig>


More information about the openbmc mailing list