From owner-freebsd-current@freebsd.org  Wed Mar 11 18:57:23 2020
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id 945B7267B9E;
 Wed, 11 Mar 2020 18:57:23 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 48d1RQ573Wz4g2T;
 Wed, 11 Mar 2020 18:57:22 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from pi by home.opsec.eu with local (Exim 4.92.3 (FreeBSD))
 (envelope-from <pi@freebsd.org>)
 id 1jC6XX-000Joj-Ng; Wed, 11 Mar 2020 19:57:11 +0100
Date: Wed, 11 Mar 2020 19:57:11 +0100
From: Kurt Jaeger <pi@freebsd.org>
To: Peter Jeremy <peter@rulingia.com>
Cc: Niclas Zeising <zeising@freebsd.org>,
 Greg 'groggy' Lehey <grog@freebsd.org>,
 Poul-Henning Kamp <phk@phk.freebsd.dk>,
 FreeBSD current users <FreeBSD-current@freebsd.org>,
 FreeBSD Stable Users <freebsd-stable@freebsd.org>
Subject: Re: New Xorg - different key-codes
Message-ID: <20200311185711.GY37073@home.opsec.eu>
References: <6762.1583886003@critter.freebsd.dk>
 <20200311004635.GB89512@eureka.lemis.com>
 <f130773f-7d68-2062-3ada-e9ebd888a5fe@freebsd.org>
 <20200311185345.GG3091@server.rulingia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200311185345.GG3091@server.rulingia.com>
X-Rspamd-Queue-Id: 48d1RQ573Wz4g2T
X-Spamd-Bar: -
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [-1.43 / 15.00];
 local_wl_from(0.00)[freebsd.org];
 NEURAL_HAM_MEDIUM(-0.54)[-0.538,0];
 NEURAL_HAM_LONG(-0.89)[-0.888,0];
 ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Mar 2020 18:57:23 -0000

Hi!

> On 2020-Mar-11 10:29:08 +0100, Niclas Zeising <zeising@freebsd.org> wrote:
> >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.
> 
> The UPDATING entry says that it's switched from devd to udev.  There's no
> mention of evdev or that the keycodes have been roto-tilled.  It's basically
> a vanilla "things have been changed, see the documentation" entry.  Given
> that entry, it's hardly surprising that people are confused.

Thanks. I was wondering myself, what/where there's mention of this.

-- 
pi@opsec.eu            +49 171 3101372                    Now what ?