From: "Kavinaya S" <kavinaya@qti.qualcomm.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v5] kernel-fit-image: allow extending compatible string property for DTBs
Date: Sun, 12 Oct 2025 09:17:50 -0700 [thread overview]
Message-ID: <27294.1760285870486275177@lists.openembedded.org> (raw)
In-Reply-To: <zrwonq2yfn75ymhosfncxsrr2yqt4zbbdnllqelbea3sv577nz@nbav227oqsfx>
On Sun, Oct 12, 2025 at 08:37 PM, Dmitry Baryshkov wrote:
>
> On Sat, Oct 11, 2025 at 09:18:02PM -0700, Kavinaya S wrote:
>
> >
> > Hi Dmitry,
> >
> > If other reviewers agree I have no concern with replacement of complete
> > compatible string.
>
> Please don't trim the contents. What are you replying to? How would one
> know it?
>
> Anyway, what is the plan to handle our DTB fitImages?
>
> --
> With best wishes
> Dmitry
>
Hi Dmitry,
For Qualcomm DTBs extending the compatible string would be sufficient as the format planned is
compatible = "qcom,<SoC>[-<soc_version>][-<foundry_id>]-<board>[/<subtype>][-<pmic>][-<board_version>]"
In this "qcom,<SoC>" would be from base Kernel device tree and remaining part to be added via extension.
If others also agree to replace the entire compatible sting, then entire string can be updated in the format we like.
Either case the Qualcomm DTB fitImages have a path forward.
Thanks,
Kavinaya
next prev parent reply other threads:[~2025-10-12 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-11 9:48 [PATCH v5] kernel-fit-image: allow extending compatible string property for DTBs Kavinaya S
2025-10-11 17:32 ` Alexander Kanavin
2025-10-11 19:03 ` [OE-core] " Gyorgy Sarvari
2025-10-11 20:07 ` Dmitry Baryshkov
2025-10-12 4:18 ` Kavinaya S
2025-10-12 15:06 ` Dmitry Baryshkov
2025-10-12 16:17 ` Kavinaya S [this message]
2025-10-12 7:58 ` [OE-core] " Mathieu Dubois-Briand
2025-10-12 9:45 ` Kavinaya S
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=27294.1760285870486275177@lists.openembedded.org \
--to=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