public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Kavinaya S" <kavinaya@qti.qualcomm.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v7] kernel-fit-image: allow overriding DTB compatible string
Date: Thu, 16 Oct 2025 08:29:48 -0700	[thread overview]
Message-ID: <774.1760628588661308317@lists.openembedded.org> (raw)
In-Reply-To: <CAB3asfhhUoscOusRRkjWavdC3QvqROuo4WvZnVH2O0sCsuB1oA@mail.gmail.com>

On Wed, Oct 15, 2025 at 10:43 PM, Adrian Freihofer wrote:

>
> What I don't quite understand yet is: Does this make sense from the kernel or
> DTB perspective? Or are we circumventing problems that should be fixed on the
> kernel or DTB side instead of overriding them on the Yocto side? I mean,
> wouldn't it make more sense to assign a compatible string that is useful for
> u-boot in the DTB without requiring FIT_DTB_COMPATIBLE_OVERRIDE?
> > 
> > 
> >
>

Hi Adrian,

Thank you for all your valuable reviews and inputs. After an internal discussion with our colleagues, we feel that the proposed change does not fully align with Qualcomm’s current approach to implementing DTB-only FIT in the format expected by our UEFI bootloader. Given this, we’ve decided to hold off on upstreaming the change for now. Our plan is to first implement the DTB-only FIT support within our meta layer, refine it further, and then propose a solution to oe-core that support both kernel+DTB FIT and DTB-only FIT formats effectively.

Thanks,
Kavinaya


  reply	other threads:[~2025-10-16 15:29 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 [this message]
2025-10-20  6:28     ` Adrian Freihofer
2025-10-22 12:46       ` Viswanath Kraleti
2025-10-16  5:03 ` Mathieu Dubois-Briand

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=774.1760628588661308317@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