mirror of
https://gitlab.freedesktop.org/mesa/drm.git
synced 2025-12-20 04:40:09 +01:00
b0815faac0
There is an excellent writeup explaining this requirement here:
https://gitlab.freedesktop.org/wayland/wayland/-/issues/175
In short, for mixed environments such as the Steam Runtime and other
container-like environments, choosing which libdrm to link into the
client's address space is a hard problem. If the runtime has a newer
libdrm than the host, then it should be preferred, because the client
may be using newly-added symbols. But if the host has a newer libdrm,
then that should be used, because drivers may be depending on those.
Bumping the DSO minor version is transparent to all users because apps
only link against the major version, e.g. DT_NEEDED libdrm.so.2; the
fact that libdrm.so.2 is a link to libdrm.so.2.122.0 is a detail known
only to the loader, but it does let a smart runtime make better
decisions.
Signed-off-by: Daniel Stone <daniels@collabora.com>
|
||
|---|---|---|
| .. | ||
| Android.bp | ||
| Android.sources.bp | ||
| etnaviv-symbols.txt | ||
| etnaviv_bo.c | ||
| etnaviv_bo_cache.c | ||
| etnaviv_cmd_stream.c | ||
| etnaviv_device.c | ||
| etnaviv_drm.h | ||
| etnaviv_drmif.h | ||
| etnaviv_gpu.c | ||
| etnaviv_perfmon.c | ||
| etnaviv_pipe.c | ||
| etnaviv_priv.h | ||
| libdrm_etnaviv.pc.in | ||
| meson.build | ||