On ASUS 1001PXD, _BQC returns an out of range value which makes
acpivout_get_brightness() return -1, in turn breaking the
display.brightness control (wsconsctl displays a mangled value).
This diff ignores the out of range value and makes the brighness
control just work again.
OK?
Index: acpivout
This patch makes two changes in the way pms(4) handles Synaptics touchpads.
It addresses problems that lead to this bug report:
https://marc.info/?l=openbsd-bugs&m=158278943515495&w=2
Tests for regressions and OKs would be welcome.
1) The patched version doesn't enable the so-called "extended
hi,
please enable the mbg device for the amd64 kernel. I'm using a Meinberg PCI511
device on amd64 with a patched kernel without any issues.
I've attached dmesg + device specific systl hw.
The single change are these two lines copied over from i386 config:
hell$ diff -u GENERIC WITHMBG
--- GEN
On Fri, Mar 13, 2020 at 05:54:01PM +0100, Rob Schmersel wrote:
> On Fri, 13 Mar 2020 16:31:18 +0100
> Patrick Wildt wrote:
> > Thanks for the diff! Since Linux uses the same firmware (43340) for
> > both 43340 and 43341, I commited the diff slightly differently to
> > follow their scheme. Thus t
On Fri, 13 Mar 2020 16:31:18 +0100
Patrick Wildt wrote:
> On Fri, Mar 13, 2020 at 02:49:33PM +0100, Rob Schmersel wrote:
> > Hi,
> >
> Thanks for the diff! Since Linux uses the same firmware (43340) for
> both 43340 and 43341, I commited the diff slightly differently to
> follow their scheme.
On Fri, Mar 13, 2020 at 02:49:33PM +0100, Rob Schmersel wrote:
> Hi,
>
> I got a new toy to play with recently which uses a bcm43341 wireless
> chipset. This chipset is the same as the bcm43340 apart from an
> additional nfc mode and can re-use the brcmfmac43340-sdio.bin firmware.
> (I simply adde
Hi,
I got a new toy to play with recently which uses a bcm43341 wireless
chipset. This chipset is the same as the bcm43340 apart from an
additional nfc mode and can re-use the brcmfmac43340-sdio.bin firmware.
(I simply added a symbolic link from firmware supplied in the
bwfm-firmware package)
In
Hi,
After reading the flock(2) code I cannot spot anything preventing it
from being unlocked. This is all made possible by the recent MP-safe
effort including atomic file flags and posix file locks.
I've been running with this for a week by now. However, testing is much
appreciated. Remember to ru
