From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Xuanhao Shi <x-shi@ti.com>
Cc: Suniel Mahesh <sunil@amarulasolutions.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/4] package/k3-image-gen: new package
Date: Tue, 26 Jul 2022 23:07:42 +0200 [thread overview]
Message-ID: <20220726230742.0e538187@windsurf> (raw)
In-Reply-To: <8d1611db-29ae-e53b-f900-f57c037cfd01@ti.com>
Hello,
On Tue, 26 Jul 2022 15:56:31 -0500
Xuanhao Shi <x-shi@ti.com> wrote:
> > Could you explain what you are trying to do? Is it because you need to
> > build two different U-Boot configurations?
>
> Yes, the R5 core requires a different U-Boot build than the A53 core. I
> mentioned a bit about it above.
>
> I understood that this patch currently does not achieve that in a proper
> way. Would you mind recommending a proper way to do this? Should I find
> a way to patch U-Boot directly so it has an option for a separate build?
>
> Since you mentioned earlier that k3-image-gen should be a package in
> boot/, should the patch modify boot/uboot/ for the separate U-Boot build
> instead?
One option that I see, which isn't very nice, is to do like Barebox in
boot/barebox/, where boot/barebox/barebox.mk contains most of the code,
but in fact two barebox packages exist, boot/barebox/barebox/ and
boot/barebox/barebox-aux/.
Another option, much simpler, is to do something that is more TI
specific, such as a ti-am64x-r5-loader package that would download your
U-Boot for R5 and build it, but without relying on the boot/uboot/
package. Exactly like if you had a custom bootloader/firmware for the
R5. I think this is the best option.
What do you think?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-26 21:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 16:50 [Buildroot] [PATCH 0/4] add support for TI's AM6X SoCs Xuanhao Shi via buildroot
2022-07-26 16:50 ` [Buildroot] [PATCH 1/4] package/arm-gnu-toolchain: add version selection Xuanhao Shi via buildroot
2022-07-26 17:37 ` Thomas Petazzoni via buildroot
2022-07-26 19:32 ` Xuanhao Shi via buildroot
2022-07-26 20:07 ` Thomas Petazzoni via buildroot
2022-07-26 21:29 ` Xuanhao Shi via buildroot
2022-07-26 16:50 ` [Buildroot] [PATCH 2/4] package/k3-image-gen: new package Xuanhao Shi via buildroot
2022-07-26 18:55 ` Thomas Petazzoni via buildroot
2022-07-26 20:56 ` Xuanhao Shi via buildroot
2022-07-26 21:07 ` Thomas Petazzoni via buildroot [this message]
2022-07-26 21:31 ` Xuanhao Shi via buildroot
2022-07-27 8:22 ` Arnout Vandecappelle
2022-07-26 16:50 ` [Buildroot] [PATCH 3/4] board/am6x: add new board support Xuanhao Shi via buildroot
2022-07-26 18:58 ` Thomas Petazzoni via buildroot
2022-07-26 21:08 ` Xuanhao Shi via buildroot
2022-07-27 8:32 ` Arnout Vandecappelle
2022-07-26 16:50 ` [Buildroot] [PATCH 4/4] configs/am64x_sk_defconfig: add new defconfig Xuanhao Shi via buildroot
2022-07-26 19:00 ` Thomas Petazzoni via buildroot
2022-07-26 21:11 ` Xuanhao Shi 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=20220726230742.0e538187@windsurf \
--to=buildroot@buildroot.org \
--cc=sunil@amarulasolutions.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=x-shi@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