All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ross Burton" <ross@burtonini.com>
To: meta-arm@lists.yoctoproject.org
Subject: [PATCH][gatesgarth] arm/qemuarm64-secureboot: don't use -dev kernel
Date: Thu, 10 Dec 2020 14:26:58 +0000	[thread overview]
Message-ID: <20201210142658.1499868-1-ross.burton@arm.com> (raw)

From: Ross Burton <ross@burtonini.com>

According to the comment linux-yocto-dev was being used to get a 5.5
kernel as 5.4 was panicking on boot.  Now linux-yocto defaults to 5.8
so just use the standard kernel instead.

Change-Id: Id382c69f16f2ff4b2cbc63be94a645e56616549d
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Jon Mason <jon.mason@arm.com>
---
 meta-arm/conf/machine/qemuarm64-secureboot.conf | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/meta-arm/conf/machine/qemuarm64-secureboot.conf b/meta-arm/conf/machine/qemuarm64-secureboot.conf
index f2c15e6..fe19ed2 100644
--- a/meta-arm/conf/machine/qemuarm64-secureboot.conf
+++ b/meta-arm/conf/machine/qemuarm64-secureboot.conf
@@ -6,10 +6,6 @@ KMACHINE = "qemuarm64"
 
 UBOOT_MACHINE = "qemu_arm64_defconfig"
 
-# The 5.4 kernel panics when booting, so use the development kernel until the
-# default kernel is upgraded (5.5. supposedly works)
-PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-dev"
-
 QB_MACHINE = "-machine virt,secure=on"
 QB_OPT_APPEND += "-no-acpi"
 QB_MEM = "-m 1024"
@@ -23,4 +19,3 @@ IMAGE_FSTYPES += "wic wic.qcow2"
 WKS_FILE ?= "qemuarm64.wks"
 WKS_FILE_DEPENDS = "trusted-firmware-a"
 IMAGE_BOOT_FILES = "${KERNEL_IMAGETYPE}"
-
-- 
2.25.1


             reply	other threads:[~2020-12-10 14:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-10 14:26 Ross Burton [this message]
2020-12-11 16:34 ` [meta-arm] [PATCH][gatesgarth] arm/qemuarm64-secureboot: don't use -dev kernel Jon Mason

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=20201210142658.1499868-1-ross.burton@arm.com \
    --to=ross@burtonini.com \
    --cc=meta-arm@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.