From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dmitry Torokhov" Subject: Re: appletouch quirk doesn't run at resume Date: Wed, 28 Mar 2007 13:35:25 -0400 Message-ID: References: <20070318004240.GO752@stusta.de> <45FD8CA3.10405@m3y3r.de> <4609866C.4060602@m3y3r.de> <460A9D28.5050703@m3y3r.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline Sender: owner-linux-input@atrey.karlin.mff.cuni.cz List-Help: List-Owner: List-Post: List-Unsubscribe: To: Jiri Kosina Cc: Thomas Meyer , Linux Kernel Mailing List , Soeren Sonnenburg , linux-input@atrey.karlin.mff.cuni.cz, Peter Osterlund List-Id: linux-input@vger.kernel.org On 3/28/07, Jiri Kosina wrote: > On Wed, 28 Mar 2007, Thomas Meyer wrote: > > > > I am not sure if this would help... According to the excerpt from X > > > log synaptics driver attempted to scan evdev devices and locate the > > > touchpad. However if this scan happen before udev had a chance to > > > process the event and create new /dev/input/eventX device node it will > > > fail. > > Okay. This strengthens above statement. And udev is too slow to create > > the devices, while the driver already scanned the directory. > > > I wonder if we should adjust the X driver to spin for a couple of > > > seconds in EventAutoDevProbe if the touchpad was already seen once... > > > Peter? > > Yes, it looks like this is the root cause. > > However I must admit that I don't like this behavior too much. We > shouldn't rely on drivers individual userland to wait for a reasonable > time before the udev settles down. This is not a nice API to provide. Will > try to think of some solution which would have reasonable > nastiness/functionality ratio. > The proper fix would be teach X to recognize hotplug events. I've heard they are working on it. -- Dmitry