Philip Guenther <guent...@gmail.com> wrote: > On Fri, Dec 13, 2019 at 4:39 AM Patrick Wildt <patr...@openbsd.org> wrote: > > > CVSROOT: /cvs > > Module name: src > > Changes by: patr...@cvs.openbsd.org 2019/12/13 05:39:08 > > > > Modified files: > > sys/dev/acpi : acpivout.c > > > > Log message: > > Make acpivout(4) call ws_[gs]et_param instead of directly > > calling the ACPI methods. On some machines, like my X395, > > those ACPI methods don't allow changing the brightness, so > > this allows acpivout(4) to e.g. use amdgpu(4)'s code. > > > > ok kettenis@ > > > > This is fatal on my X1: pushing a brightness control button panics > instantly with "rw_enter: acpil locking against myself" with a traceback > panic <- rw_enter <- acpivout_get_param <- acpi_notify <- acpi_notify_task > <- acpi_thread
x1 "r7" right?
