Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <zajec5@gmail.com>
To: buildroot@buildroot.org
Cc: "Rafał Miłecki" <rafal@milecki.pl>
Subject: [Buildroot] [PATCH] configs/broadcom_northstar_defconfig: specify kernel & headers versions
Date: Wed,  3 Jan 2024 07:33:01 +0100	[thread overview]
Message-ID: <20240103063301.6858-1-zajec5@gmail.com> (raw)

From: Rafał Miłecki <rafal@milecki.pl>

Even though Northstart platform support is well upstreamed it may always
happen that some kernel change affects/breaks something. It's a good
practice to specify fixed versions for kernel & Linux headers.

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
---
 configs/broadcom_northstar_defconfig | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/configs/broadcom_northstar_defconfig b/configs/broadcom_northstar_defconfig
index 9ae716726d..bbd368ac79 100644
--- a/configs/broadcom_northstar_defconfig
+++ b/configs/broadcom_northstar_defconfig
@@ -1,7 +1,10 @@
 BR2_arm=y
 BR2_cortex_a9=y
+BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_6=y
 BR2_ROOTFS_POST_IMAGE_SCRIPT="board/broadcom/northstar/post-image.sh"
 BR2_LINUX_KERNEL=y
+BR2_LINUX_KERNEL_CUSTOM_VERSION=y
+BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.6.9"
 BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
 BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/broadcom/northstar/linux.config"
 BR2_LINUX_KERNEL_APPENDED_ZIMAGE=y
-- 
2.35.3

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2024-01-03  6:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  6:33 Rafał Miłecki [this message]
2024-01-13 20:53 ` [Buildroot] [PATCH] configs/broadcom_northstar_defconfig: specify kernel & headers versions Peter Korsgaard

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=20240103063301.6858-1-zajec5@gmail.com \
    --to=zajec5@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=rafal@milecki.pl \
    /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