| created | 2022-09-22T04:15:30Z |
|---|---|
| begin | 2022-09-16T00:00:00Z |
| end | 2022-09-17T00:00:00Z |
| path | src/sys |
| commits | 12 |
| date | 2022-09-16T01:48:07Z | |||
|---|---|---|---|---|
| author | jsg | |||
| files | src/sys/dev/pci/drm/drm_linux.c | log | diff | annotate |
| src/sys/dev/pci/drm/include/linux/dma-fence.h | log | diff | annotate | |
| message |
mask non-chain fence sequence numbers to 32-bit for comparisons Most of drm uses 32-bit sequence numbers in fences. dma-fence-chain opts into 64-bit comparisons. Wrapping is handled like i915_seqno_passed() except that if the sequence numbers are the same one is not considered later than the other. |
|||
| date | 2022-09-16T02:16:44Z | |||
|---|---|---|---|---|
| author | jsg | |||
| files | src/sys/dev/pci/drm/drm_gem.c | log | diff | annotate |
| src/sys/dev/pci/drm/drm_internal.h | log | diff | annotate | |
| src/sys/dev/pci/drm/drm_prime.c | log | diff | annotate | |
| message |
drm/gem: Fix GEM handle release errors From Jeffy Chen 1f574fbe9c2b831a8c3156260842a7abd280d59f in linux 5.15.y/5.15.68 ea2aa97ca37a9044ade001aef71dbc06318e8d44 in mainline linux |
|||
| date | 2022-09-16T02:18:48Z | |||
|---|---|---|---|---|
| author | jsg | |||
| files | src/sys/dev/pci/drm/amd/amdgpu/amdgpu_psp.c | log | diff | annotate |
| src/sys/dev/pci/drm/amd/amdgpu/amdgpu_xgmi.c | log | diff | annotate | |
| message |
drm/amdgpu: Move psp_xgmi_terminate call from amdgpu_xgmi_remove_device to psp_hw_fini From YiPeng Chai c15c2c2c08964fd99d3366f80742129f8ae28eaa in linux 5.15.y/5.15.68 9d705d7741ae70764f3d6d87e67fad3b5c30ffd0 in mainline linux |
|||
| date | 2022-09-16T02:20:28Z | |||
|---|---|---|---|---|
| author | jsg | |||
| files | src/sys/dev/pci/drm/amd/amdgpu/gfx_v9_0.c | log | diff | annotate |
| message |
drm/amdgpu: Check num_gfx_rings for gfx v9_0 rb setup. From Candice Li 622a557b28b718d4da92ff3504d83af2310324d2 in linux 5.15.y/5.15.68 c351938350ab9b5e978dede2c321da43de7eb70c in mainline linux |
|||
| date | 2022-09-16T02:22:45Z | |||
|---|---|---|---|---|
| author | jsg | |||
| files | src/sys/dev/pci/drm/radeon/radeon_device.c | log | diff | annotate |
| message |
drm/radeon: add a force flush to delay work when radeon From Zhenneng Li 5a7a5b2edac4b05abd744eeaebda46d9dacd952d in linux 5.15.y/5.15.68 f461950fdc374a3ada5a63c669d997de4600dffe in mainline linux |
|||
| date | 2022-09-16T02:24:23Z | |||
|---|---|---|---|---|
| author | jsg | |||
| files | src/sys/dev/pci/drm/amd/amdgpu/mmhub_v1_0.c | log | diff | annotate |
| message |
drm/amdgpu: mmVM_L2_CNTL3 register not initialized correctly From Qu Huang ad5ef763dbbea8193bd2095a1401aeac6e8f74e8 in linux 5.15.y/5.15.68 b8983d42524f10ac6bf35bbce6a7cc8e45f61e04 in mainline linux |
|||
| date | 2022-09-16T02:26:35Z | |||
|---|---|---|---|---|
| author | jsg | |||
| files | src/sys/dev/pci/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.c | log | diff | annotate |
| message |
drm/amd/display: fix memory leak when using debugfs_lookup() From Greg Kroah-Hartman 58acd2ebae034db3bacf38708f508fbd12ae2e54 in linux 5.15.y/5.15.68 cbfac7fa491651c57926c99edeb7495c6c1aeac2 in mainline linux |
|||
| date | 2022-09-16T02:29:47Z | |||
|---|---|---|---|---|
| author | jsg | |||
| files | src/sys/dev/pci/drm/i915/display/intel_dp_link_training.c | log | diff | annotate |
| message |
drm/i915: Implement WaEdpLinkRateDataReload From Ville Syrjala d2ca79dd0b5487991dac52c6b679915dbd70ee4c in linux 5.15.y/5.15.68 672d6ca758651f0ec12cd0d59787067a5bde1c96 in mainline linux |
|||
| date | 2022-09-16T12:08:27Z | |||
|---|---|---|---|---|
| author | stsp | |||
| files | src/sys/dev/ic/mfireg.h | log | diff | annotate |
| message |
Make mfii(4) recover from firmware FAULT state on startup. In case firmware initially comes up in FAULT state, reset the device and give it one more chance to attach successfully. The Linux megaraid_sas driver applies the same workaround in this case. There seems to be a bug in some firmware versions which can trigger this behaviour; see mainline Linux commit 6431f5d7c6025f8b007af06ea090de308f7e6881 Problem observed by me with mfii(4) attached via KVM PCI-passthrough: mfii0 at pci0 dev 2 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05: msi mfii0: firmware fault With this workaround in place, attachment succeeds and the device works: mfii0 at pci0 dev 2 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05: msi mfii0: firmware fault; attempting full device reset, this can take some time mfii0: "RAID Ctrl SAS 6G 1GB (D3116C)", firmware 23.29.0-0019, 1024MB cache Tested for regressions on bare metal by Hrvoje with two different adapters: mfii0 at pci1 dev 0 function 0 "Symbios Logic MegaRAID SAS3508" rev 0x01: msi mfii0: "PERC H740P Mini ", firmware 51.16.0-4076, 8192MB cache mfii0 at pci4 dev 0 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05: msi mfii0: "ServeRAID M5110", firmware 23.34.0-0023, 512MB cache ok jmatthew@ |
|||
| date | 2022-09-16T12:08:28Z | |||
|---|---|---|---|---|
| author | stsp | |||
| files | src/sys/dev/pci/mfii.c | log | diff | annotate |
| message |
Make mfii(4) recover from firmware FAULT state on startup. In case firmware initially comes up in FAULT state, reset the device and give it one more chance to attach successfully. The Linux megaraid_sas driver applies the same workaround in this case. There seems to be a bug in some firmware versions which can trigger this behaviour; see mainline Linux commit 6431f5d7c6025f8b007af06ea090de308f7e6881 Problem observed by me with mfii(4) attached via KVM PCI-passthrough: mfii0 at pci0 dev 2 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05: msi mfii0: firmware fault With this workaround in place, attachment succeeds and the device works: mfii0 at pci0 dev 2 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05: msi mfii0: firmware fault; attempting full device reset, this can take some time mfii0: "RAID Ctrl SAS 6G 1GB (D3116C)", firmware 23.29.0-0019, 1024MB cache Tested for regressions on bare metal by Hrvoje with two different adapters: mfii0 at pci1 dev 0 function 0 "Symbios Logic MegaRAID SAS3508" rev 0x01: msi mfii0: "PERC H740P Mini ", firmware 51.16.0-4076, 8192MB cache mfii0 at pci4 dev 0 function 0 "Symbios Logic MegaRAID SAS2208" rev 0x05: msi mfii0: "ServeRAID M5110", firmware 23.34.0-0023, 512MB cache ok jmatthew@ |
|||
| date | 2022-09-16T15:57:23Z | |||
|---|---|---|---|---|
| author | mbuhl | |||
| files | src/sys/kern/sysv_msg.c | log | diff | annotate |
| src/sys/kern/sysv_sem.c | log | diff | annotate | |
| src/sys/sys/msg.h | log | diff | annotate | |
| src/sys/sys/sem.h | log | diff | annotate | |
| message |
semctl1 and msgctl were introduced for binary compatibility for OpenBSD 3.5. They are no longer needed. OK bluhm@ |
|||
| date | 2022-09-16T16:30:10Z | |||
|---|---|---|---|---|
| author | robert | |||
| files | src/sys/arch/arm64/dev/apldc.c | log | diff | annotate |
| src/sys/arch/arm64/dev/aplhidev.c | log | diff | annotate | |
| src/sys/dev/hid/hidkbd.c | log | diff | annotate | |
| src/sys/dev/hid/hidkbdsc.h | log | diff | annotate | |
| src/sys/dev/usb/ukbd.c | log | diff | annotate | |
| message |
move most of the key combination translation code out of ukbd(4) to hidkbd so that it can be re-used by apldc(4) and aplhidev(4) as well this also adds support for apple fn key combinations to aplhidev(4) ok miod@ |
|||