On Thu, Apr 22, 2010 at 05:48:21PM -0400, Peter M. Petrakis wrote: > Hi, > > This one is a winner. with regards to your follow up. I wouldn't > want to reset something unless we have cause to. This code > seems to be doing the right thing e.g. I see "unable to query > synaptics hardware" followed by it's (re)discovery on return > from S3. > > When it's fully supported by the Synaptics driver, the initial > reconnect will succeed and we'll never get to this additional > failsafe code which is essentially a catch all for the bleeding > edge. > I am confused here... what protocol does the kernel select upon fresh boot? It is SynPS/2 or PS/2? I fit is SYnPS/2 then the touchpad is being driven by SYnaptics protocol even though we do not fully support multitouch version of SYnaptics touchpads. And i fi ti is the case then the workaround shoudl go into synaptics-sepcific reconnect function, not generic psmouse one. Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
