Support for out-of-tree device-tree while keeping customizations outside of Buildroot#7
Open
lost-byte wants to merge 1 commit intoOpenNuvoton:masterfrom
Open
Conversation
…pplied. Namely, using the BR2_LINUX_KERNEL_CUSTOM_DTS_PATH option, apply a custom device-tree file.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Buildroot manual offers two approaches to customization. One of them is changes outside of the Buildroot tree, using the br2-external mechanism.
But in the current version, the LINUX_BUILD_DTB goal recipe in linux.mk does not allow such mechanism to be used. This is also due to the fact that in the kernel source tree the device-tree files for arm64 are not located directly in the /arch/arm/boot/dts/ directory, but are distributed in folders with the manufacturer's name.
The file linux.mk changed so that the BR2_LINUX_KERNEL_CUSTOM_DTS_PATH option set for example as "$(BR2_EXTERNAL_MYBOARD_PATH)\linux\device-tree\ma35d1-myboard-256m.dts" can be proсessed correctly.