From owner-freebsd-x11@FreeBSD.ORG  Fri Feb  6 23:12:39 2009
Return-Path: <owner-freebsd-x11@FreeBSD.ORG>
Delivered-To: freebsd-x11@freebsd.org
Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by hub.freebsd.org (Postfix) with ESMTP id 5EE9D106566B;
	Fri,  6 Feb 2009 23:12:39 +0000 (UTC)
	(envelope-from jkim@FreeBSD.org)
From: Jung-uk Kim <jkim@FreeBSD.org>
To: Joe Marcus Clarke <marcus@freebsd.org>
Date: Fri, 6 Feb 2009 18:12:27 -0500
User-Agent: KMail/1.6.2
References: <200902051650.n15Go2Ob074222@freefall.freebsd.org>
	<498CAB46.7020408@freebsd.org>
	<200902061738.24574.jkim@FreeBSD.org>
In-Reply-To: <200902061738.24574.jkim@FreeBSD.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200902061812.30056.jkim@FreeBSD.org>
Cc: freebsd-x11@freebsd.org, freebsd-gnome@freebsd.org,
	bug-followup@freebsd.org, Serge Shilov <serguei.shilov@gmail.com>
Subject: Re: ports/131124: x11/xorg - New xorg 7.4 hangs until mouse
	is	moved when AllowEmptyInput turned off
X-BeenThere: freebsd-x11@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: X11 on FreeBSD -- maintaining and support <freebsd-x11.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-x11>,
	<mailto:freebsd-x11-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-x11>
List-Post: <mailto:freebsd-x11@freebsd.org>
List-Help: <mailto:freebsd-x11-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-x11>,
	<mailto:freebsd-x11-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2009 23:12:40 -0000

On Friday 06 February 2009 05:37 pm, Jung-uk Kim wrote:
> On Friday 06 February 2009 04:27 pm, Joe Marcus Clarke wrote:
> > What about modifying the sysmouse driver to more gracefully
> > handle multiple open attempts (e.g. fail on subsequent attempts).
> >  What effect would that have on X?
>
> I thought about that.  In fact, I implemented something along the
> line but threw it away because 1) I was not sure of its expected
> behavior, 2) it is intertwined with syscons and I was afraid of
> breaking it, 3) it just hides Xserver problem (i.e., mixed uses of
> static/auto configurations) from an OS driver, 4) it does not
> provide fix for release users, 5) possible POLA violations, etc.

If my memory serves, there is another important reason: 6) Xserver and 
mouse driver open/close same device multiple times (at least twice), 
one for SetupAuto and one for enabling the device, I think.  
Depending on timing, the previous device may not be what HAL is 
expecting.

Jung-uk Kim