Dmitry, This Dell in question do not have an option to disable the touchpad. The BIOS options are unremarkable. Peter On 04/28/2010 01:07 PM, Dmitry Torokhov wrote: > On Fri, Apr 23, 2010 at 02:46:52PM -0400, Peter M. Petrakis wrote: >> Here are the dmesg boot logs with i8042.debug. >> >> On 04/23/2010 12:53 PM, Dmitry Torokhov wrote: >>> On Thursday 22 April 2010 05:47:48 pm Christoph Fritz wrote: >>>> Am Donnerstag, den 22.04.2010, 14:55 -0700 schrieb Dmitry Torokhov: >>>>> 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? >>>> >>>> Peter's dmesg: >>>> >>>> [ 7.428561] Unable to query Synaptics hardware. >>>> >>>> It's plain PS/2 or IMPS/2 because this bleeding edge device fails >>>> somewehre in synaptics_query_hardware(). Most likely the test on >>>> priv->identity. >>> >>> Ah, I missed that. Peter, could you boot with i8042.debug so we could see >>> where exactly Synaptics detection fails? >>> > > Indeed, capability request returns "d0 00 73" whereas we expect 0x47 in > the middle byte. > > Peter, please make sure that you do not have touchpad disabled in BIOS > (at least other Dells that I seen had similar options). > > Cristofer, do you know by any chance why touchpad reporing firmware 7.5 > would return such unexpected answer to 0x02 query? > > Thanks! > -- 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
