Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 21:19:10 +0200	[thread overview]
Message-ID: <ZmNdLpmIeiA83M9B@landeda> (raw)
In-Reply-To: <20240607190634.salcy2c3jnpjzs57@bryanbrattlof.com>

Bryan, All,

On 2024-06-07 14:06 -0500, Bryan Brattlof spake thusly:
> On June  7, 2024 thus sayeth Yann E. MORIN:
> > Of course, now I notice that the two defconfigs use the same versions
> > for uboot and ti-k3-r5-loader. Which got me thinking that maybe we
> > should make that explicit (and easier!) in the menuconfig:
[--SNIP--]
> > And then with a bit of sorcey/trickery in ti-k3-r5-loader (like we have
> > in package/linux-headers for example) to handle the same-as case.
> Ah Ok! Ideally they should never be different as it can only lead to 
> hard to debug issues between the jump from tiboot3.bin to tispl.bin with 
> vague error messages or no message at all. It's unfortunate that we even 
> have the ability to select a version which can be different from uboot/
> 
> IMHO the K3 boot is complicated enough even without the ability to have 
> different U-Boot version thrown into the mix. :) 

Oh, so would it make sense to completely drop that big choice, and just
always use the same version as uboot, always?

But nowadays, it is possible to enable ti-k3-r5-loader even when uboot
is not enabled. Does that even make sense, or should we tie
ti-k3-r5-loader to depend on uboot?

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

  reply	other threads:[~2024-06-07 19:19 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 [this message]
2024-06-07 20:34         ` Bryan Brattlof via buildroot
2024-06-07 20:50           ` Yann E. MORIN
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=ZmNdLpmIeiA83M9B@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