Date: Tue, 21 Apr 2020 09:45:37 -0500 From: Justin Hibbits <chmeeedalf@gmail.com> To: Vladimir Kondratyev <vladimir@kondratyev.su> Cc: Niclas Zeising <zeising@FreeBSD.org>, src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r360126 - head/sys/dev/evdev Message-ID: <20200421094537.1e26836e@titan.knownspace> In-Reply-To: <9e1f8218-916d-82cb-348f-326fc651115d@kondratyev.su> References: <202004201617.03KGHHj7074077@repo.freebsd.org> <20200420113957.50d41308@titan.knownspace> <9e1f8218-916d-82cb-348f-326fc651115d@kondratyev.su>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 20 Apr 2020 22:13:51 +0300 Vladimir Kondratyev <vladimir@kondratyev.su> wrote: > On 20.04.2020 19:39, Justin Hibbits wrote: > > But I'm curious, why not attach to sysmouse(4) and kbdmux(4)? What > > breakage does that cause? I could maybe see not attaching to > > sysmouse(4) by default, if the protocol isn't expressive enough, but > > kbdmux(4) should be sufficient. > > > > - Justin > > kbdmux(4) is pretty good for standard 102-104-keys keyboards found at > common desktops. > > But it does not work that good with some laptop ones. > > There are no "Flight mode on/off", "Touchpad on/off" e.t.c. events > defined in AT-keyset but they exist in evdev-keyset. > > Unfortunately, we do not support keymap uploading in our drivers yet > to make utilization of this advantage easy > > but IMO its better to switch to direct key-event reporting earlier > rather than later. > Thanks for that explanation. I tried thinking of any way these capabilities could be added to kbdmux, but they really are keyboard specific events, so wouldn't belong in kbdmux anyway. I'd be interested in adding the necessary capabilities to adb(4), to remove this special casing. I have a PowerBook G4 Ti to use for such a task. - Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200421094537.1e26836e>