<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial;font-size:10.5pt" ><div dir="ltr" style="font-family:Arial;font-size:10.5pt" ><div dir="ltr" ><div> </div>
<div>Add your command to the same help file here you see the existing qemuarm target</div>
<div> </div>
<div>You can now run 'bitbake <target>'</div>
<div>Common targets are:<br> obmc-phosphor-image</div>
<div>You can also run generated qemu images with a command like:<br> runqemu qemuarm <<<<<---------WHERE EVER THAT COMES FROM</div>
<div> </div></div>
<div dir="ltr" ><div> </div>
<div> </div>
<div>I hit a build failure, but it went away the 2nd time I tried. Probably just ignore unless that is an interesting data point.</div>
<div> </div>
<div><div>| ERROR: Function failed: Fetcher failure for URL: 'git://git.qemu.org/qemu.git;protocol=git'. Unable to fetch URL from any source.<br>ERROR: Task 71 (virtual:native:/home/causten/openbmc-barreleye/meta/recipes-devtools/qemu/qemu_git.bb, do_fetch) failed with exit code '1'</div></div>
<div><div> </div>
<div>No network yet :( Makes things hard to use. Can you add an ethernet device?</div>
<div> </div>
<div> </div>
<div><br>Chris Austen<br>POWER Systems Enablement Manager<br>(512) 286-5184 (T/L: 363-5184)</div>
<div> </div>
<div> </div>
<blockquote data-history-content-modified="1" style="border-left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; margin-right:0px" >----- Original message -----<br>From: Joel Stanley <joel@jms.id.au><br>Sent by: "openbmc" <openbmc-bounces+austenc=us.ibm.com@lists.ozlabs.org><br>To: Andrew Jeffery <andrew@aj.id.au><br>Cc: OpenBMC <openbmc@lists.ozlabs.org><br>Subject: Re: [PATCH] runqemu: Add palmetto target<br>Date: Thu, Mar 17, 2016 12:20 AM<br>
<div><font face="Default Monospace,Courier New,Courier,monospace" size="2" >On Thu, Mar 17, 2016 at 3:22 PM, Andrew Jeffery <andrew@aj.id.au> wrote:<br>> The patch does a few things, but is more for inciting feedback than for<br>> merging:<br>><br>> * Adds qemu_git.bb in favour of qemu_2.4.0.bb<br>> * Configured to build from master, at the commit merging the AST2400 support<br>> * Adds a runqemu target 'palmetto'<br><br>This is a good idea. Fix up the commit message so we can merge it :)<br><br>><br>> diff --git a/yocto-poky/meta/recipes-devtools/qemu/qemu.inc b/yocto-poky/meta/recipes-devtools/qemu/qemu.inc<br>> index f6c0ae3..80ba2ca 100644<br>> --- a/yocto-poky/meta/recipes-devtools/qemu/qemu.inc<br>> +++ b/yocto-poky/meta/recipes-devtools/qemu/qemu.inc<br><br>yocto-poky is supposed to be the upstream repository, and shouldn't be<br>patched by us.<br><br>I don't know how poky lets us override built in recipies with those<br>from other meta- packages. Can we carry your qemu-git.bb in<br>meta-whatever instead?<br><br>Patrick, do you have any suggestions here?<br><br><br>> diff --git a/yocto-poky/scripts/runqemu b/yocto-poky/scripts/runqemu<br>> index 23cf5be..f09da50 100755<br>> --- a/yocto-poky/scripts/runqemu<br>> +++ b/yocto-poky/scripts/runqemu<br><br>The changes to this script look like a good start.<br><br>> @@ -110,7 +110,7 @@ while true; do<br>> arg=${1}<br>> case "$arg" in<br>> "qemux86" | "qemux86-64" | "qemuarm" | "qemuarm64" | "qemumips" | "qemumipsel" | \<br>> - "qemumips64" | "qemush4" | "qemuppc" | "qemumicroblaze" | "qemuzynq")<br>> + "qemumips64" | "qemush4" | "qemuppc" | "qemumicroblaze" | "qemuzynq" | "palmetto")<br><br>Perhaps call it qemupalmetto? qemupalmbmc? to match the existing ones.<br><br>> [ -z "$MACHINE" ] && MACHINE=$arg || \<br>> error "conflicting MACHINE types [$MACHINE] and [$arg]"<br>> ;;<br>> @@ -236,13 +236,13 @@ fi<br>><br>_______________________________________________<br>openbmc mailing list<br>openbmc@lists.ozlabs.org<br><a href="https://lists.ozlabs.org/listinfo/openbmc" target="_blank" >https://lists.ozlabs.org/listinfo/openbmc</a></font></div></blockquote></div></div></div></div><BR>