From: Denys Dmytriyenko <denis@denix.org>
To: afd@ti.com
Cc: Denys Dmytriyenko <denys@konsulko.com>,
Ryan Eatmon <reatmon@ti.com>, Praneeth Bajjuri <praneeth@ti.com>,
Neha Malcom Francis <n-francis@ti.com>,
meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master/kirkstone][RFC 4/9] u-boot-bb.org: Remove this recipe
Date: Thu, 27 Apr 2023 16:31:08 -0400 [thread overview]
Message-ID: <20230427203108.GO9226@denix.org> (raw)
In-Reply-To: <20230425172345.12293-5-afd@ti.com>
On Tue, Apr 25, 2023 at 12:23:40PM -0500, Andrew Davis via lists.yoctoproject.org wrote:
> This will no longer build after we switch away from k3-image-gen. Remove
> this version until it can be rebased on the latest U-Boot with binman
> support.
> For now switch current users of this over to u-boot-ti v2021.01.
This comment is not very clear - aren't you also removing that here?
Would it be possible to preserve at least Beagle build flows intact? Can
the existing ti-sci-fw recipe that uses k3-image-gen be kept for now
alongside the new one, e.g. move it to ti-sci-fw-legacy or something?
> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
> meta-ti-bsp/conf/machine/beagle-x15.conf | 2 --
> .../conf/machine/beaglebone-ai64-k3r5.conf | 3 ---
> meta-ti-bsp/conf/machine/beaglebone-ai64.conf | 2 --
> meta-ti-bsp/conf/machine/beaglebone.conf | 2 --
> meta-ti-bsp/conf/machine/beagleplay-k3r5.conf | 3 ---
> meta-ti-bsp/conf/machine/beagleplay.conf | 2 --
> .../recipes-bsp/u-boot/u-boot-bb.org_git.bb | 24 -------------------
> 7 files changed, 38 deletions(-)
> delete mode 100644 meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb
>
> diff --git a/meta-ti-bsp/conf/machine/beagle-x15.conf b/meta-ti-bsp/conf/machine/beagle-x15.conf
> index fb52245b..be27705c 100644
> --- a/meta-ti-bsp/conf/machine/beagle-x15.conf
> +++ b/meta-ti-bsp/conf/machine/beagle-x15.conf
> @@ -5,8 +5,6 @@
> require conf/machine/include/am57xx.inc
>
> PREFERRED_PROVIDER_virtual/kernel = "linux-bb.org"
> -PREFERRED_PROVIDER_virtual/bootloader = "u-boot-bb.org"
> -PREFERRED_PROVIDER_u-boot = "u-boot-bb.org"
>
> KERNEL_DEVICETREE_PREFIX = "am57xx-beagle-x15"
>
> diff --git a/meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf b/meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf
> index 7c99b5d4..b893f380 100644
> --- a/meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf
> +++ b/meta-ti-bsp/conf/machine/beaglebone-ai64-k3r5.conf
> @@ -4,9 +4,6 @@
>
> require conf/machine/include/k3r5.inc
>
> -PREFERRED_PROVIDER_virtual/bootloader = "u-boot-bb.org"
> -PREFERRED_PROVIDER_u-boot = "u-boot-bb.org"
> -
> SYSFW_SOC = "j721e"
> SYSFW_CONFIG = "evm"
> SYSFW_SUFFIX = "gp"
> diff --git a/meta-ti-bsp/conf/machine/beaglebone-ai64.conf b/meta-ti-bsp/conf/machine/beaglebone-ai64.conf
> index 304cbb62..bd5f541f 100644
> --- a/meta-ti-bsp/conf/machine/beaglebone-ai64.conf
> +++ b/meta-ti-bsp/conf/machine/beaglebone-ai64.conf
> @@ -7,8 +7,6 @@ require conf/machine/include/j721e.inc
> UBOOT_MACHINE = "j721e_evm_a72_config"
>
> PREFERRED_PROVIDER_virtual/kernel = "linux-bb.org"
> -PREFERRED_PROVIDER_virtual/bootloader = "u-boot-bb.org"
> -PREFERRED_PROVIDER_u-boot = "u-boot-bb.org"
>
> KERNEL_DEVICETREE = " \
> ti/k3-j721e-beagleboneai64.dtb \
> diff --git a/meta-ti-bsp/conf/machine/beaglebone.conf b/meta-ti-bsp/conf/machine/beaglebone.conf
> index dceef1db..2d811d0d 100644
> --- a/meta-ti-bsp/conf/machine/beaglebone.conf
> +++ b/meta-ti-bsp/conf/machine/beaglebone.conf
> @@ -5,8 +5,6 @@
> require conf/machine/include/ti33x.inc
>
> PREFERRED_PROVIDER_virtual/kernel = "linux-bb.org"
> -PREFERRED_PROVIDER_virtual/bootloader = "u-boot-bb.org"
> -PREFERRED_PROVIDER_u-boot = "u-boot-bb.org"
>
> KERNEL_DEVICETREE_PREFIX = "am335x-bone"
>
> diff --git a/meta-ti-bsp/conf/machine/beagleplay-k3r5.conf b/meta-ti-bsp/conf/machine/beagleplay-k3r5.conf
> index c40615c9..f8f08d63 100644
> --- a/meta-ti-bsp/conf/machine/beagleplay-k3r5.conf
> +++ b/meta-ti-bsp/conf/machine/beagleplay-k3r5.conf
> @@ -4,9 +4,6 @@
>
> require conf/machine/include/k3r5.inc
>
> -PREFERRED_PROVIDER_virtual/bootloader = "u-boot-bb.org"
> -PREFERRED_PROVIDER_u-boot = "u-boot-bb.org"
> -
> SYSFW_SOC = "am62x"
> SYSFW_CONFIG = "evm"
> SYSFW_SUFFIX = "gp"
> diff --git a/meta-ti-bsp/conf/machine/beagleplay.conf b/meta-ti-bsp/conf/machine/beagleplay.conf
> index e8d25cd9..f4f6a49c 100644
> --- a/meta-ti-bsp/conf/machine/beagleplay.conf
> +++ b/meta-ti-bsp/conf/machine/beagleplay.conf
> @@ -20,8 +20,6 @@ OPTEEMACHINE = "k3-am62x"
> UBOOT_MACHINE = "am62x_evm_a53_defconfig"
>
> PREFERRED_PROVIDER_virtual/kernel = "linux-bb.org"
> -PREFERRED_PROVIDER_virtual/bootloader = "u-boot-bb.org"
> -PREFERRED_PROVIDER_u-boot = "u-boot-bb.org"
>
> KERNEL_DEVICETREE = " \
> ti/k3-am625-beagleplay.dtb \
> diff --git a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb b/meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb
> deleted file mode 100644
> index 4e4688aa..00000000
> --- a/meta-ti-bsp/recipes-bsp/u-boot/u-boot-bb.org_git.bb
> +++ /dev/null
> @@ -1,24 +0,0 @@
> -require u-boot-ti.inc
> -
> -SUMMARY = "BeagleBoard.org U-Boot"
> -
> -COMPATIBLE_MACHINE = "beagle.*"
> -
> -LIC_FILES_CHKSUM = "file://Licenses/README;md5=5a7450c57ffe5ae63fd732446b988025"
> -
> -PV = "2021.01"
> -
> -UBOOT_GIT_URI = "git://github.com/beagleboard/u-boot.git"
> -UBOOT_GIT_PROTOCOL = "https"
> -BRANCH = "v2021.01-ti-08.05.00.005-SDK-8.5"
> -SRCREV = "46ff4982b41067e5c93369bddd49b1541856d80b"
> -
> -BRANCH:beaglebone-ai64 = "v2021.01-ti-08.05.00.001"
> -BRANCH:beaglebone-ai64-k3r5 = "v2021.01-ti-08.05.00.001"
> -SRCREV:beaglebone-ai64 = "ea96725b5156135d5875415f75d2188f6f56622a"
> -SRCREV:beaglebone-ai64-k3r5 = "ea96725b5156135d5875415f75d2188f6f56622a"
> -
> -BRANCH:beagleplay = "v2021.01-ti-BeaglePlay-Release"
> -BRANCH:beagleplay-k3r5 = "v2021.01-ti-BeaglePlay-Release"
> -SRCREV:beagleplay = "f036fbdc25941d7585182d2552c767edb9b04114"
> -SRCREV:beagleplay-k3r5 = "f036fbdc25941d7585182d2552c767edb9b04114"
> --
> 2.39.2
next prev parent reply other threads:[~2023-04-27 20:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 17:23 [meta-ti][master/kirkstone][RFC 0/9] Switch to U-Boot binman Andrew Davis
2023-04-25 17:23 ` [meta-ti][master/kirkstone][RFC 1/9] ti-dm-fw: Add recipe for TI DM firmware Andrew Davis
2023-04-25 17:23 ` [meta-ti][master/kirkstone][RFC 2/9] ti-eth-fw: Add recipe for TI Ethernet firmware Andrew Davis
2023-04-25 17:23 ` [meta-ti][master/kirkstone][RFC 3/9] ti-sci-fw: Remove source package recipe Andrew Davis
2023-04-25 17:23 ` [meta-ti][master/kirkstone][RFC 4/9] u-boot-bb.org: Remove this recipe Andrew Davis
2023-04-27 20:31 ` Denys Dmytriyenko [this message]
2023-04-28 15:13 ` Andrew Davis
2023-05-02 19:38 ` Denys Dmytriyenko
2023-05-04 14:00 ` Andrew Davis
2023-05-06 1:42 ` Denys Dmytriyenko
2023-04-25 17:23 ` [meta-ti][master/kirkstone][RFC 5/9] u-boot-ti-staging: Remove version 2021.01 Andrew Davis
2023-04-25 17:23 ` [meta-ti][master/kirkstone][RFC 6/9] ti-sci-fw: Drop k3-image-gen and only provide firmware Andrew Davis
2023-04-25 17:23 ` [meta-ti][master/kirkstone][RFC 7/9] u-boot-ti-staging: Use binman to package our firmware Andrew Davis
2023-04-25 17:23 ` [meta-ti][master/kirkstone][RFC 8/9] conf: machine: Switch all the machines over to U-Boot binman Andrew Davis
2023-04-25 17:23 ` [meta-ti][master/kirkstone][RFC 9/9] conf: machine: Remove all leftover config files Andrew Davis
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=20230427203108.GO9226@denix.org \
--to=denis@denix.org \
--cc=afd@ti.com \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=n-francis@ti.com \
--cc=praneeth@ti.com \
--cc=reatmon@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.