From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Bryan Brattlof <bb@ti.com>
Cc: Xuanhao Shi <X15000177@gmail.com>,
Paresh Bhagat <p-bhagat@ti.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] boot/ti-k3-r5-loader: share download files with uboot
Date: Fri, 7 Jun 2024 22:50:52 +0200 [thread overview]
Message-ID: <ZmNyrBsiNN-QGXdA@landeda> (raw)
In-Reply-To: <20240607203427.feo5giguhthammt2@bryanbrattlof.com>
Bryan, All,
On 2024-06-07 15:34 -0500, Bryan Brattlof via buildroot spake thusly:
> On June 7, 2024 thus sayeth Yann E. MORIN:
[--SNIP--]
> > Oh, so would it make sense to completely drop that big choice, and just
> > always use the same version as uboot, always?
[--SNIP--]
> There is the falcon mode option but I haven't typed out the support for
> any K3 SoCs yet (on my to-do soon list) and I haven't seen anyone use a
> separate fitimage made outside of U-Boot for falcon mode. But that
> doesn't eliminate the possibility of a future package being introduced
> to do that.
Thanks for the interesting feedback. 👍
> If you're OK with it, I would probably make ti-k3-r5-loader/ depend on
> uboot/ and tie the versions together until that mythical falcon mode
> package arrives.
Yes, please. Beware that you'll need to be careful on what variables you
evaluate and when:
- some variables are used to define make dependencies; e.g. _VERSION;
- uboot sorts after ti-k3-r5-loader, so you can't rely on variables
that are _computed_ in uboot.mk, but only on those that come from
Kconfig;
- variables that are evaluated in _CMD blocks can be anything, because
those are evaluated 'late'.
I would direct you to the doc about that, if there was one... :-(
I think _VERSION is the only that really matters, though, but look at
how it's done for linux-headers vs linux, this is the kind of ugliness
will need here too.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-06-07 20:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 9:37 [Buildroot] [PATCH] boot/ti-k3-r5-loader: share download files with uboot Yann E. MORIN
2024-06-07 17:26 ` Bryan Brattlof via buildroot
2024-06-07 18:10 ` Yann E. MORIN
2024-06-07 19:06 ` Bryan Brattlof via buildroot
2024-06-07 19:19 ` Yann E. MORIN
2024-06-07 20:34 ` Bryan Brattlof via buildroot
2024-06-07 20:50 ` Yann E. MORIN [this message]
2024-07-12 15:39 ` Romain Naour via buildroot
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=ZmNyrBsiNN-QGXdA@landeda \
--to=yann.morin.1998@free.fr \
--cc=X15000177@gmail.com \
--cc=bb@ti.com \
--cc=buildroot@buildroot.org \
--cc=p-bhagat@ti.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