From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Bajjuri Praneeth <praneeth@ti.com>, Bryan Brattlof <bb@ti.com>,
Lothar Felten <lothar.felten@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] configs/beaglebone: Bump to Linux mainline
Date: Fri, 12 Dec 2025 11:24:08 +0100 [thread overview]
Message-ID: <20251212112408.3e3b5b14@windsurf> (raw)
In-Reply-To: <20251212101533.820554-2-kory.maincent@bootlin.com>
Hello,
On Fri, 12 Dec 2025 10:15:28 +0000
Kory Maincent <kory.maincent@bootlin.com> wrote:
> diff --git a/configs/beaglebone_defconfig b/configs/beaglebone_defconfig
> index 86bf6bce9a..b27b97916e 100644
> --- a/configs/beaglebone_defconfig
> +++ b/configs/beaglebone_defconfig
> @@ -1,7 +1,6 @@
> BR2_arm=y
> BR2_cortex_a8=y
> BR2_ARM_FPU_VFPV3=y
> -BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_12=y
This needs to be kept, but adjusted to the kernel version used.
> BR2_GLOBAL_PATCH_DIR="board/beagleboard/beaglebone/patches"
> BR2_DOWNLOAD_FORCE_CHECK_HASHES=y
> BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_MDEV=y
> @@ -9,9 +8,8 @@ BR2_ROOTFS_POST_BUILD_SCRIPT="board/beagleboard/beaglebone/post-build.sh"
> BR2_ROOTFS_POST_IMAGE_SCRIPT="support/scripts/genimage.sh"
> BR2_ROOTFS_POST_SCRIPT_ARGS="-c board/beagleboard/beaglebone/genimage.cfg"
> BR2_LINUX_KERNEL=y
> -BR2_LINUX_KERNEL_CUSTOM_TARBALL=y
> -BR2_LINUX_KERNEL_CUSTOM_TARBALL_LOCATION="$(call github,beagleboard,linux,6.12.34-ti-arm32-r12)/linux-6.12.34-ti-arm32-r12.tar.gz"
> -BR2_LINUX_KERNEL_DEFCONFIG="bb.org"
> +BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
> +BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="board/ti/common/am335x/linux.config"
You can't do this: you need to specify a specific kernel version.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-12-12 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 10:15 [Buildroot] [PATCH 0/3] Add support for BeagleBone Green Eco board Kory Maincent via buildroot
2025-12-12 10:15 ` [Buildroot] [PATCH 1/3] configs/beaglebone: Bump to Linux mainline Kory Maincent via buildroot
2025-12-12 10:24 ` Thomas Petazzoni via buildroot [this message]
2025-12-12 10:42 ` Kory Maincent via buildroot
2025-12-12 10:15 ` [Buildroot] [PATCH 2/3] configs/beaglebone: Use Buildroot's default U-Boot version Kory Maincent via buildroot
2025-12-12 10:24 ` Thomas Petazzoni via buildroot
2025-12-12 10:15 ` [Buildroot] [PATCH 3/3] board/beaglebone: Add BeagleBone Green Eco support Kory Maincent via buildroot
2025-12-12 10:25 ` Thomas Petazzoni via buildroot
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=20251212112408.3e3b5b14@windsurf \
--to=buildroot@buildroot.org \
--cc=bb@ti.com \
--cc=kory.maincent@bootlin.com \
--cc=lothar.felten@gmail.com \
--cc=praneeth@ti.com \
--cc=thomas.petazzoni@bootlin.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