From owner-freebsd-x11@freebsd.org Thu Mar 2 17:11:07 2017 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3ED1FCF5D4B for ; Thu, 2 Mar 2017 17:11:07 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 192A0103 for ; Thu, 2 Mar 2017 17:11:07 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) Received: from [IPv6:::1] (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by freefall.freebsd.org (Postfix) with ESMTP id 26D9B1F67 for ; Thu, 2 Mar 2017 17:11:06 +0000 (UTC) (envelope-from jonathan@FreeBSD.org) To: freebsd-x11@freebsd.org From: Jonathan Anderson Subject: X input: devd, dbus, hald, evdev... ??? Message-ID: Date: Thu, 2 Mar 2017 13:41:05 -0330 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 17:11:07 -0000 Hi all, It seems like there's been a lot of churn in X lately, so I have a few questions about the current state of play for input devices. Apologies in advance for the barrage. :) I notice that the handbook (https://www.freebsd.org/doc/handbook/x-config.html) doesn't mention dbus or hald, so are they not needed any more? Is everything meant to be handled automatically through devd? Should I remove the hald_enable line from /etc/rc.conf? dbus_enable? How does evdev/webcamd fit into the picture? I see that devd is starting an instances webcamd for my touchpad and touchscreen, but when I install xf86-input-evdev, it does funny things to my keyboard input. Should X be able to detect input devices under /dev/input automatically, or do I need to explicitly configure them? I think that I need an explicit driver config for my drm-next setup, so does that mean that I also need to create explicit ServerLayout, Screen, Keyboard, Mouse, etc., files in /usr/local/etc/X11/xorg.conf.d? In sum... how is this all meant to fit together? Thanks, Jon -- jonathan@FreeBSD.org