From: "Tom Rini" <trini@konsulko.com>
To: Jon Mason <jdmason@kudzu.us>
Cc: poky@lists.yoctoproject.org
Subject: Re: [poky] [PATCH 1/2] beaglebone-yocto: use correct CPU and QB_RNG
Date: Thu, 14 Oct 2021 13:34:53 -0400 [thread overview]
Message-ID: <20211014173453.GG7964@bill-the-cat> (raw)
In-Reply-To: <20211014143124.13941-1-jdmason@kudzu.us>
On Thu, Oct 14, 2021 at 10:31:23AM -0400, Jon Mason wrote:
> The beagles use the AM3358 SoC, which is an Arm Cortex-A8. Use that for
> QB_CPU. Also, use QB_RNG to specify the random number generator device.
> Finally, correct the image deps to get qemu to run.
>
> Signed-off-by: Jon Mason <jdmason@kudzu.us>
> ---
> meta-yocto-bsp/conf/machine/beaglebone-yocto.conf | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> index b3d960a8cd80..06746afa96ae 100644
> --- a/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> +++ b/meta-yocto-bsp/conf/machine/beaglebone-yocto.conf
> @@ -41,16 +41,16 @@ MACHINE_FEATURES = "usbgadget usbhost vfat alsa"
> IMAGE_BOOT_FILES ?= "u-boot.${UBOOT_SUFFIX} ${SPL_BINARY} ${KERNEL_IMAGETYPE} ${KERNEL_DEVICETREE}"
>
> # support runqemu
> -EXTRA_IMAGEDEPENDS += "qemu-native qemu-helper-native"
> +EXTRA_IMAGEDEPENDS += "qemu-system-native qemu-helper-native:do_addto_recipe_sysroot"
> IMAGE_CLASSES += "qemuboot"
> QB_DEFAULT_FSTYPE = "wic"
> QB_FSINFO = "wic:no-kernel-in-fs"
> QB_KERNEL_ROOT = "/dev/vda2"
> QB_SYSTEM_NAME = "qemu-system-arm"
> QB_MACHINE = "-machine virt"
> -QB_CPU = "-cpu cortex-a15"
> +QB_CPU = "-cpu cortex-a8"
> QB_KERNEL_CMDLINE_APPEND = "console=ttyAMA0 systemd.mask=systemd-networkd"
> -QB_OPT_APPEND = "-device virtio-rng-device"
> +QB_RNG = "-device virtio-rng-device"
> QB_TAP_OPT = "-netdev tap,id=net0,ifname=@TAP@,script=no,downscript=no"
> QB_NETWORK_DEVICE = "-device virtio-net-device,netdev=net0,mac=@MAC@"
> QB_ROOTFS_OPT = "-drive id=disk0,file=@ROOTFS@,if=none,format=raw -device virtio-blk-device,drive=disk0"
Perhaps this is the wrong place to open this can of worms, so to speak,
but why is the beaglebone BSP also supporting QEMU, under the "virt"
machine that would be for qemuarm ? It would be I think one thing to
make use of
https://qemu.readthedocs.io/en/latest/system/arm/sabrelite.html on the
appropriate machine.conf file and support running it that way as well.
But this isn't emulating the BSP hardware, it's just passing the
resulting rootfs image to qemu-system-arm. If that's a general goal
now, shouldn't it be pushed up higher in the include files?
--
Tom
next prev parent reply other threads:[~2021-10-14 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 14:31 [PATCH 1/2] beaglebone-yocto: use correct CPU and QB_RNG Jon Mason
2021-10-14 14:31 ` [PATCH 2/2] genericx86-common.inc: add qemu requirement Jon Mason
2021-10-14 17:34 ` Tom Rini [this message]
2021-10-14 22:45 ` [poky] [PATCH 1/2] beaglebone-yocto: use correct CPU and QB_RNG Richard Purdie
2021-10-14 22:51 ` Tom Rini
2021-10-19 14:47 ` Jon Mason
2021-10-19 14:54 ` Tom Rini
2021-10-19 14:38 ` Jon Mason
2021-10-19 14:43 ` [poky] " Tom Rini
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=20211014173453.GG7964@bill-the-cat \
--to=trini@konsulko.com \
--cc=jdmason@kudzu.us \
--cc=poky@lists.yoctoproject.org \
/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.