From owner-freebsd-current@FreeBSD.ORG Thu Nov 8 19:20:25 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F313748 for ; Thu, 8 Nov 2012 19:20:25 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 1867C8FC08 for ; Thu, 8 Nov 2012 19:20:24 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id qA8JKEi7053678; Thu, 8 Nov 2012 12:20:14 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id qA8JKE1l053675; Thu, 8 Nov 2012 12:20:14 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Thu, 8 Nov 2012 12:20:14 -0700 (MST) From: Warren Block To: Ian Lepore Subject: Re: 9.1-RC3 feels okay :-) In-Reply-To: <1352390005.17290.71.camel@revolution.hippie.lan> Message-ID: References: <201211062158.qA6Lvt2l039276@fire.js.berklix.net> <1352390005.17290.71.camel@revolution.hippie.lan> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Thu, 08 Nov 2012 12:20:14 -0700 (MST) Cc: "Julian H. Stacey" , freebsd-current@freebsd.org, CeDeROM X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Nov 2012 19:20:25 -0000 On Thu, 8 Nov 2012, Ian Lepore wrote: > On Thu, 2012-11-08 at 08:45 -0700, Warren Block wrote: >> On Thu, 8 Nov 2012, CeDeROM wrote: >> >>> I have tested additional options in xorg runtime :-) >>> >>> With the patched xorg mouse driver 1.7.1 (or driver version >=1.7.2) >>> situation is following: >>> >>> 1. With hald and dbus no xorg.conf file is needed. However it might bo >>> option to pass some additional featutes parameters with xorg.conf. >>> 2. With no hald and dbus mouse and keyboard does not work in xorg unless >>> Option "AllowEmptyInput" "False" is added to Section "ServerLayout" by >>> hand in xorg.conf. Without this option input does not work even if >>> xorg.conf defines it! AllowEmptyInput=False forces to detect input deviced >>> by Xorg at startup. >> >> No. AllowEmptyInput is wrong. It was causing so many problems that it >> has been removed from later xorg-server releases. > > This is disturbing news. We build embedded systems at work that use X > for presentation and have no input devices. I understand that > AllowEmptyInput is inappropriate to work around the problem we're > discussing here, but that doesn't mean it's never needed. The xorg folks should be able to suggest the right replacement. >> Option "AutoAddDevices" "Off" is the one that means "dont' use Hal to >> detect input devices". >> >>> Thank you for this hint! This could be added to the handbook :-) >>> AllowEmptyInput=False should be a default for Xorg IMO we can report it to >>> the Xorg project! :-) >> >> Really, the simplest solution is to build xorg-server with the HAL >> option disabled. I agree that this should be the default. > > So if you're using xorg-server that was built with hal included (maybe > because you're more a package than a ports kind of person and have no > control over the build), is AutoAddDevices still the right option to > manipulate? That is, will it disable the use of hal and fall back to > honoring the xorg.conf input devices even if the server was built with > hal support? xorg-server with hal support and AutoAddDevices Off in xorg.conf should be equivalent to xorg-server built without hal support. Put another way: if xorg-server is built without hal support, AutoAddDevices is irrelevant, it can't use hal for input device detection anyway.