From: Andrew Davis <afd@ti.com>
To: Hari Prasath Gujulan Elango <gehariprasath@ti.com>, <reatmon@ti.com>
Cc: <praneeth@ti.com>, <denys@konsulko.com>,
<meta-arago@lists.yoctoproject.org>, <s-kapoor@ti.com>,
<p-gupta5@ti.com>, <u-kumar1@ti.com>
Subject: Re: [meta-arago][scarthgap][PATCH] tisdk-default-image: add ti-vendor-kernel-headers-dev to DEVTOOLS
Date: Fri, 28 Aug 2026 09:18:55 -0500 [thread overview]
Message-ID: <e2ebea10-e5c3-42d4-b6c3-5675da4923a9@ti.com> (raw)
In-Reply-To: <20260828080918.1161144-1-gehariprasath@ti.com>
On 8/28/26 3:09 AM, Hari Prasath Gujulan Elango wrote:
> TI vendor kernel uapi additions (e.g. DMA_HEAP_IOCTL_EXPORT) isn't
> present in the standard header provided by the linux-libc-headers,
> so on-target compilation against them needs the ti-vendor-kernel-headers-dev
> package alongside linux-libc-headers-dev.
>
> Signed-off-by: Hari Prasath Gujulan Elango <gehariprasath@ti.com>
> ---
> meta-arago-distro/recipes-core/images/tisdk-default-image.bb | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta-arago-distro/recipes-core/images/tisdk-default-image.bb b/meta-arago-distro/recipes-core/images/tisdk-default-image.bb
> index 264d1b2d..cac6628e 100644
> --- a/meta-arago-distro/recipes-core/images/tisdk-default-image.bb
> +++ b/meta-arago-distro/recipes-core/images/tisdk-default-image.bb
> @@ -36,6 +36,7 @@ IMAGE_FSTYPES:remove:omapl138 = "ubifs ubi"
>
> DEVTOOLS = " \
> linux-libc-headers-dev \
> + ti-vendor-kernel-headers-dev \
What application(s) actually need this header file, shouldn't they
add it to their DEPENDS line instead of unconditionally installing
for this image? (and why only this image, we have other images
folks build on)
Andrew
> build-essential \
> packagegroup-core-tools-debug \
> git \
next prev parent reply other threads:[~2026-08-28 14:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 8:09 [meta-arago][scarthgap][PATCH] tisdk-default-image: add ti-vendor-kernel-headers-dev to DEVTOOLS Hari Prasath Gujulan Elango
2026-08-28 8:16 ` PRC Automation
2026-08-28 14:18 ` Andrew Davis [this message]
2026-08-28 17:37 ` 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=e2ebea10-e5c3-42d4-b6c3-5675da4923a9@ti.com \
--to=afd@ti.com \
--cc=denys@konsulko.com \
--cc=gehariprasath@ti.com \
--cc=meta-arago@lists.yoctoproject.org \
--cc=p-gupta5@ti.com \
--cc=praneeth@ti.com \
--cc=reatmon@ti.com \
--cc=s-kapoor@ti.com \
--cc=u-kumar1@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.