summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp/conf/machine/am64xx-evm-k3r5-sr2-hs-se.conf
diff options
context:
space:
mode:
authorDenys Dmytriyenko <denys@konsulko.com>2023-05-11 18:40:49 +0000
committerRyan Eatmon <reatmon@ti.com>2023-05-11 14:19:01 -0500
commit24e9324551ecd853b7fa5326fadface547b96652 (patch)
tree87f05dc899485c047a3de1c9e1b14f7f6d18564a /meta-ti-bsp/conf/machine/am64xx-evm-k3r5-sr2-hs-se.conf
parentf3a081a6c22773bba1fdf5e488ff7dec30c3dc84 (diff)
downloadmeta-ti-24e9324551ecd853b7fa5326fadface547b96652.tar.gz
mesa-pvr: convert bbappend into standalone alternative provider
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 then mark mesa package as providing safe ABIs (EGL/GLES/GBM) in order for all generic dependent packages to not be treated as machine-specific, allowing their re-use across different machines of the same architecture But doing the above alters the upstream mesa package and changes its signatures even when not building for TI platforms, which is a Yocto Project compliance violation. In order to resolve this issue, convert Mesa bbappend, that adds PVR support, into its own standalone alternative provider, called mesa-pvr and allow selecting it with PREFERRED_PROVIDER settings. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
Diffstat (limited to 'meta-ti-bsp/conf/machine/am64xx-evm-k3r5-sr2-hs-se.conf')
0 files changed, 0 insertions, 0 deletions