Date: Wed, 11 Mar 2020 09:37:27 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Niclas Zeising <zeising@freebsd.org> Cc: "Greg 'groggy' Lehey" <grog@FreeBSD.org>, FreeBSD current users <FreeBSD-current@FreeBSD.ORG>, FreeBSD Stable Users <freebsd-stable@freebsd.org> Subject: Re: New Xorg - different key-codes Message-ID: <8844.1583919447@critter.freebsd.dk> In-Reply-To: <f130773f-7d68-2062-3ada-e9ebd888a5fe@freebsd.org> References: <6762.1583886003@critter.freebsd.dk> <20200311004635.GB89512@eureka.lemis.com> <f130773f-7d68-2062-3ada-e9ebd888a5fe@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <f130773f-7d68-2062-3ada-e9ebd888a5fe@freebsd.org>, Niclas Zeis= ing w rites: >This has to do with switching to using evdev to handle input devices on = >FreeBSD 12 and CURRENT. There's been several reports, and suggested = >solutions to this, as well as an UPDATING entry detailing the change. I don't think I would have thought the rather counter-intuitive behaviour I saw yesterday, even if you had told me in those very words that the scan-codes had changed :-) -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8844.1583919447>