From: Francesco Valla <francesco@valla.it>
To: Antonin Godard <antonin.godard@bootlin.com>
Cc: Trevor Gamblin <tgamblin@baylibre.com>,
openembedded-core@lists.openembedded.org,
Adrian Freihofer <adrian.freihofer@siemens.com>,
Marek Vasut <marek.vasut@mailbox.org>,
Michael Opdenacker <michael.opdenacker@rootcommit.com>
Subject: Re: [OE-core] [PATCH v2] kernel-fit-image: support arbitrary loadables
Date: Fri, 27 Mar 2026 10:02:25 +0100 [thread overview]
Message-ID: <acZGz-B14OB7ugyL@bywater> (raw)
In-Reply-To: <DHDFDB6KCDMU.LLC8N7SBMK6H@bootlin.com>
Hi Antonin,
On Fri, Mar 27, 2026 at 09:34:42AM +0100, Antonin Godard wrote:
> Hi,
>
> On Tue Mar 3, 2026 at 9:30 PM CET, Francesco Valla via lists.openembedded.org wrote:
> [...]
> >> Thanks for submitting this. LGTM, but it'd be nice to have it
> >> documented as well.
> >>
> >> Could you add some details to the Yocto Project docs (e.g. in the
> >> "Variables Glossary" section) and submit it to
> >> docs@lists.yoctoproject.org?
> >
> > Yes, documentation here is pretty much necessary to understand how this
> > shall be used.
> > I'll work on it as soon as possible.
>
> Did you manage to come up with some documentation for this? I am catching up
> with the latest changes from OE-Core and this appears to be missing.
>
Uhm, I sent it twice to the list actually, without any reply. But... it
just occurred to me that I'm not subscribed to that list, so maybe my
message was droppe without notice?
I'll subscribe and resend in a couple of hours. Apologies.
> As a starting point, we'd need documentation for the following variable in
> https://git.yoctoproject.org/yocto-docs/tree/documentation/ref-manual/variables.rst:
>
> FIT_LOADABLES
> FIT_LOADABLE_FILENAME
> FIT_LOADABLE_TYPE
> FIT_LOADABLE_ARCH
> FIT_LOADABLE_OS
> FIT_LOADABLE_LOADADDRESS
>
> And an update to the class' documentation here:
> https://git.yoctoproject.org/yocto-docs/tree/documentation/ref-manual/classes.rst?id=5bfe4f9aecf542766dec727bedbb30b1f93ab64a#n1419
>
> I think the key point is to show how these variables are translated into the fit
> node. I think an example in the class documentation would be great for that.
>
> These should be sent to docs@lists.yoctoproject.org.
>
> Let me know if I can be of any help.
>
> Thanks!
> Antonin
Regards,
Francesco
next prev parent reply other threads:[~2026-03-27 9:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 21:17 [PATCH v2] kernel-fit-image: support arbitrary loadables Francesco Valla
2026-03-02 18:00 ` [OE-core] " Trevor Gamblin
2026-03-03 20:30 ` Francesco Valla
2026-03-27 8:34 ` Antonin Godard
2026-03-27 9:02 ` Francesco Valla [this message]
2026-03-27 9:14 ` Antonin Godard
2026-03-03 20:41 ` Francesco Valla
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=acZGz-B14OB7ugyL@bywater \
--to=francesco@valla.it \
--cc=adrian.freihofer@siemens.com \
--cc=antonin.godard@bootlin.com \
--cc=marek.vasut@mailbox.org \
--cc=michael.opdenacker@rootcommit.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tgamblin@baylibre.com \
/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