The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org, "Bryan O'Donoghue" <typedef@eircom.net>
Subject: Re: [PATCH] Change behaviour of psmouse-base.c under error conditions.
Date: Mon, 5 Sep 2005 19:20:40 -0500	[thread overview]
Message-ID: <200509051920.40482.dtor_core@ameritech.net> (raw)
In-Reply-To: <20050905215512.GB12252@midnight.suse.cz>

On Monday 05 September 2005 16:55, Vojtech Pavlik wrote:
> On Mon, Sep 05, 2005 at 04:12:13PM -0500, Dmitry Torokhov wrote:
> > On Monday 05 September 2005 15:58, Bryan O'Donoghue wrote:
> > > 
> > > However, the KVM in question invariably ends up sending a packet like this
> > > 
> > > packet= 0x0 0xff 0x2 0x8
> > > 
> > > Which is completely invalid for PS/2 and IMPS/2, the specification of
> > > PS/2 defines bit 4 in byte 0 as always being 1.
> 
> Just for the record: Bit 4 was supposed to indicate an external (=1)
> mouse, while internal mice would have a '0' there. This then would allow
> to differentiate between two devices on the same bus.
> 
> I've even seen that in action on one very old laptop.
> 
> Of course, extended protocols break that completely.

IBM Trackpoint controllers can force that bit to 1 for internal device
and to 0 for external. If we ever implement pass-through port for
trackpoints we might use it do demultiplex data streams.

-- 
Dmitry

      parent reply	other threads:[~2005-09-06  0:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-05 20:58 [PATCH] Change behaviour of psmouse-base.c under error conditions Bryan O'Donoghue
2005-09-05 21:12 ` Dmitry Torokhov
2005-09-05 21:55   ` Vojtech Pavlik
2005-09-05 22:56     ` Bryan O'Donoghue
2005-09-06  0:20     ` Dmitry Torokhov [this message]

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=200509051920.40482.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=typedef@eircom.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox