From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <kavinaya@qti.qualcomm.com>, <openembedded-core@lists.openembedded.org>
Cc: "Alexander Kanavin" <alex.kanavin@gmail.com>,
"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [OE-core] [PATCH v7] kernel-fit-image: allow overriding DTB compatible string
Date: Thu, 16 Oct 2025 07:03:12 +0200 [thread overview]
Message-ID: <DDJHF42PN7TW.3M8KTUFHDD38C@bootlin.com> (raw)
In-Reply-To: <20251015080502.1704801-1-kavinaya@qti.qualcomm.com>
On Wed Oct 15, 2025 at 10:05 AM CEST, Kavinaya S via lists.openembedded.org wrote:
> The Linux kernel allows multiple DTBs to share the same compatible string.
> For example:
> qcs6490-rb3gen2.dtb
> qcs6490-rb3gen2-vision-mezzanine.dtb
> qcs6490-rb3gen2-industrial-mezzanine.dtb
>
> All of these use the same base compatible string:
> compatible = "qcom,qcs6490-rb3gen2", "qcom,qcm6490";
>
> Since the latter two DTBs are overlays on top of the base DTB and do not
> modify platform properties, they retain the same compatible string.
>
> When these DTBs are bundled into a single fitImage, the bootloader cannot
> distinguish between them due to identical compatible strings.
>
> To address this, introduce a mechanism to override the compatible string
> using a BitBake variable:
> FIT_DTB_COMPATIBLE_OVERRIDE[<dtb_name>] = "<compatible_string>"
>
> This overrides the compatible string generated resulting in unique entries in the
> generated .its file. For example:
> FIT_DTB_COMPATIBLE_OVERRIDE[qcs6490-rb3gen2-vision-mezzanine] = "qcom,qcs6490-rb3gen2-vision"
> FIT_DTB_COMPATIBLE_OVERRIDE[qcs6490-rb3gen2-vision-mezzanine] = "qcom,qcs6490-rb3gen2-vision qcom,qcm6490"
>
> Results in:
>
> compatible = "qcom,qcs6490-rb3gen2-vision";
> compatible = "qcom,qcs6490-rb3gen2-vision", "qcom,qcm6490";
>
> Suggested-By: Alexander Kanavin <alex.kanavin@gmail.com>
> Suggested-By: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> Signed-off-by: Kavinaya S <kavinaya@qti.qualcomm.com>
> ---
Hi Kavinaya,
Thanks for the new version. However, I still got a similar issue:
ERROR: linux-yocto-6.16.9+git-r0 do_compile: Execution of '/srv/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-1723335/tmp/work/qemuarm64-poky-linux/linux-yocto/6.16.9+git/temp/run.do_compile.365769' failed with exit code 1
...
| make[2]: *** No rule to make target 'arch/arm64/boot/dts/am335x-bonegreen-ext.dtb'. Stop.
https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/2701
https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/2549
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/2463
Can you have a look at this please?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-10-16 5:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 8:05 [PATCH v7] kernel-fit-image: allow overriding DTB compatible string Kavinaya S
2025-10-15 17:13 ` [OE-core] " Adrian Freihofer
2025-10-16 15:29 ` Kavinaya S
2025-10-20 6:28 ` [OE-core] " Adrian Freihofer
2025-10-22 12:46 ` Viswanath Kraleti
2025-10-16 5:03 ` Mathieu Dubois-Briand [this message]
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=DDJHF42PN7TW.3M8KTUFHDD38C@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=alex.kanavin@gmail.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=kavinaya@qti.qualcomm.com \
--cc=openembedded-core@lists.openembedded.org \
/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