All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: afd@ti.com
Cc: Ryan Eatmon <reatmon@ti.com>, meta-ti@lists.yoctoproject.org
Subject: Re: [meta-ti][master/kirkstone][PATCH v2 2/5] linux-ti-mainline: Remove ti-upstream-tools
Date: Tue, 11 Apr 2023 15:49:16 -0400	[thread overview]
Message-ID: <20230411194916.GX9226@denix.org> (raw)
In-Reply-To: <20230411174037.32244-2-afd@ti.com>

On Tue, Apr 11, 2023 at 12:40:34PM -0500, Andrew Davis via lists.yoctoproject.org wrote:
> Mainline should test the mainline kernel as it is, not with out-of-tree
> changes like new DTB/DTBOs. Use only upstream DTB/DTBOs. As that was the
> last thing provided by ti-upstream-tools, remove it here.
> 
> Signed-off-by: Andrew Davis <afd@ti.com>
> ---
>  .../recipes-kernel/linux/linux-ti-mainline_git.bb     | 11 +++--------
>  1 file changed, 3 insertions(+), 8 deletions(-)
> 
> diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-mainline_git.bb b/meta-ti-bsp/recipes-kernel/linux/linux-ti-mainline_git.bb
> index 7d948a85..d0f1b4e2 100644
> --- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-mainline_git.bb
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-mainline_git.bb
> @@ -1,5 +1,5 @@
>  SECTION = "kernel"
> -SUMMARY = "Mainline Linux kernel for TI devices (with ti-upstream-tools)"
> +SUMMARY = "Mainline Linux kernel for TI devices"
>  LICENSE = "GPL-2.0-only"
>  LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
>  
> @@ -15,9 +15,6 @@ KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT} \
>  
>  S = "${WORKDIR}/git"
>  
> -BRANCH = "master"
> -TOOLS_BRANCH = "master"
> -
>  # 5.15 Mainline version
>  SRCREV = "8bb7eca972ad531c9b149c0a51ab43a417385813"
>  PV = "5.15+git${SRCPV}"
> @@ -28,12 +25,11 @@ PR = "${MACHINE_KERNEL_PR}"
>  
>  KERNEL_GIT_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git"
>  KERNEL_GIT_PROTOCOL = "https"
> +KERNEL_GIT_BRANCH = "master"
>  SRC_URI += " \
> -    ${KERNEL_GIT_URI};protocol=${KERNEL_GIT_PROTOCOL};branch=${BRANCH};name=linux \
> -    git://git.ti.com/git/ti-linux-kernel/ti-upstream-tools.git;branch=${TOOLS_BRANCH};protocol=${KERNEL_GIT_PROTOCOL};name=ti-upstream-tools;destsuffix=git/ti-upstream-tools \
> +	${KERNEL_GIT_URI};protocol=${KERNEL_GIT_PROTOCOL};branch=${KERNEL_GIT_BRANCH};name=linux \
>  "
>  
> -SRCREV_ti-upstream-tools = "0f60697843bba6f8d721b14da92b1652563ccb95"
>  SRCREV_FORMAT = "linux"

Remove SRCREV_FORMAT that is used for multi-SCM recipes, as well as 
";name=linux" from SRC_URI above.


>  DEFCONFIG_NAME = "multi_v7_defconfig"
> @@ -43,7 +39,6 @@ KERNEL_CONFIG_COMMAND = "oe_runmake -C ${S} O=${B} ${DEFCONFIG_NAME}"
>  
>  kernel_do_compile:append() {
>  	oe_runmake dtbs CC="${KERNEL_CC} $cc_extra " LD="${KERNEL_LD}" ${KERNEL_EXTRA_ARGS}

Are you keeping "make dtbs" to build ALL DTBs from the kernel? Same story as 
with patch #5 for linux-ti-next - KERNEL_DEVICETREE has a list of upstreamed 
DTBs that will be built automatically, so above line can also be removed.
(though j784s4-evm has an empty KERNEL_DEVICETREE - nothing got upstreamed?)


> -	oe_runmake -C ${S}/ti-upstream-tools LINUX=${S} DTC=${B}/scripts/dtc/dtc O=${B} CC="${KERNEL_CC} $cc_extra " LD="${KERNEL_LD}" ${KERNEL_EXTRA_ARGS}
>  }
>  
>  do_shared_workdir:prepend() {
> -- 
> 2.39.2


  reply	other threads:[~2023-04-11 19:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 17:40 [meta-ti][master/kirkstone][PATCH v2 1/5] linux-ti-mainline: Use upstream configs with upstream kernel Andrew Davis
2023-04-11 17:40 ` [meta-ti][master/kirkstone][PATCH v2 2/5] linux-ti-mainline: Remove ti-upstream-tools Andrew Davis
2023-04-11 19:49   ` Denys Dmytriyenko [this message]
2023-04-11 21:35     ` Andrew Davis
2023-04-11 17:40 ` [meta-ti][master/kirkstone][PATCH v2 3/5] linux-ti-mainline: Update to v6.2 mainline version Andrew Davis
2023-04-11 17:40 ` [meta-ti][master/kirkstone][PATCH v2 4/5] linux-ti-next: Add defconfig for OMAP-L138 Andrew Davis
2023-04-11 19:51   ` Denys Dmytriyenko
2023-04-11 21:14     ` Andrew Davis
2023-04-11 21:32       ` Denys Dmytriyenko
2023-04-11 21:42         ` Andrew Davis
2023-04-11 17:40 ` [meta-ti][master/kirkstone][PATCH v2 5/5] linux-ti-next: Remove unneeded do_compile append Andrew Davis
2023-04-11 19:38 ` [meta-ti][master/kirkstone][PATCH v2 1/5] linux-ti-mainline: Use upstream configs with upstream kernel Denys Dmytriyenko

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=20230411194916.GX9226@denix.org \
    --to=denis@denix.org \
    --cc=afd@ti.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --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.