From: kavinaya@qti.qualcomm.com
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] kernel-fitimage: add support for custom ITS file override
Date: Thu, 25 Sep 2025 20:42:20 -0700 [thread overview]
Message-ID: <27560.1758858140781391880@lists.openembedded.org> (raw)
In-Reply-To: <29002.1758707163729683981@lists.openembedded.org>
Hi Adrian,
Thanks for your question. To clarify:
We are not hardcoding anything or bypassing upstream logic. All BitBake variables and artifact handling remain unchanged. The only difference is that if FIT_CUSTOM_ITS_FILE is set, we use that file instead of generating one dynamically.
This ensures we still rely on the existing process for preparing kernel, DTBs, and other artifacts.
Regarding extending the ITS generator: yes, we considered it, but our required compatible string format is very specific and would need major changes to the generator, adding complexity and maintenance overhead. Using a custom ITS file is simpler, low-impact, and keeps upstream behavior intact while meeting our UEFI compatibility needs.
Let me know if you’d like more details or if you see a better alternative.
Thanks,
Kavinaya
next prev parent reply other threads:[~2025-09-26 3:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250919073335.2069114-1-kavinaya@qti.qualcomm.com>
2025-09-19 7:33 ` [PATCH 1/2] kernel-fitimage: add support for custom ITS file override Kavinaya S
2025-09-21 11:40 ` [OE-core] " Freihofer, Adrian
2025-09-22 8:41 ` kavinaya
2025-09-22 9:58 ` [OE-core] " Alexander Kanavin
[not found] ` <1867495AF42A64B8.23261@lists.openembedded.org>
2025-09-22 20:58 ` Freihofer, Adrian
2025-09-24 8:30 ` kavinaya
2025-09-24 9:46 ` kavinaya
2025-09-26 3:42 ` kavinaya [this message]
2025-09-26 7:31 ` [OE-core] " Alexander Kanavin
2025-09-29 14:26 ` kavinaya
2025-09-19 7:33 ` [PATCH 2/2] image-fitimage.conf: introduce CUSTOM_ITS_FILE variable Kavinaya S
2025-09-22 9:44 ` [OE-core] " Alexander Kanavin
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=27560.1758858140781391880@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 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.