From: "Peter M. Petrakis" <peter.petrakis@canonical.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Christoph Fritz <chf.fritz@googlemail.com>,
linux-input@vger.kernel.org, rubini <rubini@cvml.unipv.it>,
Christopher Heiny <cheiny@synaptics.com>
Subject: Re: [PATCH] Reset ps/2 port should psmouse_probe fail before retrying
Date: Wed, 28 Apr 2010 16:17:24 -0400 [thread overview]
Message-ID: <4BD897D4.4060405@canonical.com> (raw)
In-Reply-To: <20100428170721.GA6608@core.coreip.homeip.net>
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!
>
next prev parent reply other threads:[~2010-04-28 20:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 22:52 [PATCH] Reset ps/2 port should psmouse_probe fail before retrying Peter M. Petrakis
2010-04-17 11:01 ` Christoph Fritz
2010-04-17 15:31 ` Peter M. Petrakis
2010-04-17 16:53 ` Christoph Fritz
2010-04-19 15:33 ` Peter M. Petrakis
2010-04-20 0:37 ` Christoph Fritz
2010-04-20 21:08 ` Peter M. Petrakis
2010-04-21 6:33 ` Dmitry Torokhov
2010-04-21 16:05 ` Peter M. Petrakis
2010-04-21 17:10 ` Dmitry Torokhov
2010-04-21 19:38 ` Peter M. Petrakis
2010-04-21 19:52 ` Dmitry Torokhov
2010-04-21 21:10 ` Peter M. Petrakis
2010-04-22 16:28 ` Christoph Fritz
2010-04-22 21:48 ` Peter M. Petrakis
2010-04-22 21:55 ` Dmitry Torokhov
2010-04-23 0:47 ` Christoph Fritz
2010-04-23 16:53 ` Dmitry Torokhov
2010-04-23 18:46 ` Peter M. Petrakis
2010-04-28 17:07 ` Dmitry Torokhov
2010-04-28 20:17 ` Peter M. Petrakis [this message]
2010-04-29 16:57 ` Christoph Fritz
2010-04-29 17:46 ` Dmitry Torokhov
2010-04-30 22:37 ` Peter M. Petrakis
2010-05-02 3:07 ` Christoph Fritz
2010-05-02 7:41 ` Christoph Fritz
2010-05-07 17:57 ` Peter M. Petrakis
2010-05-08 16:01 ` Christoph Fritz
2010-04-24 1:22 ` Christoph Fritz
2010-04-24 10:00 ` Christoph Fritz
2010-04-28 7:26 ` Dmitry Torokhov
2010-05-08 16:22 ` Christoph Fritz
2010-05-11 8:22 ` Dmitry Torokhov
2010-05-11 22:24 ` Christoph Fritz
-- strict thread matches above, loose matches on Subject: below --
2010-04-14 20:46 Peter M. Petrakis
2010-04-14 21:04 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BD897D4.4060405@canonical.com \
--to=peter.petrakis@canonical.com \
--cc=cheiny@synaptics.com \
--cc=chf.fritz@googlemail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=rubini@cvml.unipv.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.