From: Andrew Davis <afd@ti.com>
To: <reatmon@ti.com>, Praneeth Bajjuri <praneeth@ti.com>,
Denys Dmytriyenko <denys@konsulko.com>,
<meta-ti@lists.yoctoproject.org>, "Sapp, Randolph" <rs@ti.com>
Subject: Re: [meta-ti][kirkstone][PATCH v2 2/2] linux-ti-staging: Use vendored kernel-devicetree.bbclass
Date: Thu, 18 May 2023 12:45:12 -0500 [thread overview]
Message-ID: <4b3ecd96-44d1-eeeb-7e58-704d4e041bcc@ti.com> (raw)
In-Reply-To: <20230518161519.16296-2-reatmon@ti.com>
On 5/18/23 11:15 AM, Ryan Eatmon via lists.yoctoproject.org wrote:
> Change over to using the kernel_devicetree_vendor_dtb.bbclass to have
> the DTBs installed into the same vendored subdirectory that is in the
> kernel.
>
> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
> ---
> v2: - Fixed syntax of "1"
> - Fixed name of custom kernel class to match the other patch.
>
> meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb
> index cdee548f..7c992ac5 100644
> --- a/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb
> +++ b/meta-ti-bsp/recipes-kernel/linux/linux-ti-staging_6.1.bb
> @@ -3,7 +3,7 @@ SUMMARY = "Linux kernel for TI devices"
> LICENSE = "GPL-2.0-only"
> LIC_FILES_CHKSUM = "file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
>
> -inherit kernel
> +inherit kernel_vendor_dtb
>
> require recipes-kernel/linux/setup-defconfig.inc
> require recipes-kernel/linux/kernel-rdepends.inc
> @@ -18,6 +18,9 @@ FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}-6.1:"
> KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT} \
> ${EXTRA_DTC_ARGS}"
>
> +KERNEL_DTBDEST = "${KERNEL_IMAGEDEST}/dtbs"
Do we want this to be "dtbs" or "dtb"? Debian uses "dtb" which is the
far more common distro today and the one we plan to support in the near
term. I know I used "dtbs" in the U-Boot side patch for this, but I'm
having second thoughts and it's easy to switch it over in U-Boot..
Andrew
> +KERNEL_DTBVENDORED = "1"
> +
> S = "${WORKDIR}/git"
>
> BRANCH = "ti-linux-6.1.y"
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#16558): https://lists.yoctoproject.org/g/meta-ti/message/16558
> Mute This Topic: https://lists.yoctoproject.org/mt/98994752/3619733
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/leave/6695306/3619733/2033773410/xyzzy [afd@ti.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2023-05-18 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 16:15 [meta-ti][kirkstone][PATCH v2 1/2] kernel_devicetree_vendor_dtb: Backport kernel-devicetree.bbclass Ryan Eatmon
2023-05-18 16:15 ` [meta-ti][kirkstone][PATCH v2 2/2] linux-ti-staging: Use vendored kernel-devicetree.bbclass Ryan Eatmon
2023-05-18 17:25 ` Andrew Davis
2023-05-18 17:32 ` Denys Dmytriyenko
2023-05-18 17:45 ` Andrew Davis [this message]
2023-05-18 18:06 ` Ryan Eatmon
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=4b3ecd96-44d1-eeeb-7e58-704d4e041bcc@ti.com \
--to=afd@ti.com \
--cc=denys@konsulko.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
--cc=rs@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.