From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Anand Gadiyar via buildroot <buildroot@buildroot.org>
Cc: Bryan Brattlof <bb@ti.com>, Andrew Davis <afd@ti.com>,
Xuanhao Shi <X15000177@gmail.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
Romain Naour <romain.naour@gmail.com>,
Anand Gadiyar <gadiyar@ti.com>
Subject: Re: [Buildroot] [PATCH v7 2/3] boot/ti-k3-image-gen: add new package
Date: Sun, 11 Dec 2022 21:09:33 +0100 [thread overview]
Message-ID: <20221211210933.19fb5199@windsurf> (raw)
In-Reply-To: <20221206171719.747581-3-gadiyar@ti.com>
Hello,
On Tue, 6 Dec 2022 11:17:18 -0600
Anand Gadiyar via buildroot <buildroot@buildroot.org> wrote:
> From: Xuanhao Shi <x-shi@ti.com>
>
> This is the image generator that builds the full boot binary,
> tiboot3.bin, for the R5 core on TI's k3 devices.
> This requires the R5 spl output from the ti-k3-r5-loader package.
>
> https://git.ti.com/cgit/k3-image-gen/k3-image-gen
The commit title should just be:
boot/ti-k3-image-gen: new package
(not "add new package")
> diff --git a/boot/ti-k3-image-gen/Config.in b/boot/ti-k3-image-gen/Config.in
> new file mode 100644
> index 0000000000..02018f2f78
> --- /dev/null
> +++ b/boot/ti-k3-image-gen/Config.in
> @@ -0,0 +1,30 @@
> +config BR2_TARGET_TI_K3_IMAGE_GEN
> + bool "ti-k3-image-gen"
> + select BR2_TARGET_TI_K3_R5_LOADER
Should be a:
depends on BR2_TARGET_TI_K3_R5_LOADER
> +if BR2_TARGET_TI_K3_IMAGE_GEN
> +config BR2_TARGET_TI_K3_IMAGE_GEN_SOC
> + string "SOC type for image gen"
string "SoC"
> + help
> + The target SoC option for image gen.
> + For example, "am64x" for AM64X boards.
> +
> +config BR2_TARGET_TI_K3_IMAGE_GEN_SOC_TYPE
> + string "SOC security type for image gen"
string "SoC security type"
> + help
> + The security type option for image gen.
> + Options are "gp", "hs-fs", or "hs-se".
> +
> +config BR2_TARGET_TI_K3_IMAGE_GEN_CONFIG
> + string "CONFIG type for image gen"
string "config type"
> +define TI_K3_IMAGE_GEN_BUILD_CMDS
> + $(TI_K3_IMAGE_GEN_MAKE) -C $(@D) $(TI_K3_IMAGE_GEN_MAKE_OPTS)
> +endef
There is a serious problem: the build process of this package downloads
stuff:
Connecting to git.ti.com (git.ti.com)|198.47.28.208|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/blobs/raw/59d6f921b3b562e0aa1f42ce322e4645b1bfc52c/ti-sysfw/ti-sci-firmware-am64x-gp.bin [following]
--2022-12-11 20:53:58-- https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/blobs/raw/59d6f921b3b562e0aa1f42ce322e4645b1bfc52c/ti-sysfw/ti-sci-firmware-am64x-gp.bin
Reusing existing connection to git.ti.com:443.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/plain/ti-sysfw/ti-sci-firmware-am64x-gp.bin?id=59d6f921b3b562e0aa1f42ce322e4645b1bfc52c [following]
--2022-12-11 20:53:59-- https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/plain/ti-sysfw/ti-sci-firmware-am64x-gp.bin?id=59d6f921b3b562e0aa1f42ce322e4645b1bfc52c
Reusing existing connection to git.ti.com:443.
HTTP request sent, awaiting response... 200 OK
Length: 225248 (220K) [application/octet-stream]
Saving to: ‘ti-sci-firmware-am64x-gp.bin’
ti-sci-firmware-am64x-gp.bin 100%[==============================================>] 219,97K 114KB/s in 1,9s
2022-12-11 20:54:01 (114 KB/s) - ‘ti-sci-firmware-am64x-gp.bin’ saved [225248/225248]
Download SUCCESS!
This is not acceptable as it circumvents the download infrastructure of
Buildroot, but also the legal information collection infrastructure.
This needs to be fixed by downloading this file, either through a
separate package, or as an _EXTRA_DOWNLOADS of this package, and the
Makefile needs to be changed to not download this file. My impression
is that the Makefile will not download the files if they are already
available. So you could have _EXTRA_DOWNLOADS + some post-extract logic
to put the files at the right place.
Best regards,
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-12-11 20:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 17:17 [Buildroot] [PATCH v7 0/3] add support for TI's AM64x boards Anand Gadiyar via buildroot
2022-12-06 17:17 ` [Buildroot] [PATCH v7 1/3] boot/ti-k3-r5-loader: add new package Anand Gadiyar via buildroot
2022-12-06 20:18 ` François Perrad
2022-12-11 20:06 ` Thomas Petazzoni via buildroot
2022-12-06 17:17 ` [Buildroot] [PATCH v7 2/3] boot/ti-k3-image-gen: " Anand Gadiyar via buildroot
2022-12-06 20:19 ` François Perrad
2022-12-11 20:09 ` Thomas Petazzoni via buildroot [this message]
2022-12-11 20:41 ` François Perrad
2022-12-11 21:22 ` Thomas Petazzoni via buildroot
2022-12-12 22:35 ` Gadiyar, Anand via buildroot
2022-12-19 20:56 ` Julien Olivain
2022-12-06 17:17 ` [Buildroot] [PATCH v7 3/3] board/ti/am64x_sk: add new board Anand Gadiyar via buildroot
2022-12-06 20:19 ` François Perrad
2022-12-11 20:12 ` Thomas Petazzoni via buildroot
2022-12-19 21:12 ` Julien Olivain
2022-12-20 19:29 ` Gadiyar, Anand via buildroot
[not found] ` <20230608063000.882363-1-patrick.oppenlander@gmail.com>
2023-06-08 13:29 ` [Buildroot] [PATCH v7 0/3] add support for TI's AM64x boards Gadiyar, Anand via buildroot
2023-06-08 15:59 ` Andreas Dannenberg via buildroot
2023-06-13 5:56 ` Patrick Oppenlander
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=20221211210933.19fb5199@windsurf \
--to=buildroot@buildroot.org \
--cc=X15000177@gmail.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=gadiyar@ti.com \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.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