Date: Fri, 29 Sep 2017 22:04:27 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-usb@FreeBSD.org Subject: [Bug 222646] ukbd(4): support Consumer Control based multimedia keys Message-ID: <bug-222646-17-MYyaqulLhX@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-222646-17@https.bugs.freebsd.org/bugzilla/> References: <bug-222646-17@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222646 --- Comment #4 from Vladimir Kondratyev <wulf@freebsd.org> --- (In reply to Greg V from comment #3) > Pressing both volume buttons on my mouse results in the two keys pressed-= released in order. Did you observed it with evemu or with libinput? Please use former as it connects directly to input device and gives raw data. > Some devices *might* support simultaneous presses of multiple media keys,= but I think in that case, we would just lose the extra key presses. I recently implemented evdev support for consumer page for bluetooth keyboa= rds (not publicly available yet) and found out that my bt-keyboard loses *relea= se* events on simultaneous presses as it is unable to report "which key has been depressed" at HID-protocol level. It is capable only to say that "last/all = key has been depressed" so my driver has to generate release event at next interrupt at his own. I do not see how your patch does such "autorelease". Maybe ukbd does this automagically? I should look deeper in its internals. Unfortunately I cant do hardware testing now --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-222646-17-MYyaqulLhX>