Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In drm from linux >= 5.9 renoir no longer uses the gpu info firmware and
some reported hardware information changes.
'drm/amdgpu: use IP discovery table for renoir'
c1cf79ca5ced46ea6a7843cbe98836e4d51c6c52
Remove warning which is known to be harmless
https://gitlab.freedesktop.org/drm/amd/-/issues/1332
and was removed with mesa 20.2 in
'radeonsi/gfx10: implement most performance counters'
38a4b861459b02401d3ff71670218506e7acf019
|
|
From Roland Scheidegger
51a82ec3e437d1d2dc4c688578640d25b3e7f0a2 in mainline Mesa
|
|
From Marek Olsak
56cc10bd27b24d513de88bf7fa94a6c8f43e348f in mainline Mesa
|
|
From Jan Zielinski
52aa730d07618513d6c055618069b2f4680974cc in mainline Mesa
Encountered by naddy@ when doing a clang 11 build. This commit
suggested by patrick@
|
|
|
|
From Vinson Lee
ff8daa013621019f1606dc0c188b16f1ce34fea7 in mainline Mesa
fixes clang 11 build
mortimer@ had almost the same diff
|
|
|
|
With Mesa 20.1 even after the kernel change to do wbinvd on all cpus
sthen@ reported that hard hangs still occurred on his Haswell system
with inteldrm.
Mark Kane also reported seeing hangs on Ivy Bridge on bugs@.
Some systems/workloads seem to be more prone to triggering this than
others as I have not seen any hangs on Ivy Bridge and the only hangs
I saw on Haswell when running piglit went away with the wbinvd change.
It seems something is wrong with drm memory attributes or coherency in
the kernel and newer Mesa versions expect behaviour we don't have.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
On mips64, the compiler does not allow use of non-zero argument with
__builtin_frame_address(). However, the returned frame address is only
used when PIPE_ARCH_X86 is defined. The compile error can be avoided
by making #ifdef PIPE_ARCH_X86 cover the getting of frame address too.
The argument checking of __builtin_frame_address() has been present
as a debug assert in clang 8. In clang 10, there is a proper runtime
check for the argument. This is why the build has not failed before.
OK jsg@
|
|
From Eric Engestrom
7f5ef97a07d4054efb96f0d644344644023af82c in Mesa git
fixes llvmpipe renderer string showing "LLVM 16.0" with LLVM 10
|
|
|
|
distfiles when upstream removed autotools
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
From Brian Paul
02c3dad0f3b4d26e0faa5cc51d06bc50d693dcdc in mainline Mesa
"A security advisory (TALOS-2019-0857/CVE-2019-5068) found that
creating shared memory regions with permission mode 0777 could allow
any user to access that memory. Several Mesa drivers use shared-
memory XImages to implement back buffers for improved performance.
This path changes the shmget() calls to use 0600 (user r/w).
Tested with legacy Xlib driver and llvmpipe."
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|