From: Miguel Gazquez <miguel.gazquez@bootlin.com>
To: Ryan Eatmon <reatmon@ti.com>, meta-ti@lists.yoctoproject.org
Cc: thomas.petazzoni@bootlin.com, praneeth@ti.com,
romain.gantois@bootlin.com, kory.maincent@bootlin.com,
thomas.bonnefille@bootlin.com, denys@konsulko.com,
robertcnelson@gmail.com
Subject: Re: [PATCH 1/2] conf: machine: add BeagleBone Green Eco to KERNEL_DEVICETREE
Date: Thu, 17 Jul 2025 19:55:19 +0200 [thread overview]
Message-ID: <53308664-c3e5-4442-9eca-3c4bce84395e@bootlin.com> (raw)
In-Reply-To: <40c291ff-c3ee-4d9f-a45a-3affb088cf7e@ti.com>
Le 15/07/2025 à 15:52, Ryan Eatmon a écrit :
>
>
> On 7/15/2025 6:34 AM, Miguel Gazquez wrote:
>> Add am335x-bonegreen-eco devicetree to KERNEL_DEVICETREE in ti33x.inc
>>
>> Signed-off-by: Miguel Gazquez <miguel.gazquez@bootlin.com>
>> ---
>> meta-ti-bsp/conf/machine/include/ti33x.inc | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/meta-ti-bsp/conf/machine/include/ti33x.inc b/meta-ti-bsp/
>> conf/machine/include/ti33x.inc
>> index
>> 7e9eb48c52737e74750565e639956334162432e2..0a0730eae104371d65548588b3333839857a3a50 100644
>> --- a/meta-ti-bsp/conf/machine/include/ti33x.inc
>> +++ b/meta-ti-bsp/conf/machine/include/ti33x.inc
>> @@ -28,6 +28,7 @@ KERNEL_DEVICETREE = " \
>> ti/omap/am335x-boneblack.dtb \
>> ti/omap/am335x-boneblue.dtb \
>> ti/omap/am335x-bonegreen-wireless.dtb \
>> + ti/omap/am335x-bonegreen-eco.dtb \
>> ti/omap/am335x-bonegreen.dtb \
>> ti/omap/am335x-chiliboard.dtb \
>> ti/omap/am335x-cm-t335.dtb \
>
> NAK. As has been mentioned several times on this list, we do not update
> KERNEL_DEVICETREE directly. As we support multiple kernel versions with
> each branch, we cannot have a single KERNEL_DEVICETREE that works for
> all kernel versions.
>
> To that end we setup the KERNEL_DEVICETREE_PREFIX variable that will
> pattern match and change the value for KERNEL_DEVICETREE based on the
> available matching DTBs in the given kernel. The only kernel version
> that uses KERNEL_DEVICETREE is the mainline (aka latest stable) kernel.
> And the value for this variable is automatically updated to include all
> of the available DTBs in the mainline kernel at the time we update the
> recipe to that version.
>
> As the KERNEL_DEVICETREE_PREFIX already has an entry that will pick up
> this new DTB when it is available, this change is not needed.
When building for the am335x_evm without this patch, the devicetree for
the beaglebone green eco is not included in the wic image, so the kernel
can't boot.
As you said, in the linux-ti-staging recipe, KERNEL_DEVICETREE does
contains the dtb for the bbg eco.
But core-image-minimal (which create the wic image) uses the value of
KERNEL_DEVICETREE from ti33x.inc, and not the one generated from
KERNEL_DEVICETREE_PREFIX, so it doesn't contains the devicetree for the
bbge. This can be checked with `bitbake-getvar -r core-image-minimal
KERNEL_DEVICETREE`.
It probably works for others boards because, apart from the bbge, there
isn't any board supported in ti-linux-6.12.y but not in mainline.
If we can't modify KERNEL_DEVICETREE here, what should I do to include
the devicetree into the final image ?
>
> Right now this new DTB is only available on linux-next and has not made
> it into any released kernels.
>
>
--
Miguel Gazquez, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-07-17 17:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 11:34 [PATCH 0/2] conf: machine: Add machine for BeagleBone Green Eco board Miguel Gazquez
2025-07-15 11:34 ` [PATCH 1/2] conf: machine: add BeagleBone Green Eco to KERNEL_DEVICETREE Miguel Gazquez
2025-07-15 13:52 ` Ryan Eatmon
2025-07-15 20:12 ` Thomas Petazzoni
2025-07-17 17:55 ` Miguel Gazquez [this message]
2025-07-17 18:01 ` Ryan Eatmon
2025-07-18 9:54 ` Miguel Gazquez
2025-07-18 14:35 ` Ryan Eatmon
2025-07-18 15:48 ` Miguel Gazquez
2025-07-21 16:49 ` Ryan Eatmon
2025-07-30 13:13 ` Miguel Gazquez
2025-07-15 11:34 ` [PATCH 2/2] conf: machine: add new BeagleBone Green Eco machine Miguel Gazquez
2025-07-15 13:52 ` Ryan Eatmon
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=53308664-c3e5-4442-9eca-3c4bce84395e@bootlin.com \
--to=miguel.gazquez@bootlin.com \
--cc=denys@konsulko.com \
--cc=kory.maincent@bootlin.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
--cc=robertcnelson@gmail.com \
--cc=romain.gantois@bootlin.com \
--cc=thomas.bonnefille@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.