Date: Fri, 6 Feb 2009 18:12:27 -0500 From: Jung-uk Kim <jkim@FreeBSD.org> To: Joe Marcus Clarke <marcus@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 Message-ID: <200902061812.30056.jkim@FreeBSD.org> In-Reply-To: <200902061738.24574.jkim@FreeBSD.org> References: <200902051650.n15Go2Ob074222@freefall.freebsd.org> <498CAB46.7020408@freebsd.org> <200902061738.24574.jkim@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200902061812.30056.jkim>