<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 18 May 2016 at 09:13, Andrew Jeffery <span dir="ltr"><<a href="mailto:andrew@aj.id.au" target="_blank">andrew@aj.id.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id=":8yn" class="">Thanks for the pointer. Is this the patchset you're referring to?<br>
<br>
<a href="http://lists.openembedded.org/pipermail/openembedded-core/2016-March/118982.html" rel="noreferrer" target="_blank">http://lists.openembedded.org/pipermail/openembedded-core/2016-March/118982.html</a><br>
<br>
A brief look suggests it might get us some of the way there, but I'll<br>
take a more detailed look in the next day or so.</div></blockquote></div><br>I was actually thinking of <a href="http://lists.openembedded.org/pipermail/openembedded-core/2016-May/121180.html">http://lists.openembedded.org/pipermail/openembedded-core/2016-May/121180.html</a>.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Your use case is exactly what this sort of work is aiming to solve (put the machine-specific qemu knowledge into the BSP instead of runqemu) so feedback would be greatly appreciated.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>