From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6541ECAC5BB for ; Wed, 8 Oct 2025 18:04:03 +0000 (UTC) Subject: Re: [PATCH v4 1/1] fitimage: Add support for custom compatible string via optional parameter To: openembedded-core@lists.openembedded.org From: "Kavinaya S" X-Originating-Location: Mumbai, Maharashtra, IN (163.116.213.159) X-Originating-Platform: Windows Chrome 141 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Wed, 08 Oct 2025 11:03:57 -0700 References: In-Reply-To: Message-ID: <10142.1759946637705390547@lists.openembedded.org> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Wed, 08 Oct 2025 18:04:03 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/224586 On Mon, Oct 6, 2025 at 04:04 AM, Dmitry Baryshkov wrote: > > In which cases? Could you please be more specific here? > One case in Qualcomm DTBs is, both 'qcs6490-rb3gen2-vision-mezzanine.dtb' &= 'qcs6490-rb3gen2-industrial-mezzanine.dtb' are going to have same compatib= le string even though the overlays applied are different. When they are pac= ked into a single FIT Image, it is not possible to distinguish between them= just by reading compatible string. Same is the case with 'apq8016-sbc-d3-c= amera-mezzanine.dtb' & 'apq8016-sbc-usb-host.dtb' as well.