From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 8/9] meta-isar: linux-mainline: Update to 6.6.9
Date: Tue, 2 Jan 2024 11:08:28 +0100 [thread overview]
Message-ID: <baffabe907e50805f05483bf83a676f0a3f8a8dc.1704190109.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1704190109.git.jan.kiszka@siemens.com>
From: Jan Kiszka <jan.kiszka@siemens.com>
This will allow to use the mainline kernel also on the VisionFive 2.
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
.../{linux-mainline_5.4.203.bb => linux-mainline_6.6.9.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename meta-isar/recipes-kernel/linux/{linux-mainline_5.4.203.bb => linux-mainline_6.6.9.bb} (85%)
diff --git a/meta-isar/recipes-kernel/linux/linux-mainline_5.4.203.bb b/meta-isar/recipes-kernel/linux/linux-mainline_6.6.9.bb
similarity index 85%
rename from meta-isar/recipes-kernel/linux/linux-mainline_5.4.203.bb
rename to meta-isar/recipes-kernel/linux/linux-mainline_6.6.9.bb
index 47270cbb..c8c5d55f 100644
--- a/meta-isar/recipes-kernel/linux/linux-mainline_5.4.203.bb
+++ b/meta-isar/recipes-kernel/linux/linux-mainline_6.6.9.bb
@@ -1,7 +1,7 @@
# Example recipe for building the mainline kernel
#
# This software is a part of ISAR.
-# Copyright (c) Siemens AG, 2018-2020
+# Copyright (c) Siemens AG, 2018-2024
#
# SPDX-License-Identifier: MIT
@@ -10,13 +10,13 @@ require recipes-kernel/linux/linux-custom.inc
ARCHIVE_VERSION = "${@ d.getVar('PV')[:-2] if d.getVar('PV').endswith('.0') else d.getVar('PV') }"
SRC_URI += " \
- https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-${ARCHIVE_VERSION}.tar.xz \
+ https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-${ARCHIVE_VERSION}.tar.xz \
file://x86_64_defconfig \
file://ftpm-module.cfg \
file://subdir/no-ubifs-fs.cfg \
file://no-root-nfs.cfg;apply=no"
-SRC_URI[sha256sum] = "fc933f5b13066cfa54aacb5e86747a167bad1d8d23972e4a03ab5ee36c29798a"
+SRC_URI[sha256sum] = "8ebc65af0cfc891ba63dce0546583da728434db0f5f6a54d979f25ec47f548b3"
S = "${WORKDIR}/linux-${ARCHIVE_VERSION}"
--
2.35.3
next prev parent reply other threads:[~2024-01-02 10:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 10:08 [PATCH 0/9] Restore cross-build for RISC-V, update VisionFive 2 Jan Kiszka
2024-01-02 10:08 ` [PATCH 1/9] crossvars: Account for PACKAGE_ARCH = "${BUILD_ARCH}" Jan Kiszka
2024-01-02 10:08 ` [PATCH 2/9] Add workaround for cross-building riscv64 Jan Kiszka
2024-01-08 17:31 ` Jan Kiszka
2024-01-02 10:08 ` [PATCH 3/9] meta-isar: jh7110-u-boot-spl-tool: Use BPN instead of PN Jan Kiszka
2024-01-02 10:08 ` [PATCH 4/9] meta-isar: starfive-visionfive2: Use kernel DTB Jan Kiszka
2024-01-02 10:08 ` [PATCH 5/9] meta-isar: jh7110-u-boot-spl-tool: Rework Jan Kiszka
2024-01-02 10:08 ` [PATCH 6/9] meta-isar: starfive-visionfive2: Switch to upstream U-Boot Jan Kiszka
2024-01-02 10:08 ` [PATCH 7/9] meta-isar: starfive-visionfive2: Drop obsolete recipes Jan Kiszka
2024-01-02 10:08 ` Jan Kiszka [this message]
2024-01-02 10:08 ` [PATCH 9/9] meta-isar: Switch VisionFive 2 to mainline kernel Jan Kiszka
2024-01-03 16:39 ` [PATCH 0/9] Restore cross-build for RISC-V, update VisionFive 2 Jan Kiszka
2024-01-05 15:45 ` Anton Mikanovich
2024-01-05 21:19 ` Jan Kiszka
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=baffabe907e50805f05483bf83a676f0a3f8a8dc.1704190109.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
/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