created | 2021-08-15T00:09:20Z |
---|---|
begin | 2021-08-11T00:00:00Z |
end | 2021-08-12T00:00:00Z |
path | src/sys |
commits | 9 |
date | 2021-08-11T03:06:57Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/pci/drm/i915/i915_cmd_parser.c | log | diff | annotate |
src/sys/dev/pci/drm/i915/gem/i915_gem_execbuffer.c | log | diff | annotate | |
message |
drm/i915: Revert "drm/i915/gem: Asynchronous cmdparser" From Jason Ekstrand 6976f3cf34a1a8b791c048bbaa411ebfe48666b1 in linux 5.10.y/5.10.57 c9d9fdbc108af8915d3f497bbdf3898bf8f321b8 in mainline linux |
date | 2021-08-11T03:08:26Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/pci/drm/i915/gem/i915_gem_execbuffer.c | log | diff | annotate |
message |
drm/i915: avoid uninitialised var in eb_parse() The backport of c9d9fdbc108af8915d3f497bbdf3898bf8f321b8 to 5.10 in 6976f3cf34a1a8b791c048bbaa411ebfe48666b1 removed more than it should have leading to 'batch' being used uninitialised. The 5.13 backport and the mainline commit did not remove the portion this patch adds back. Sent to the linux stable list and queued to be in 5.10.58. |
date | 2021-08-11T03:10:43Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/pci/drm/i915/i915_request.c | log | diff | annotate |
message |
Revert "drm/i915: Propagate errors on awaiting already signaled fences" From Jason Ekstrand 118b070bf415eb6c0fa39e5fa1b1ef6b83e80cee in linux 5.10.y/5.10.57 3761baae908a7b5012be08d70fa553cc2eb82305 in mainline linux |
date | 2021-08-11T03:12:47Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/pci/drm/amd/display/dc/dml/dcn21/display_mode_vba_21.c | log | diff | annotate |
message |
drm/amd/display: Fix comparison error in dcn21 DML From Victor Lu f9d875c8c92f1bdaeeb3eeccbf8402974f20cd31 in linux 5.10.y/5.10.57 ec3102dc6b36c692104c4a0546d4119de59a3bc1 in mainline linux |
date | 2021-08-11T03:15:51Z | |||
---|---|---|---|---|
author | jsg | |||
files | src/sys/dev/pci/drm/amd/display/dc/dcn20/dcn20_resource.c | log | diff | annotate |
message |
drm/amd/display: Fix max vstartup calculation for modes with borders From Nicholas Kazlauskas 98b070694f4570908a0e8ea5afb68d81b0aa2051 in linux 5.10.y/5.10.57 d7940911fc0754d99b208f0e3098762d39f403a0 in mainline linux |
date | 2021-08-11T16:14:00Z | |||
---|---|---|---|---|
author | sthen | |||
files | src/sys/dev/pci/drm/drm_linux.c | log | diff | annotate |
src/sys/dev/pci/drm/include/linux/irq_work.h | log | diff | annotate | |
message |
backout drm/include/linux/irq_work.h r1.4 and drm/drm_linux.c r1.83 problems with suspend on various ThinkPad machines seen by me, tb@, deraadt@, benno@ seem to go away with this reverted. |
date | 2021-08-11T18:15:50Z | |||
---|---|---|---|---|
author | tb | |||
files | src/sys/arch/amd64/amd64/est.c | log | diff | annotate |
message |
Make hw.setperf percentages proportional to the enhanced speed step frequencies on intel processors. This way, the default hw.setperf=99 corresponds to the maximum ordinary speed while setting it to 100 enables turbo mode. Tested in snaps for a week, positive feedback from several. |
date | 2021-08-11T18:31:48Z | |||
---|---|---|---|---|
author | tb | |||
files | src/sys/arch/amd64/amd64/k1x-pstate.c | log | diff | annotate |
message |
Do not read the status MSR before setting performance adjustment mode. This makes modifying hw.setperf and apmd -A work on robert's laptop. Previously, it would sometimes be impossible to set hw.setperf to any value on this machine. Keep a delay loop that waits for the MSR write to take effect before setting hw.cpuspeed to the new value since this is apparently needed for some pre-ryzen processors. Debugging, initial diff & test by robert ok brynet |
date | 2021-08-11T18:46:11Z | |||
---|---|---|---|---|
author | tb | |||
files | src/sys/arch/i386/i386/k1x-pstate.c | log | diff | annotate |
message |
sync with amd64 k1x-pstate.c r1.11 reminded by brynet |