Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach via buildroot <buildroot@buildroot.org>
To: Kilian Zinnecker via buildroot <buildroot@buildroot.org>
Cc: Kilian Zinnecker <kilian.zinnecker@mail.de>
Subject: Re: [Buildroot] [Help] Problem with BR2_LINUX_KERNEL_CUSTOM_DTS_PATH and kernel 6.12
Date: Wed, 01 Jan 2025 15:13:07 +0200	[thread overview]
Message-ID: <87r05mpti4.fsf@tarshish> (raw)
In-Reply-To: <6114083.lOV4Wx5bFT@kilian-laptop> (Kilian Zinnecker via buildroot's message of "Wed, 01 Jan 2025 13:59:04 +0100")

Hi Kilian,

On Wed, Jan 01 2025, Kilian Zinnecker via buildroot wrote:
> I am struggeling to get a custom device tree compiled as part of a developing 
> a board support (i.e., for the beaglev-ahead). And I suspect it might have to 
> do with a recent change to mainline kernel 6.12, which buildroot might not 
> take into account yet. Here is what I try:
>
> I add my own device tree source file into the board folder and set the 
> following lines in my defconfig:
>
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_CUSTOM_VERSION=y
> BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.12.7"
> BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG=y
> BR2_LINUX_KERNEL_DTS_SUPPORT=y
> # BR2_LINUX_KERNEL_INTREE_DTS_NAME is not set
> BR2_LINUX_KERNEL_CUSTOM_DTS_PATH="board/beaglev-ahead/beaglev-ahead.dts"
> BR2_LINUX_KERNEL_DTB_OVERLAY_SUPPORT=y
>
> Now when the kernel gets build, the Makefile throws the error, that there 
> exists no rule to build my particular dtb.

See the link below for a recent discussions of this issue on the list:

  https://lore.kernel.org/buildroot/dcbd3f77-e737-41a2-9f23-87141d0bdf9b@grenoble.cnrs.fr/

Edgar Bonet suggested a fix that you might want to test:

  https://lore.kernel.org/buildroot/035d6d78-0a31-4083-8fa1-65f5be5f74b5@grenoble.cnrs.fr/

baruch

-- 
                                                     ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2025-01-01 13:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-01 12:59 [Buildroot] [Help] Problem with BR2_LINUX_KERNEL_CUSTOM_DTS_PATH and kernel 6.12 Kilian Zinnecker via buildroot
2025-01-01 13:13 ` Baruch Siach via buildroot [this message]
2025-01-01 13:16   ` Kilian Zinnecker via buildroot
2025-01-03 14:37     ` Edgar Bonet
2025-01-04  7:22       ` Kilian Zinnecker 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=87r05mpti4.fsf@tarshish \
    --to=buildroot@buildroot.org \
    --cc=baruch@tkos.co.il \
    --cc=kilian.zinnecker@mail.de \
    /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