Skip to content

ti-img-rouge-umlibs: housekeeping and version bump

[email protected] yocto-meta-ti 3 versions – New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v3 Latest2 patches 0 repliesNew
  2. v22 patches 3 repliesSuperseded
  3. v12 patches 3 repliesSuperseded

Patches in v3 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2libgles: rename subdir to powervr-umlibsmeta-ti-bsp/recipes-graphics/powervr-umlibs/ti-img-rogue-umlibs_23.1.6404501.bb meta-ti-bsp/recipes-graphics/powervr-umlibs/ti-sgx-ddk-um/pvrsrvkm.rules meta-ti-bsp/recipes-graphics/powervr-umlibs/ti-sgx-ddk-um_1.17.4948957.bb+0 -00 replies
2/2ti-img-rogue-umlibs: bump version and explicitly packagemeta-ti-bsp/recipes-bsp/powervr-drivers/ti-img-rogue-driver_23.1.6404501.bb meta-ti-bsp/recipes-graphics/powervr-umlibs/ti-img-rogue-umlibs_23.1.6404501.bb+64 -260 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.

Read the v3 thread

Cover letter [meta-ti][master/kirkstone][PATCHv3 0/2] ti-img-rouge-umlibs: housekeeping and version bump

From: Randolph Sapp <[email protected]>

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 won't set the provides or conflicts args just yet. Software rendering is still nice to have as a fallback, but I'll drop it if anyone in the community wants it gone for minimal image reasons.

Also bump the umlib and km versions. Add some rough gem support for now. Should get some userspace applications like Chromium to start behaving a little better. This is still experimental, but I don't think it'll break anything that's already been working.

This version changes the libgles subdir to powervr-umlibs, keeping in line with the naming convention used by the kernel modules.

---

Ugh, apparently something from testing slipped into a commit again. If the ${PN}-dev package is present in the packages string yocto will automatically sort out all the dev links, and with this driver there one dev link that's always required for mesa interactions:

libpvr_dri_support.so

Drop the dev package from the packages string. Most of the links aren't needed but since we've got to ignore the sanity check anyway (and the link names are currently unique). We'll just go ahead and ship all the core driver devlinks in case something weird changes in the future.

Randolph Sapp (2):
libgles: rename subdir to powervr-umlibs
ti-img-rogue-umlibs: bump version and explicitly package

 .../ti-img-rogue-driver_23.1.6404501.bb       |   2 +-
 .../ti-img-rogue-umlibs_23.1.6404501.bb       |  73 ------------
 .../ti-img-rogue-umlibs_23.1.6404501.bb       | 111 ++++++++++++++++++
 .../ti-sgx-ddk-um/pvrsrvkm.rules              |   0
 .../ti-sgx-ddk-um_1.17.4948957.bb             |   0
 5 files changed, 112 insertions(+), 74 deletions(-)
 delete mode 100644 meta-ti-bsp/recipes-graphics/libgles/ti-img-rogue-umlibs_23.1.6404501.bb
 create mode 100644 meta-ti-bsp/recipes-graphics/powervr-umlibs/ti-img-rogue-umlibs_23.1.6404501.bb
 rename meta-ti-bsp/recipes-graphics/{libgles => powervr-umlibs}/ti-sgx-ddk-um/pvrsrvkm.rules (100%)
 rename meta-ti-bsp/recipes-graphics/{libgles => powervr-umlibs}/ti-sgx-ddk-um_1.17.4948957.bb (100%)
Signature · 1 line
2.40.1