Skip to contentSkip to conversation

inquiry | configuring for a specific linux lts

Buildroot Andreas Ziegler 1 participant 1 message Jun 16, 2024 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi James,

also probably not what you are looking for; and does not incorporate the hash topic, since I use CUSTOM_KERNEL_VERSION ...

Quoted 15 lines · James Knight

Trying to figure out the best way with Buildroot to target a specific Linux LTS branch for images. At this time, using a setup that has an external toolchain build (v6.6.x Linux headers) and inside each project configurations a BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE option is specified to a value of (for example) 6.6.32. As Buildroot evolves, it may update its own configuration and Linux hashes to a more recent version (e.g. v6.6.33). In turn, when updating the Buildroot version to use, there is a need to update all configurations to use the most recent LTS version.

I am looking for a capability somewhat provided by the existing BR2_LINUX_KERNEL_LATEST_VERSION option, but targeting a specific LTS version. For example:

Quoted 8 lines
    BR2_LINUX_KERNEL_LATEST_VERSION
    BR2_LINUX_KERNEL_LATEST_LTS_0606_VERSION
    BR2_LINUX_KERNEL_LATEST_LTS_0601_VERSION
    BR2_LINUX_KERNEL_LATEST_LTS_0516_VERSION
    ...

Then these configurations can use whatever the latest LTS version of a configured major-minor without updating.

I used to use a script to bulk-replace specific kernel versions, but recently switched to a few definitions in BR2_EXTERNAL/Config.in:

# latest release candidate
if BR2_TOOLCHAIN_HEADERS_LATEST

config NABLA_LINUX_VERSION

	string
	default "6.10-rc3"

config NABLA_LINUX_PATCH
string
default
"https://mirrors.edge.kernel.org/pub/linux/kernel/projects/rt/6.10/patch-6.10-rc3-rt5.patch.xz"

endif # BR2_TOOLCHAIN_HEADERS_LATEST

# stable kernel for 64-bit systems
if BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_6 && (BR2_aarch64 || BR2_x86_64)

config NABLA_LINUX_VERSION

	string
	default "6.6.33"

config NABLA_LINUX_PATCH
string
default
"https://mirrors.edge.kernel.org/pub/linux/kernel/projects/rt/6.6/patch-6.6.32-rt32.patch.xz"

endif # BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_6_6

# stable kernel for older architectures
if BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_10 && BR2_i386

config NABLA_LINUX_VERSION

	string
	default "5.10.218" if BR2_i386

config NABLA_LINUX_PATCH
string
default
"https://mirrors.edge.kernel.org/pub/linux/kernel/projects/rt/5.10/patch-5.10.218-rt110.patch.xz"

endif # BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_5_10

Variables are referred in the project configuration:

BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="$(NABLA_LINUX_VERSION)" BR2_LINUX_KERNEL_PATCH="$(NABLA_LINUX_PATCH)"

Not elegant, but at least allows central management of the kernel version(s) for all projects.

Kind regards,
Andreas

Quoted 8 lines

I imagine this may not be implemented since these additional configuration options may be a bit too much to maintain. Assuming such an approach is not desired, I wonder if it may be possible to support a BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE option where users can define a value such as 6.6. (or 6.6.x or whatever) and have Buildroot use whatever the most recent version it "supports" (e.g. has a hash reference).

Quoted 7 lines

For now, it seems the tasks needed to handle an updated Buildroot framework with a custom Linux version is to first have projects track/patch the hash version of Linux any time a custom version is set; and update both the version and patch-hash in a board configuration when wanting to update.

If I am overlooking another way to approach this, please let me know.

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot