From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: trelane@digitasaru.net, dtor_core@ameritech.net,
linux-kernel@vger.kernel.org, petero2@telia.com
Subject: Re: [ATTN: Dmitry Torokhov] About the trackpad and 2.6.11-rc[23] but not -rc1
Date: Mon, 7 Feb 2005 14:49:33 -0500 [thread overview]
Message-ID: <d120d500050207114959466682@mail.gmail.com> (raw)
In-Reply-To: <20050207191615.GC12024@digitasaru.net>
On Mon, 7 Feb 2005 13:16:15 -0600, Joseph Pingenot
<trelane@digitasaru.net> wrote:
> From Dmitry Torokhov on Monday, 07 February, 2005:
> >On Mon, 7 Feb 2005 13:05:41 -0600, Joseph Pingenot
> ><trelane@digitasaru.net> wrote:
> >> From Dmitry Torokhov on Monday, 07 February, 2005:
> >> >On Mon, 7 Feb 2005 12:09:50 -0600, Joseph Pingenot
> >> ><trelane@digitasaru.net> wrote:
> >> >> From Dmitry Torokhov on Monday, 07 February, 2005:
> >> >> >Nonetheless it would be nice to see the data stream from the touchpad
> >> >> >to see why our ALPS support does not work quite right. Could you
> >> >> >please try booting with "log_buf_len=131072 i8042.debug=1", and
> >> >> >working the touchpad a bit. then send me the output of "dmesg -s
> >> >> >131072" (or just /var/log/messages).
> >> >> dmesg output, non-mouse output trimmed (for obvious reasons, if you think
> >> >> about it ;) is attached.
> >> >I am sorry, I was not clear enough. I'd like to see -rc2 (the broken
> >> >one), complete with bootup process, so we will see why it can't
> >> >synchronize at all. (I of course don't need keyboard data of anything
> >> >that has been typed after boot).
> >> They're both broken in about the same way, iirc. Is there something special
> >> in -rc2 that's not in -rc3?
> >No, -rc3 will do as well. Any version starting with -rc2 should do the trick.
>
> All info in the mail to which you repsonded were from -rc3, including
> and especially the attachemnt. The only info I sent from -rc1 was the
> contents of /proc/bus/input/devices in response to the *original* request.
>
Ah, I see. Well, the data in foo.gz file looks like standard PS/2
protocol, it would be interesting to see the beginning of the dmesg
(where we do all the detection). It looks like something has reset the
absolute mode back to standard relative one.
--
Dmitry
next prev parent reply other threads:[~2005-02-07 19:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 15:43 [ATTN: Dmitry Torokhov] About the trackpad and 2.6.11-rc[23] but not -rc1 Joseph Pingenot
2005-02-07 16:51 ` Dmitry Torokhov
2005-02-07 18:09 ` Joseph Pingenot
2005-02-07 18:59 ` Dmitry Torokhov
2005-02-07 19:05 ` Joseph Pingenot
2005-02-07 19:12 ` Dmitry Torokhov
2005-02-07 19:16 ` Joseph Pingenot
2005-02-07 19:49 ` Dmitry Torokhov [this message]
2005-02-07 19:59 ` Joseph Pingenot
2005-02-08 18:00 ` Joseph Pingenot
2005-02-08 21:26 ` Dmitry Torokhov
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=d120d500050207114959466682@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
--cc=trelane@digitasaru.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox