[PATCH] runqemu: Add palmetto target

Patrick Williams patrick at stwcx.xyz
Fri Mar 18 03:28:45 AEDT 2016


On Thu, Mar 17, 2016 at 03:22:48PM +1030, Andrew Jeffery wrote:
> diff --git a/yocto-poky/scripts/runqemu b/yocto-poky/scripts/runqemu
> index 23cf5be..f09da50 100755
> --- a/yocto-poky/scripts/runqemu
> +++ b/yocto-poky/scripts/runqemu
> @@ -110,7 +110,7 @@ while true; do
>      arg=${1}
>      case "$arg" in
>          "qemux86" | "qemux86-64" | "qemuarm" | "qemuarm64" | "qemumips" | "qemumipsel" | \
> -        "qemumips64" | "qemush4"  | "qemuppc" | "qemumicroblaze" | "qemuzynq")
> +        "qemumips64" | "qemush4"  | "qemuppc" | "qemumicroblaze" | "qemuzynq" | "palmetto")

It seems like there should be a way to extend the machines in runqemu
without modifying the script.  Maybe an environment variable like
"palmetto_SUPPORTS_QEMU=1" that we can set in one of the bitbake machine
files for each machine?

Might want to bounce this problem off of #yocto on IRC.

> +PALMETTO_DEFAULT_KERNEL=cuImage
> +PALMETTO_DEFAULT_FSTYPE=cpio.gz

Also ideally have these come from a bitbake file.

> +        "palmetto")
> +            mem_size=512
> +            ;;

> +if [ "$MACHINE" = "palmetto" ]; then
> +    QEMU=qemu-system-arm
> +    MACHINE_SUBTYPE=palmetto-bmc
> +    export QEMU_AUDIO_DRV="none"
> +    KERNCMDLINE="console=ttyS4"
> +    QEMUOPTIONS="$QEMU_NETWORK_CMD -M ${MACHINE_SUBTYPE} -initrd $ROOTFS -no-reboot -nographic"
> +fi
> +

Would be nice if this stuff was also in a bitbake file of sorts.  Would
really be nice if we could leverage the machine classes (palmetto is-a
openpower) to reduce the redundancy.

>  
> -- 
> 2.5.0
> 
> _______________________________________________
> openbmc mailing list
> openbmc at lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/openbmc

-- 
Patrick Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20160317/3d22ad0c/attachment.sig>


More information about the openbmc mailing list