Hello Andrew,
Thanks for the reviews.
On 8/28/2026 8:12 PM, Andrew Davis wrote:
On 8/28/26 3:07 AM, Hari Prasath Gujulan Elango wrote:
The TI vendor kernel's dma-heap.h carries DMA_HEAP_IOCTL_EXPORT in
downstream.The standard header provided by linux-libc-headers' wouldn't
Add a space after end of sentences "."
ACK
have the custom changes.Copy it straight from the kernel's staged
source tree (STAGING_KERNEL_DIR)into a separate /usr/include/ti/linux
path instead, for userspace code that needs it.
Signed-off-by: Hari Prasath Gujulan Elango <[email protected]>
---
.../ti-vendor-kernel-headers_1.0.bb | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
create mode 100644 meta-ti-bsp/recipes-kernel/ti-vendor-kernel-
headers/ti-vendor-kernel-headers_1.0.bb
diff --git a/meta-ti-bsp/recipes-kernel/ti-vendor-kernel-headers/ti-
vendor-kernel-headers_1.0.bb b/meta-ti-bsp/recipes-kernel/ti-vendor-
kernel-headers/ti-vendor-kernel-headers_1.0.bb
new file mode 100644
index 000000000..bf7dcc3a5
--- /dev/null
+++ b/meta-ti-bsp/recipes-kernel/ti-vendor-kernel-headers/ti-vendor-
kernel-headers_1.0.bb
@@ -0,0 +1,17 @@
+SUMMARY = "TI vendor kernel uapi headers not present in mainline
linux-libc-headers"
+DESCRIPTION = "Copies select uapi headers straight from the TI vendor
kernel source \
s/uapi/UAPI as it is acronym (Userspace Application Programing Interface)
ACK
+tree into a TI-specific include path (/usr/include/ti/linux), for
userspace code \
+that needs them but can't rely on linux-libc-headers carrying TI-only
additions."
+LICENSE = "GPL-2.0-only"
+LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/GPL-2.0-
only;md5=801f80980d171dd6425610833a22dbe6"
+
+PACKAGE_ARCH = "${MACHINE_ARCH}"
+
+do_configure[depends] += "virtual/kernel:do_shared_workdir"
+do_install[depends] += "virtual/kernel:do_shared_workdir"
+
+do_install() {
+ install -d ${D}${includedir}/ti/linux
+ install -m 0644 ${STAGING_KERNEL_DIR}/include/uapi/linux/dma-
heap.h ${D}${includedir}/ti/linux/dma-heap.h
+}
+
I don't have an huge issue with this series, but let's make sure we know
the alternatives
first. If only a couple applications need this header, they can bundle a
copy of the
DMA_HEAP_IOCTL_EXPORT definition inside their own source.
That does have the downside of if the definition in kernel changes the
application will not
get the update automatically when rebuilt against the new kernel. But
this is already the big
issue with using custom UAPI like this in the first place, if the kernel
gets updated the
applications can stop working. The upstream kernel never breaks existing
UAPI, but our
downstream can and does.
As said, this patch looks fine as-is, just something to think about.
We could certainly explore this option, but as you have highlighted
syncing that with the kernel would be a challenge. I need more time to
discuss with the concerned team how best we can manage this.I would say
let's take this patch in considering the SDK release for Ford.
Regards,
Hari
Andrew
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20305):
https://lists.yoctoproject.org/g/meta-ti/message/20305
Mute This Topic: https://lists.yoctoproject.org/mt/120969413/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
