On 4/6/23 14:28, Andrew Davis wrote:
Previously the virtual/gpudriver provider would point to the kernel-mode
driver, which would cause Mesa libraries to depend on those and not the
user-mode driver. It is the user-mode driver that should depend on the
kernel-mode driver, not the other way around. The logical dependency
chain should be:
App -> virtual/libgl -> Mesa -> virtual/gpudriver -> IMG-UM -> IMG-KM
We already talked about this so I'm fine with it.
Flip the dependency chain so it matches the above. While here make
the UM driver depend on, not just recommend, the KM driver as it is
not functional with out it.
Signed-off-by: Andrew Davis <[email protected]>
...
-RRECOMMENDS:mesa-megadriver:append:class-target = "
${@d.getVar('PREFERRED_PROVIDER_virtual/gpudriver')}"
+RDEPENDS:mesa-megadriver:append:class-target = "
${@d.getVar('PREFERRED_PROVIDER_virtual/gpudriver')}"
I have issues with making this a full dependency here. We're adding the
PVR components to mesa, software rendering is still there as a fallback.
If someone wishes to remove the powervr umlibs with OPKG having this as
a hard dependency will break a lot of things.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16310):
https://lists.yoctoproject.org/g/meta-ti/message/16310
Mute This Topic: https://lists.yoctoproject.org/mt/98112282/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
