On Mon Nov 4, 2024 at 4:37 PM CST, Ryan Eatmon wrote:
> On 11/4/2024 4:19 PM, Randolph Sapp wrote:
> > On Mon Nov 4, 2024 at 1:46 PM CST, Ryan Eatmon via lists.yoctoproject.org
> > wrote:
> >> Backport two fixes from the latest mesa project to fix two builds issues
> >> related to newer llvm versi
On Mon Nov 4, 2024 at 1:46 PM CST, Ryan Eatmon via lists.yoctoproject.org wrote:
> Backport two fixes from the latest mesa project to fix two builds issues
> related to newer llvm versions.
>
> Signed-off-by: Ryan Eatmon
> ---
> ...allium-Fix-build-with-llvm-18-and-19.patch | 53 +
From: Randolph Sapp
The mesa.inc that we inherit from oe-core now has the required
parameters. This conditional append is no longer required.
This reverts commit dbc6afc46e55b247606dfad5238137c8fa807843.
Signed-off-by: Randolph Sapp
---
meta-ti-bsp/conf/layer.conf| 4
From: Randolph Sapp
Bump versions of mesa-pvr and ti-sgx-ddk-km to support SGX with kernel
6.6 and the same version of mesa rogue is using right now (23.2.1).
These commits are currently compatible with both kernel 6.1 and 6.6.
Enable SGX by default in the 6.6 BSP provider section logic.
Signed
From: Randolph Sapp
Resolve some issues with J721E and compressed NPOT (Non-Power-Of-Two)
textures.
Also, add some additional allocation tracking in render process specific
tasks.
Signed-off-by: Randolph Sapp
---
.../powervr-umlibs/ti-img-rogue-umlibs_24.1.6554834.bb | 2 +-
1 file c
From: Randolph Sapp
We got a bit more time to do a proper migration this time. A discovery
period to see what actually works and boy, it wasn't much.
This update resolves issues with:
- Macro redefinition
- Sparse NPOT texture allocations
- vec4 reductions
- Mesa
From: Randolph Sapp
We got a bit more time to do a proper migration this time. A discovery
period to see what actually works and boy, it wasn't much.
This update resolves issues with:
- Macro redefinition
- Sparse NPOT texture allocations
- vec4 reductions
- Mesa
From: Randolph Sapp
Bump SRCREV to pick up some patches that adjust the way heaps are
sized. This solves issues seen when utilizing page sizes greater
than 4K.
Signed-off-by: Randolph Sapp
---
.../powervr-drivers/ti-img-rogue-driver_23.3.6512818.bb | 2 +-
.../powervr-drivers/ti-img-ro
From: Randolph Sapp
Adding this sanity check here preemptively. Since these libraries were
compiled with an older version of GCC than what is currently in use on
scarthgap and master they won't trip the sanity check just yet, but if
someone attempts to update them and uses a newer compiler (for s
From: Randolph Sapp
Add ldflags to the INSANE_SKIP strings for all components. We now use the Yocto
compiler for these packages but we do not use all of the yocto compiler flags.
As such, whenever the GCC version being used for these packages is equal to the
version Yocto is currently on, we wil
From: Randolph Sapp
Add ldflags to INSANE_SKIP for the libopencl-rogue-tools package. For
some reason I didn't catch this sooner, but this falls victim to the
same issues the parent package faced earlier this year.
Just enough options enabled that Yocto wants to do a ldflags check, but
the DDK w
On Mon Jun 24, 2024 at 3:06 PM CDT, Denys Dmytriyenko wrote:
> On Mon, Jun 24, 2024 at 01:17:12PM -0500, r...@ti.com wrote:
> > From: Randolph Sapp
> >
> > Resolve some issues afer the new bsp-provider selection logic was added and
> > add
> > some patches to help with compilation flag checks in
From: Randolph Sapp
Bump this recipe to add a change to help with GCC 14 compatibility in
the check-cc script used to check compiler flags before use.
Signed-off-by: Randolph Sapp
---
.../powervr-drivers/ti-img-rogue-driver_24.1.6554834.bb | 2 +-
1 file changed, 1 insertion(+), 1 dele
From: Randolph Sapp
Bump this recipe to add a change to help with GCC 14 compatibility in
the check-cc script used to check compiler flags before use.
Reset this back to the proper branches for kernel 6.1 since this recipe
is only being used in 6.6 bsp providers.
Signed-off-by: Randolph Sapp
-
From: Randolph Sapp
Resolve some issues afer the new bsp-provider selection logic was added and add
some patches to help with compilation flag checks in the KM.
This includes equivalent patches from the following post for GCC 14 compat:
https://lists.yoctoproject.org/g/meta-ti/topic/106806264
R
On Fri Jun 21, 2024 at 5:41 PM CDT, Max Krummenacher wrote:
> Hello Randolph
>
> Am Freitag, dem 21.06.2024 um 15:15 -0500 schrieb r...@ti.com:
> > From: Randolph Sapp
> >
> > Bump this recipe to add a change to help with GCC 14 compatibility in
> > the check-cc script used to check compiler flag
From: Randolph Sapp
Bump this recipe to add a change to help with GCC 14 compatibility in
the check-cc script used to check compiler flags before use.
Also ports some of the patches that were added to the kirkstone branch
post creation of what was supposed to be a temporary scarthgap branch.
Si
On Wed Jun 19, 2024 at 12:32 PM CDT, Max Krummenacher wrote:
> From: Max Krummenacher
>
> GCC-14 set more warnings to errors, demote the ones which trigger to a
> warning.
> This is when building bsp-ti-6_1. I did not notice it when building bsp-ti-6_6
>
> Signed-off-by: Max Krummenacher
> ---
>
From: Randolph Sapp
Bump the SRCREV to pick up some new binaries for AM62P. The allocation
patch for Chromium was not included for this device previously.
Signed-off-by: Randolph Sapp
---
.../powervr-umlibs/ti-img-rogue-umlibs_24.1.6554834.bb | 2 +-
1 file changed, 1 insertion(+), 1
On Thu Jun 6, 2024 at 5:10 PM CDT, Denys Dmytriyenko wrote:
> On Thu, Jun 06, 2024 at 02:37:46PM -0500, Randolph Sapp via
> lists.yoctoproject.org wrote:
> > On Thu Jun 6, 2024 at 11:02 AM CDT, Amol Practise wrote:
> > > Hi Team,
> > >
> > > Any h
On Thu Jun 6, 2024 at 11:02 AM CDT, Amol Practise wrote:
> Hi Team,
>
> Any help would be appreciated on below issue.
>
> On Sun, Jun 2, 2024 at 12:40 PM Amol Practise via lists.yoctoproject.org
> wrote:
>
> > Hi all,
> >
> > I am getting below error while i am trying to build westom image for
> >
From: Randolph Sapp
Lift the common parts of the top level gitignore from oe-core and
meta-openembedded. This masks out temporary python files, intermediate
artifacts, and unclean patch leftovers (.orig, .rej, etc).
We're choosing to leave patches at the root of the project out of this
as mainta
From: Randolph Sapp
Lift the common parts of the top level gitignore from oe-core and
meta-openembedded. This masks out temporary python files, intermediate
artifacts, and unclean patch leftovers (.orig, .rej, etc).
We're choosing to leave patches at the root of the project out of this
as mainta
On Tue Jun 4, 2024 at 5:15 PM CDT, Ryan Eatmon wrote:
>
>
> On 6/4/2024 2:12 PM, Denys Dmytriyenko wrote:
> > On Mon, Jun 03, 2024 at 02:55:15PM -0500, r...@ti.com wrote:
> >> From: Randolph Sapp
> >>
> >> Lift the common parts of the top level gitignore from oe-core and
> >> meta-openembedded. Th
From: Randolph Sapp
Lift the common parts of the top level gitignore from oe-core and
meta-openembedded. This masks out temporary python files, intermediate
artifacts, and patches at the root of the project.
Signed-off-by: Randolph Sapp
---
.gitignore | 7 +++
1 file changed, 7 insertions(
From: Randolph Sapp
Bump the SRCREV to pick up rebuilt binaries. Upstream release notes:
Regenerate all binaries with a fix for exportable buffer allocations
that should improve Chromium compatibility.
Signed-off-by: Randolph Sapp
---
.../powervr-umlibs/ti-img-rogue-umlibs_24.1.6554834.bb
On Thu May 2, 2024 at 2:45 PM CDT, Denys Dmytriyenko wrote:
> Can you make it a diff please? As shown previously, that helps with review
> and
> allows spotting issues much easier.
>
[snip]
Yeah, sorry about the delay on this. Just got back to Dallas. Appending the diff
here if people need it. I
From: Randolph Sapp
Add a recipe for mesa-pvr to use a newer branch based on mesa 23.2.1.
This branch does not currently contain SGX patches so it is also being
masked by the ltsprep branding to prevent regressing those devices
currently.
Please note that may run into sstate errors when switchin
From: Randolph Sapp
Locally overlay verbatim copies of mesa 22.3.5 patches from
oe-core/master, so we get whatever QoL patches from core relevant to the
current release.
Signed-off-by: Randolph Sapp
---
.../0001-gallium-Fix-build-with-llvm-17.patch | 41 ++
...e-cmake-dependenc
From: Randolph Sapp
Jump the drivers to DDK 24.1.6554834 and update pvr-mesa to match the version
presented in that release.
This adds the update as a new recipe for the newer version as it requires a
change in device tree that is currently only present in the ltsprep branding.
The new mesa ver
From: Randolph Sapp
Recipes for DDK 24.1, but lock them behind ltsprep tags because they
require device tree changes that do not work on the current default
kernel for this layer.
Signed-off-by: Randolph Sapp
---
.../ti-img-rogue-driver_24.1.6554834.bb | 44 ++
.../ti-img-rogue-umli
On Thu May 2, 2024 at 12:59 PM CDT, Randolph Sapp via lists.yoctoproject.org
wrote:
> On Wed May 1, 2024 at 10:01 PM CDT, Denys Dmytriyenko wrote:
> > Reformatted to be a diff against the previous version to spot the actual
> > changes and spot any issues. See below.
> >
&
On Thu May 2, 2024 at 1:20 PM CDT, Denys Dmytriyenko wrote:
> On Thu, May 02, 2024 at 12:49:13PM -0500, Randolph Sapp wrote:
> > On Wed May 1, 2024 at 10:06 PM CDT, Denys Dmytriyenko wrote:
> > > On Wed, May 01, 2024 at 08:26:21PM -0400, Denys Dmytriyenko wrote:
> > > > From: Randolph Sapp
> > > >
On Wed May 1, 2024 at 11:47 AM CDT, Denys Dmytriyenko wrote:
> On Tue, Apr 30, 2024 at 04:38:21PM -0500, Randolph Sapp via
> lists.yoctoproject.org wrote:
> > From: Randolph Sapp
> >
> > Add a recipe for mesa-pvr to use a newer branch based on mesa 23.2.1.
> >
On Wed May 1, 2024 at 10:01 PM CDT, Denys Dmytriyenko wrote:
> Reformatted to be a diff against the previous version to spot the actual
> changes and spot any issues. See below.
>
>
> On Wed, May 01, 2024 at 08:26:19PM -0400, Denys Dmytriyenko wrote:
> > From: Randolph Sapp
> >
> > Add these rec
On Wed May 1, 2024 at 10:06 PM CDT, Denys Dmytriyenko wrote:
> On Wed, May 01, 2024 at 08:26:21PM -0400, Denys Dmytriyenko wrote:
> > From: Randolph Sapp
> >
> > Add a recipe for mesa-pvr to use a newer branch based on mesa 23.2.1.
> > This branch does not currently contain SGX patches so it is a
From: Randolph Sapp
Add these recipes but lock them behind ltsprep tags because they require
device tree changes that does not work on the current default kernel for
this layer.
Signed-off-by: Randolph Sapp
---
.../ti-img-rogue-driver_24.1.6554834.bb | 44 ++
.../ti-img-rogue-umlibs
From: Randolph Sapp
Add a recipe for mesa-pvr to use a newer branch based on mesa 23.2.1.
This branch does not currently contain SGX patches so it is also being
masked by the ltsprep branding to prevent regressing those devices
currently.
Please note that because this recipe is currently in
SIGG
From: Randolph Sapp
Locally overlay verbatim copies of mesa 22.3.5 patches from
oe-core/master, so we get whatever QoL patches from core relevant to the
current release.
Signed-off-by: Randolph Sapp
---
.../0001-gallium-Fix-build-with-llvm-17.patch | 41 ++
...e-cmake-dependenc
From: Randolph Sapp
Jump the drivers to DDK 24.1.6554834 and update pvr-mesa to match the version
presented in that release.
This adds the update as a new recipe for the newer version as it requires a
change in device tree that is currently only present in the ltsprep branding.
The new mesa ver
On Wed Mar 6, 2024 at 4:50 PM CST, Randolph Sapp via lists.yoctoproject.org
wrote:
> From: Randolph Sapp
>
> Bump the package version to align with the changed AM62 GPU device tree
> compatible string. This will make it easer to switch back and forth
> between the proprietary
From: Randolph Sapp
Bump the package version to align with the changed AM62 GPU device tree
compatible string. This will make it easer to switch back and forth
between the proprietary and open source driver.
Signed-off-by: Randolph Sapp
---
.../powervr-drivers/ti-img-rogue-driver_23.3.6512818.
From: Randolph Sapp
Bump the SRCREV to include a fix for suspend and resume. Unfortunately
version 23.3 includes a partial rework of the power management subsystem
that breaks OS active power management. Apparently it also broke OS
suspend/resume by incorrectly setting OS state before the device
From: Randolph Sapp
Bump the SRCREV to include some useful patches that:
- Fix the ROGUE segfault issue introduced by SGX (this was what
the old conditional logic was addressing)
- Fix destruction of event queue with proxies still attached
Signed-off-by: Randolph Sapp
From: Randolph Sapp
If Yocto even sees a "-dev" package in the PACKAGES string it will
automatically forward all dev-so links to that package. Remove that
entry from the PACKAGES string so we get the required links again.
Signed-off-by: Randolph Sapp
---
This is a master only patch! In kirksto
From: Randolph Sapp
Bump SRCREV to include the following changes in UM and KM:
- Rebuild all releases with external memory wrap disabled due to
some incompatibility with certain Qt use cases.
- Add a watchdog change that prevents an occasional false
timeout wh
From: Randolph Sapp
Move to the 23.2 release branch and bump SRCREV accordingly. This branch
has the proper implementation of the cache coherency fix along with some
other checks that address some system stability issues on Jacinto
devices.
Signed-off-by: Randolph Sapp
---
...iver_23.1.6404501
From: Randolph Sapp
Add the configuration options for am62pxx-evm.
This also adds support for new devicetree properties to override the
clock value of the device. See the kernel module modifications [1] and
dt bindings for more information.
[1]
https://git.ti.com/cgit/graphics/ti-img-rogue-dri
From: Randolph Sapp
Another graphics series to pull things forwards and enable AM62P support. This
addresses a potential regression with rogue post SGX integration and tests out
some new dt configuration options for AM62P.
Give it a spin.
Randolph Sapp (4):
mesa-pvr: isolate sgx and rogue com
From: Randolph Sapp
Bump SRCREV to include some patches to better isolate SGX and PVR
components.
Signed-off-by: Randolph Sapp
---
meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr
From: Randolph Sapp
Enable the GPU on the am62pxx-evm machine target.
Signed-off-by: Randolph Sapp
---
meta-ti-bsp/conf/machine/include/am62pxx.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-ti-bsp/conf/machine/include/am62pxx.inc
b/meta-ti-bsp/conf/machine/inclu
From: Randolph Sapp
Bump ti-sgx-ddk-um and ti-sgx-ddk-km to the new branch for Kirkstone and
mesa independent builds. This also sets up SGX to use the latest mesa
revision rogue uses.
Changelog:
- IMG Support has officially ended. This repo will not be getting
regular updates after this unl
From: Randolph Sapp
Bump the SRCREV to include the required changes to build for SGX now.
Signed-off-by: Randolph Sapp
---
meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.
From: Randolph Sapp
Brining back SGX on kirkstone (and hopefully making it easier for the community
to port to other distros).
This overhauls the SGX drivers, fixing a few bugs and setting things up to
achieve three things:
1) OpenGLES2 Acceleration under kirkstone (even if it is limited)
2) Br
From: Randolph Sapp
Enable SGX Graphics on the currently tested platforms.
Signed-off-by: Randolph Sapp
---
meta-ti-bsp/conf/machine/include/am65xx.inc | 2 +-
meta-ti-bsp/conf/machine/include/omap-a15.inc | 2 +-
meta-ti-bsp/conf/machine/include/ti33x.inc| 2 +-
meta-ti-bsp/conf/machine
From: Randolph Sapp
Bump the SRCREV to include the required changes to build for SGX now.
Signed-off-by: Randolph Sapp
---
meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-ti-bsp/recipes-graphics/mesa/mesa-pvr_22.3.5.
From: Randolph Sapp
Bump ti-sgx-ddk-um and ti-sgx-ddk-km to the new branch for Kirkstone and
mesa independent builds. This also sets up SGX to use the latest mesa
revision rogue uses.
Changelog:
- IMG Support has officially ended. This repo will not be getting
regular updates after this unl
From: Randolph Sapp
Enable SGX Graphics on the currently tested platforms.
Signed-off-by: Randolph Sapp
---
meta-ti-bsp/conf/machine/include/am65xx.inc | 2 +-
meta-ti-bsp/conf/machine/include/omap-a15.inc | 2 +-
meta-ti-bsp/conf/machine/include/ti33x.inc| 2 +-
3 files changed, 3 inser
From: Randolph Sapp
Brining back SGX on kirkstone (and hopefully making it easier for the community
to port to other distros).
This overhauls the SGX drivers, fixing a few bugs and setting things up to
achieve three things:
1) OpenGLES2 Acceleration under kirkstone (even if it is limited)
2) Br
On 9/6/23 10:22, Max Krummenacher wrote:
From: Max Krummenacher
Hi
I'm trying to build and run latest OE master for a AM62 based machine
All builds fine.
I don't have the GPU working at runtime while the GPU works fine
using the 'same' configuration with kirkstone branches.
Apart from the GPU
From: Randolph Sapp
Meta-clang provides a bbappend for mesa to use clang to accelerate it's
rasterization with runtime code generation through the use of llvmpipe.
With the addition of mesa-pvr we no longer get this for free with the
blanket mesa bbappend on the devices that explicitly request me
From: Randolph Sapp
This won't really address the issue of why the driver won't currently
work against the upstream kernel, but at least it'll deal with the
current compilation errors.
Signed-off-by: Randolph Sapp
---
.../powervr-drivers/ti-img-rogue-driver_23.1.6404501.bb | 2 +-
1 fi
On 7/13/23 14:37, prane...@ti.com wrote:
From: Praneeth Bajjuri
commit 5f9be228390b ("machine: Add AM62Q HS-SE evm configuration")
has added am62xx-lp.inc which is used by am62xx-lp-evm machine.
The features listed in am62xx.inc are common between machines
am62xx-evm and am62xx-lp-evm. (Ex: MA
From: Randolph Sapp
Bump the SRCREV for the umlibs and driver package to include some fixes
for Jacinto devices. These patches do the following:
- Fix virtual memory addressing
- Resolve an issue with APM and debug requests
- Attempt to resolve most of the cache coherency related issues on
On 6/28/23 20:21, Ricardo Salveti wrote:
Provide a package file list based on the image path to avoid it later be
expanded by using the host system path.
Fixes a package QA error when files named similarly are provided by the
host system (e.g. /usr/bin/oclock is a match for /usr/bin/ocl*).
Sign
From: Randolph Sapp
The following patch was dropped from the SRC_URI one of my previous
graphics overhaul patches:
0001-compiler-support-OpenEmbedded-nodistro-internal-aarc.patch
Actually remove it from the source tree now that upstream is carrying
the equivalent to help enable other tools.
Sig
From: Randolph Sapp
Upstream changed to not be so picky about compilers. Bump SRCREV so the
odd things using our recipes are happy again.
Signed-off-by: Randolph Sapp
---
.../powervr-drivers/ti-img-rogue-driver_23.1.6404501.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
From: Randolph Sapp
Edit the file paths so they point at files in the source directory
explicitly. For some reason shell glob were previously only respected by
some machines.
Signed-off-by: Randolph Sapp
---
.../ti-img-rogue-umlibs_23.1.6404501.bb | 27 ++-
1 file changed
From: Randolph Sapp
Use RRECOMMENDS for components. Apparently I made an resolvable
dependency cycle that Yocto silently clipped. My best guess at the
culprit was: mesa-megadriver (RR) -> rogue-km (RR) -> rogue-um (RD) ->
libgles1-rogue (RD) -> mesa-megadriver
That killed the ti-img-rogue-umlibs
On 6/22/23 15:22, Randolph Sapp via lists.yoctoproject.org wrote:
From: Randolph Sapp
There's a weird issue with Yocto's caching system (though it may be
intentional behavior). Changing the package config won't always update
the package contents when you are directly modifyi
On 6/22/23 15:07, Randolph Sapp via lists.yoctoproject.org wrote:
On 6/21/23 13:26, Randolph Sapp via lists.yoctoproject.org wrote:
From: Randolph Sapp
Bumping into the limitations of the binary_package class. This change
allows all rogue components to be optionally packaged without blowing
From: Randolph Sapp
There's a weird issue with Yocto's caching system (though it may be
intentional behavior). Changing the package config won't always update
the package contents when you are directly modifying the recipe's deploy
directory if there is a cached build.
Oddly enough, if you edit
On 6/21/23 13:26, Randolph Sapp via lists.yoctoproject.org wrote:
From: Randolph Sapp
Bumping into the limitations of the binary_package class. This change
allows all rogue components to be optionally packaged without blowing
out the dependency chain.
Add a python function to fetch file paths
From: Randolph Sapp
Bumping into the limitations of the binary_package class. This change
allows all rogue components to be optionally packaged without blowing
out the dependency chain.
Add a python function to fetch file paths from the FILE vars for each
component so we don't end up double trac
On 6/21/23 02:58, Daniel Schultz wrote:
libx11-xcb has a hard dependency for x11 but is included by the
libvk-rogue package. Only include libvk-rogue when the
DISTRO_FEATURES "vulkan x11 wayland" are enabled, which is identical
to the RRECOMMENDS variable.
Signed-off-by: Daniel Schultz
---
Ho
On 6/6/23 16:21, Andrew Davis wrote:
On 6/6/23 2:33 PM, r...@ti.com wrote:
From: Randolph Sapp
Adding serial consoles to this variable makes systemd attempt to start a
Getty instance on them. Getty has no retry limit and no retry timout.
I'm sure you can guess where this is going.
This fixes
On 6/6/23 16:02, Denys Dmytriyenko wrote:
On Tue, Jun 06, 2023 at 11:37:06AM +0800, Xulin Sun via lists.yoctoproject.org
wrote:
Bring in KERNEL_CC variable to avoid below building issue:
WARNING: ti-img-rogue-driver-23.1.6404501-b do_package_qa: QA Issue:
File /lib/modules/6.1.31-rt10-yocto-pr
From: Randolph Sapp
Well, flew a bit too close to the sun on that last patch. Apparently
there are a few hidden runtime dependencies on the API devlinks that
make things like EGL upset when they aren't present.
We may circle back to this at some point but for now we're fine shipping
the devlinks
On 6/6/23 14:33, Randolph Sapp via lists.yoctoproject.org wrote:
From: Randolph Sapp
Adding serial consoles to this variable makes systemd attempt to start a
Getty instance on them. Getty has no retry limit and no retry timout.
I'm sure you can guess where this is going.
This fixe
From: Randolph Sapp
Adding serial consoles to this variable makes systemd attempt to start a
Getty instance on them. Getty has no retry limit and no retry timout.
I'm sure you can guess where this is going.
This fixes the endless start / stop Getty on ttyS0/ttyS3 messages that
will flood the log
On 6/5/23 12:17, Matthias Schnelte via lists.yoctoproject.org wrote:
Hello everyone,
I was trying to build kirkstone for am335x with a SGX GPU.
I was not able to use it with mesa.
On the latest kirkstone (1743b0101) (I tried it with the latest master, too) if
I set
PREFERRED_PROVIDER_virtual/
From: Randolph Sapp
Move recipes to new subdir since we offer more than just libgles now.
Reusing the naming convention of the subdirectory used for the km
components for now.
Signed-off-by: Randolph Sapp
---
.../ti-img-rogue-umlibs_23.1.6404501.bb | 0
.../{libgles =
From: Randolph Sapp
Bump the version and explicitly package all Khronos APIs separately.
This should be nice for those folks that want a headless opencl system
for tinkering and such.
This version includes experimental GEM support (for applications like
Chromium that like to poke at the render n
From: Randolph Sapp
Well, I'm trying to be nice for those few that want a truly minimal
yocto environment. Let's see how long it takes before I regret it.
Split all Khronos API libs into their own packages and adjust
dependencies as necessary. Use mesa's fancy function to set some
variables. We
On 5/30/23 16:58, Randolph Sapp via lists.yoctoproject.org wrote:
From: Randolph Sapp
Bump the version and explicitly package all Khronos APIs separately.
This should be nice for those folks that want a headless opencl system
for tinkering and such.
This version includes experimental GEM
On 5/30/23 17:01, Andrew Davis wrote:
On 5/30/23 4:58 PM, r...@ti.com wrote:
From: Randolph Sapp
Move recipes to new subdir since we offer more than just libgles now.
Reusing the naming convention of the subdirectory used for the km
components for now.
Signed-off-by: Randolph Sapp
---
.../
From: Randolph Sapp
Move recipes to new subdir since we offer more than just libgles now.
Reusing the naming convention of the subdirectory used for the km
components for now.
Signed-off-by: Randolph Sapp
---
.../ti-img-rogue-umlibs_23.1.6404501.bb | 0
.../{libgles =
From: Randolph Sapp
Well, I'm trying to be nice for those few that want a truly minimal
yocto environment. Let's see how long it takes before I regret it.
Split all Khronos API libs into their own packages and adjust
dependencies as necessary. Use mesa's fancy function to set some
variables. We
From: Randolph Sapp
Bump the version and explicitly package all Khronos APIs separately.
This should be nice for those folks that want a headless opencl system
for tinkering and such.
This version includes experimental GEM support (for applications like
Chromium that like to poke at the render n
On 5/30/23 13:18, Andrew Davis wrote:
On 5/30/23 1:11 PM, Randolph Sapp wrote:
On 5/30/23 13:03, Andrew Davis wrote:
On 5/24/23 3:03 PM, r...@ti.com wrote:
From: Randolph Sapp
Adding serial consoles to this variable makes systemd attempt to
start a
Getty instance on them. Getty has no retr
On 5/30/23 13:03, Andrew Davis wrote:
On 5/24/23 3:03 PM, r...@ti.com wrote:
From: Randolph Sapp
Adding serial consoles to this variable makes systemd attempt to start a
Getty instance on them. Getty has no retry limit and no retry timout.
I'm sure you can guess where this is going.
This fixe
On 5/30/23 10:51, Andrew Davis wrote:
On 5/26/23 8:58 PM, Randolph Sapp via lists.yoctoproject.org wrote:
From: Randolph Sapp
Move recipe to new rogue subdir since we offer more than just libgles
now.
I did something like this as part of:
https://lists.yoctoproject.org/g/meta-ti/message
From: Randolph Sapp
Bump the version and explicitly package all Khronos APIs separately.
This should be nice for those folks that want a headless opencl system
for tinkering and such.
This version includes experimental GEM support (for applications like
Chromium that like to poke at the render n
From: Randolph Sapp
Well, I'm trying to be nice for those few that want a truly minimal
yocto environment. Let's see how long it takes before I regret it.
Split all Khronos API libs into their own packages and adjust
dependencies as necessary. Use mesa's fancy function to set some
variables. We
From: Randolph Sapp
Move recipe to new rogue subdir since we offer more than just libgles
now.
Signed-off-by: Randolph Sapp
---
.../{libgles => rogue}/ti-img-rogue-umlibs_23.1.6404501.bb| 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename meta-ti-bsp/recipes-graphics/{libgles =
From: Randolph Sapp
Adding serial consoles to this variable makes systemd attempt to start a
Getty instance on them. Getty has no retry limit and no retry timout.
I'm sure you can guess where this is going.
This fixes the endless start / stop Getty on ttyS0/ttyS3 messages that
will flood the log
From: Randolph Sapp
Cleanup the J* APM patch a little. Apparently I could have stood to read
the docs a little more. Found some better runtime pm functions and also
discovered something new about the power island definition.
Notes from upstream:
- Add the CCB coherency HACK from DDK 1.15
On 5/16/23 17:29, Randolph Sapp via lists.yoctoproject.org wrote:
From: Randolph Sapp
Rename the .wks to .wks.in so the EFI_PROVIDER variable is expanded
properly. We only ever set a soft recommendation for GRUB. If anyone
attempted to change that previously it was ignored (for more than just
From: Randolph Sapp
Rename the .wks to .wks.in so the EFI_PROVIDER variable is expanded
properly. We only ever set a soft recommendation for GRUB. If anyone
attempted to change that previously it was ignored (for more than just
the reason here, but that's out of my control).
Add a timeout for th
On 5/11/23 13:40, Denys Dmytriyenko wrote:
From: Denys Dmytriyenko
There are some unobvious issues with adding PVR support to Mesa
via a bbappend:
1. We need to mark mesa package as machine-specific, due to
differences in builds between SGX, Rogue and software-rendering
2. We also need to the
1 - 100 of 193 matches
Mail list logo
