public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Changqing Li <changqing.li@windriver.com>
To: Matt Madison <matt@madison.systems>,
	openembedded-core@lists.openembedded.org
Cc: Alexander Kanavin <alex@linutronix.de>,
	Khem Raj <raj.khem@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core][PATCH v2 1/2] qemu.bbclass: drop OLDEST_KERNEL reference
Date: Thu, 30 Dec 2021 16:51:49 +0800	[thread overview]
Message-ID: <3e66c6fb-b376-a292-34b1-70abdc270f41@windriver.com> (raw)
In-Reply-To: <20211216114836.964835-2-matt@madison.systems>

[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]


On 12/16/21 7:48 PM, Matt Madison wrote:
> [Please note: This e-mail is from an EXTERNAL e-mail address]
>
> which is introducing task hash changes for some
> allarch package builds, and should no longer
> be needed with recent versions of qemu.
>
> Signed-off-by: Matt Madison <matt@madison.systems>
> ---
>   meta/classes/qemu.bbclass | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/qemu.bbclass b/meta/classes/qemu.bbclass
> index 01a7b86ae1..333202b7c4 100644
> --- a/meta/classes/qemu.bbclass
> +++ b/meta/classes/qemu.bbclass
> @@ -54,7 +54,7 @@ def qemu_run_binary(data, rootfs_path, binary):
>   # this dance). For others (e.g. arm) a -cpu option is not necessary, since the
>   # qemu-arm default CPU supports all required architecture levels.
>
> -QEMU_OPTIONS = "-r ${OLDEST_KERNEL} ${@d.getVar("QEMU_EXTRAOPTIONS_%s" % d.getVar('PACKAGE_ARCH')) or ""}"
> +QEMU_OPTIONS = "${@d.getVar("QEMU_EXTRAOPTIONS_%s" % d.getVar('PACKAGE_ARCH')) or ""}"

Hi,

Latest yocto still take "CentOS 7.x" as Supported Linux Distributions. 
But centos7 have kernel version 3.10.

But we have some archs, like aarch64, set OLDEST_KERNEL to 3.14. Without 
"-r ${OLDEST_KERNEL}",

some recipes which will run qemu during configure or compile will failed 
with error:

FATAL: kernel too old

How about add it back?


Thanks

Changqing

>   QEMU_OPTIONS[vardeps] += "QEMU_EXTRAOPTIONS_${PACKAGE_ARCH}"
>
>   QEMU_EXTRAOPTIONS_ppce500v2 = " -cpu e500v2"
> --
> 2.32.0
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#159782): https://lists.openembedded.org/g/openembedded-core/message/159782
> Mute This Topic: https://lists.openembedded.org/mt/87765279/3616873
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [changqing.li@windriver.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

[-- Attachment #2: Type: text/html, Size: 3375 bytes --]

  reply	other threads:[~2021-12-30  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 11:48 [OE-core][PATCH v2 0/2] qemu.bbclass: drop OLDEST_KERNEL reference Matt Madison
2021-12-16 11:48 ` [OE-core][PATCH v2 1/2] " Matt Madison
2021-12-30  8:51   ` Changqing Li [this message]
2021-12-30 11:06     ` Alexander Kanavin
2021-12-30 13:21     ` Richard Purdie
2021-12-31  0:50       ` Changqing Li
2021-12-16 11:48 ` [OE-core][PATCH v2 2/2] qemu: add patch to set minimum kernel version for riscv32 Matt Madison

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=3e66c6fb-b376-a292-34b1-70abdc270f41@windriver.com \
    --to=changqing.li@windriver.com \
    --cc=alex@linutronix.de \
    --cc=matt@madison.systems \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox