All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org, linus@transmeta.com
Subject: Re: [PATCH] Logitech PS/2++ updates
Date: Sat, 14 Jun 2003 17:29:33 -0700	[thread overview]
Message-ID: <20030615002933.GB17706@BL4ST> (raw)
In-Reply-To: <20030615005947.E27599@ucw.cz>

Vojtech Pavlik <vojtech@suse.cz> wrote:
> On Tue, Mar 25, 2003 at 06:55:38PM -0800, Eric Wong wrote:
> >  /*
> >   * The PS2++ protocol is a little bit complex
> >   */
> > +	if (psmouse->type == PSMOUSE_PS2PP) { 
> > +
> > +		if ((packet[0] & 0x48) == 0x48 && (packet[1] & 0x02) == 0x02 ) {
> >  
> 
> Hmm, is this change needed? This
> 
> if ((packet[0] & 0x40) == 0x40 && abs((int)packet[1] - (((int)packet[0] & 0x10) << 4)) > 191 ) {
> 
> condition is from Logitech docs and should work with any PS2PP device.
> It doesn't with yours?

The updated PS2PP uses 6 bits to determine packet-type instead of 4 as
used previously, so compatibility with the touchpad protocol was broken
if I recall correctly.

NEW (6 t bits):
       bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0
packet0   E    1   t5   t4    1    M    R    L   
packet1  t3   t2   t1   t0   d2   d1    1    0  
packet2  d8   d7   d6   d5   d4   d3   d2   d1 

OLD (4 t bits)
       bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0
packet0   E    1   t3   t2    1    M    R    L   
packet1   ?    ?   t1   t0   d2   d1    1    0  
packet2  d8   d7   d6   d5   d4   d3   d2   d1 

E is set if it's an external device

-- 
Eric Wong

  reply	other threads:[~2003-06-15  0:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26  2:55 [PATCH] Logitech PS/2++ updates Eric Wong
2003-06-14 21:18 ` Vojtech Pavlik
2003-06-14 23:39   ` Eric Wong
2003-06-15  8:39     ` Vojtech Pavlik
2003-06-17 23:16       ` Eric Wong
2003-06-20  7:34         ` Vojtech Pavlik
2003-06-14 22:59 ` Vojtech Pavlik
2003-06-15  0:29   ` Eric Wong [this message]
2003-06-15  7:21     ` Vojtech Pavlik

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=20030615002933.GB17706@BL4ST \
    --to=normalperson@yhbt.net \
    --cc=linus@transmeta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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.