From: Randolph Sapp <rs@ti.com>
To: Andrew Davis <afd@ti.com>, <rs@ti.com>, <denis@denix.org>,
<reatmon@ti.com>, <detheridge@ti.com>, <praneeth@ti.com>
Cc: <meta-ti@lists.yoctoproject.org>
Subject: Re: [meta-ti][master/wrynose][PATCH] ti-sgx-ddk-*: version bump to support wrynose
Date: Fri, 13 Nov 2026 14:07:37 -0600 [thread overview]
Message-ID: <DMUCROR5YB40.39CTYNATDAFYQ@ti.com> (raw)
In-Reply-To: <b5cb59c8-2e08-44b2-9271-b3766085772f@ti.com>
On Thu Nov 12, 2026 at 4:54 PM CST, Andrew Davis wrote:
> On 11/12/26 4:37 PM, rs@ti.com wrote:
>> From: Randolph Sapp <rs@ti.com>
>>
>> Bump the SGX graphics packages to include support for kernel 6.18 and
>> mesa 25.2.8.
>>
>> This include initial experimental support for a unified dri interface.
>> This deprecates the old mesa interface added for the "sgx" gallium shim.
>>
>> This allows SGX devices to use the "pvr" gallium shim currently being
>> used by the rogue proprietary driver. It also adds some experimental EGL
>> features to accommodate the increased requirements for that interface.
>>
>> EGL blit operations are present, but testing is currently limited.
>>
>> Prime buffer import and export functionality is partially advertised, as
>> required for the mesa pipe loader interface and EGL wayland. The
>> functionality provided for these features is currently the bare minimum
>> for context initialization. Expect some incompatibility.
>>
>> This is the initial version, so you may see some issues depending on the
>> application. Please report those issues if they are not covered below.
>>
>> Known issues:
>> - Multisampling support is currently disabled as it does not currently
>> work (debug in progress)
>> - A hardware recovery may be seen when initially interacting with the
>> device (debug pending)
>> - DRM EGL format negotiations may fail in some applications with tilcdc
>> (low priority / technical limitation)
>>
>> Signed-off-by: Randolph Sapp <rs@ti.com>
>> ---
>> meta-ti-bsp/conf/machine/include/ti-bsp.inc | 2 ++
>> .../recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb | 2 +-
>> meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_24.0.1.bb | 2 +-
>> meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_25.2.8.bb | 2 +-
>> .../powervr-umlibs/ti-sgx-ddk-um_1.17.4948957.bb | 2 +-
>> 5 files changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/meta-ti-bsp/conf/machine/include/ti-bsp.inc b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
>> index bf90d1da8a12..d9f59159037a 100644
>> --- a/meta-ti-bsp/conf/machine/include/ti-bsp.inc
>> +++ b/meta-ti-bsp/conf/machine/include/ti-bsp.inc
>> @@ -42,6 +42,8 @@ BSP_KERNEL_VERSION:bsp-ti-6_18 = "6.18%"
>> BSP_BOOTLOADER_PROVIDER:bsp-ti-6_18 = "u-boot-ti-staging"
>> BSP_BOOTLOADER_VERSION:bsp-ti-6_18 = "2026.01%"
>>
>> +BSP_SGX_DRIVER_PROVIDER:bsp-ti-6_18 = "ti-sgx-ddk-km"
>> +BSP_SGX_DRIVER_VERSION:bsp-ti-6_18 = "1.17%"
>> BSP_ROGUE_DRIVER_PROVIDER:bsp-ti-6_18 = "ti-img-rogue-driver"
>> BSP_ROGUE_DRIVER_VERSION:bsp-ti-6_18 = "26%"
>> BSP_MESA_PVR_VERSION:bsp-ti-6_18 = "25%"
>> diff --git a/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb b/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb
>> index 343f09de3d86..934e663849bd 100644
>> --- a/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb
>> +++ b/meta-ti-bsp/recipes-bsp/powervr-drivers/ti-sgx-ddk-km_1.17.4948957.bb
>> @@ -17,7 +17,7 @@ BRANCH = "${PV}/mesa/k6.1"
>>
>> SRC_URI = "git://git.ti.com/git/graphics/omap5-sgx-ddk-linux.git;protocol=https;branch=${BRANCH}"
>>
>> -SRCREV = "9ae0fa4998b1c624408945e062bf8fb0ea7efb9d"
>> +SRCREV = "cfcc733d3d59f3287574fd4909e2cd4cd9346f3f"
>>
>> TARGET_PRODUCT:ti33x = "ti335x_linux"
>> TARGET_PRODUCT:ti43x = "ti437x_linux"
>> diff --git a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_24.0.1.bb b/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_24.0.1.bb
>> index 2c20a538b2cf..f5dc5301e757 100644
>> --- a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_24.0.1.bb
>> +++ b/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_24.0.1.bb
>> @@ -29,7 +29,7 @@ PR = "r1"
>> PACKAGE_ARCH = "${MACHINE_ARCH}"
>>
>> GALLIUMDRIVERS:append = "${@bb.utils.contains('PREFERRED_PROVIDER_virtual/gpudriver', 'ti-img-rogue-driver', ',pvr', '', d)}"
>> -GALLIUMDRIVERS:append = "${@bb.utils.contains('PREFERRED_PROVIDER_virtual/gpudriver', 'ti-sgx-ddk-km', ',sgx', '', d)}"
>> +GALLIUMDRIVERS:append = "${@bb.utils.contains('PREFERRED_PROVIDER_virtual/gpudriver', 'ti-sgx-ddk-km', ',pvr', '', d)}"
>>
>> VULKAN_DRIVERS:append = "${@bb.utils.contains('PREFERRED_PROVIDER_virtual/gpudriver', 'ti-img-rogue-driver', ',pvr', '', d)}"
>>
>> diff --git a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_25.2.8.bb b/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_25.2.8.bb
>> index 03b0b9bfc886..1b53ac39d55e 100644
>> --- a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_25.2.8.bb
>> +++ b/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_25.2.8.bb
>> @@ -20,7 +20,7 @@ PR = "r1"
>> PACKAGE_ARCH = "${MACHINE_ARCH}"
>>
>> GALLIUMDRIVERS:append = "${@bb.utils.contains('PREFERRED_PROVIDER_virtual/gpudriver', 'ti-img-rogue-driver', ',pvr', '', d)}"
>> -GALLIUMDRIVERS:append = "${@bb.utils.contains('PREFERRED_PROVIDER_virtual/gpudriver', 'ti-sgx-ddk-km', ',sgx', '', d)}"
>> +GALLIUMDRIVERS:append = "${@bb.utils.contains('PREFERRED_PROVIDER_virtual/gpudriver', 'ti-sgx-ddk-km', ',pvr', '', d)}"
>
> Could we just do:
>
> GALLIUMDRIVERS:append = "pvr"
>
> now that everyone who includes this will want the "pvr" driver?
>
> Andrew
>
Yeah, but I'm waiting for an additional build to finish to see if we could also
get away with enabling the vulkan components even though those are actually
unusable under SGX. Just want to make sure it doesn't advertise anything weird
to other userspace tools.
People wanted some revision to test so this was safer / more obvious change for
anyone following along at home.
>>
>> VULKAN_DRIVERS:append = "${@bb.utils.contains('PREFERRED_PROVIDER_virtual/gpudriver', 'ti-img-rogue-driver', ',pvr', '', d)}"
>>
>> diff --git a/meta-ti-bsp/recipes-graphics/powervr-umlibs/ti-sgx-ddk-um_1.17.4948957.bb b/meta-ti-bsp/recipes-graphics/powervr-umlibs/ti-sgx-ddk-um_1.17.4948957.bb
>> index c4cc5f10ef3b..bd0656a3cb7e 100644
>> --- a/meta-ti-bsp/recipes-graphics/powervr-umlibs/ti-sgx-ddk-um_1.17.4948957.bb
>> +++ b/meta-ti-bsp/recipes-graphics/powervr-umlibs/ti-sgx-ddk-um_1.17.4948957.bb
>> @@ -13,7 +13,7 @@ BRANCH = "${PV}/mesa/glibc-2.35"
>> SRC_URI = " \
>> git://git.ti.com/git/graphics/omap5-sgx-ddk-um-linux.git;protocol=https;branch=${BRANCH} \
>> "
>> -SRCREV = "84a396a4fb379f10931421e489ac8a199d6a9f2c"
>> +SRCREV = "f52f27edce0e961be46eb4426dd030a6ab17ad16"
>>
>> INITSCRIPT_NAME = "rc.pvr"
>> INITSCRIPT_PARAMS = "defaults 8"
next prev parent reply other threads:[~2026-11-13 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 22:37 [meta-ti][master/wrynose][PATCH] ti-sgx-ddk-*: version bump to support wrynose rs
2026-11-12 22:54 ` Andrew Davis
2026-11-13 20:07 ` Randolph Sapp [this message]
2026-11-13 12:28 ` PRC Automation
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=DMUCROR5YB40.39CTYNATDAFYQ@ti.com \
--to=rs@ti.com \
--cc=afd@ti.com \
--cc=denis@denix.org \
--cc=detheridge@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--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.