created | 2021-04-10T23:48:55Z |
---|---|
begin | 2021-04-05T00:00:00Z |
end | 2021-04-06T00:00:00Z |
path | src/sys |
commits | 10 |
date | 2021-04-05T09:31:45Z | |||
---|---|---|---|---|
author | patrick | |||
files | src/sys/dev/fdt/sdhc_fdt.c | log | diff | annotate |
message |
Revert slow mode change so that we always use it for legacy and high speed timings, and if the device tree tells us to. While the change was done to reduce diff, it introduced a regression on some devices, hence this revert. Reported and tested by dtucker@ Tested by kettenis@ and myself |
date | 2021-04-05T12:13:07Z | |||
---|---|---|---|---|
author | dtucker | |||
files | src/sys/dev/fdt/mvsw.c | log | diff | annotate |
message | Fix typo in debug message. ok kettenis@ |
date | 2021-04-05T14:36:18Z | |||
---|---|---|---|---|
author | kn | |||
files | src/sys/dev/fdt/simpleaudio.c | log | diff | annotate |
message |
Set sysclk before using it simpleaudio_set_params() calls set_params() which reads sysclk off the "i2s_clk" property before it sets that very clock's rate with dd_set_sysclk() (in case there's multiplier specified). Hence reverse the order so set_params() can pick up the newly set rate. The rate is still off on the Pinebook Pro, but I came across this when reading the code; this also matches NetBSD's sys/dev/fdt/ausoc.c r1.6 "Set sysclk rate at set_format time, so the link set_format callback can read the new sysclk". OK kettenis patrick |
date | 2021-04-05T16:17:25Z | |||
---|---|---|---|---|
author | landry | |||
files | src/sys/dev/usb/usbdevs | log | diff | annotate |
message | Add 0x413d:0x2107 for various PCSensors TEMPer devices |
date | 2021-04-05T16:18:32Z | |||
---|---|---|---|---|
author | landry | |||
files | src/sys/dev/usb/usbdevs.h | log | diff | annotate |
src/sys/dev/usb/usbdevs_data.h | log | diff | annotate | |
message | sync |
date | 2021-04-05T16:26:06Z | |||
---|---|---|---|---|
author | landry | |||
files | src/sys/dev/usb/ugold.c | log | diff | annotate |
message |
ugold(4): add support for TEMPerGold & more TEMPerHUM devices originally from mlarkin@ for TEMPerGold_V3.1 (only a temperature sensor), i just added TEMPerX variants to the mix - all those devices share the same usb product id (boo), so differentiate them on the firmware string... even if the device is labelled as TEMPerHUM and has a blue TXT button on it, its firmware reports itself as TEMPerX_V3.3. ok jung@ sthen@ mlarkin@ |
date | 2021-04-05T18:26:45Z | |||
---|---|---|---|---|
author | dv | |||
files | src/sys/arch/amd64/amd64/vmm.c | log | diff | annotate |
message |
Improve rdmsr/wrmsr exit handling for both AMD SVM and Intel VMX. At some point, the logic for handling vmexits related to msr access changed and the handling for SVM diverged from VMX. While booting the newest 9front release, abieber@ noticed boot loops on an AMD host. This commit changes the behavior to be the same between SVM and VMX hosts, with the exception of a single MSR, and enforces that any rdmsr instruction must be explicitly handled otherwise a #GP is injected into the guest. Any wrmsr instructions that are not explicitly handled are ignored (%rax, %rdx set to 0). The PAT msr is now shadowed, allowing guests to read a copy of the host PAT. Their writes are stored in guest vcpu state and not passed through to the host cpu. (PAT writes are validated, however, and invalid values inject #GP.) tested by brynet@, abieber@ ok brynet@, mlarkin@ |
date | 2021-04-05T18:26:46Z | |||
---|---|---|---|---|
author | dv | |||
files | src/sys/arch/amd64/include/vmmvar.h | log | diff | annotate |
message |
Improve rdmsr/wrmsr exit handling for both AMD SVM and Intel VMX. At some point, the logic for handling vmexits related to msr access changed and the handling for SVM diverged from VMX. While booting the newest 9front release, abieber@ noticed boot loops on an AMD host. This commit changes the behavior to be the same between SVM and VMX hosts, with the exception of a single MSR, and enforces that any rdmsr instruction must be explicitly handled otherwise a #GP is injected into the guest. Any wrmsr instructions that are not explicitly handled are ignored (%rax, %rdx set to 0). The PAT msr is now shadowed, allowing guests to read a copy of the host PAT. Their writes are stored in guest vcpu state and not passed through to the host cpu. (PAT writes are validated, however, and invalid values inject #GP.) tested by brynet@, abieber@ ok brynet@, mlarkin@ |
date | 2021-04-05T20:45:49Z | |||
---|---|---|---|---|
author | mglocker | |||
files | src/sys/dev/usb/usbdevs | log | diff | annotate |
src/sys/dev/usb/uvideo.c | log | diff | annotate | |
message |
Add a new quirk flag to not attach video devices which aren't supported by uvideo(4) currently, like the Chicony Integrated IR Camera. This is especially helpful when you have two video devices of which the unsupported one is attached first as reported by martijn@. OK gnezdo@ |
date | 2021-04-05T20:46:06Z | |||
---|---|---|---|---|
author | mglocker | |||
files | src/sys/dev/usb/usbdevs.h | log | diff | annotate |
src/sys/dev/usb/usbdevs_data.h | log | diff | annotate | |
message | regen |