public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arndt Schoenewald <abs@src00024x007.mc.schoenewald.de>
To: Allan Sandfeld Jensen <snowwolf@one2one-networks.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux console project <linuxconsole-dev@lists.sourceforge.net>
Subject: Re: ps2/ new data for mouse protocol (fwd msg attached)
Date: Wed, 25 Jul 2001 20:02:04 +0200	[thread overview]
Message-ID: <20010725200204.A21273@digda.intern.quelltext.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10107250905030.8057-100000@transvirtual.com>
In-Reply-To: <Pine.LNX.4.10.10107250905030.8057-100000@transvirtual.com>

Hi Allen,

I received your following message since James Simmons CC'd it to the
linuxconsole-dev mailing list:

> > However, some mouse secrets from various sources I hacked in here:
> > http://home.t-online.de/home/gunther.mayer/gm_psauxprint-0.01.c -
> 
> Very nice. I am currently looking for some info to solve a problem with 
> thinkpads and logitech cordless mice over ps/2. Basicly the wheel doesnt 
> work. Looking closer they dont respond to the imps/2 or mousemanps/2 
> protocol. Since cordless mice are more common than thinkpads, I think the 
> problem would be solved if it was with the mouse. So I am guessing the IBM 
> defaults to just repeating standard ps/2 protocol, and you have to first 
> trick that before you trick the mouse. Since it works in windows there IS a 
> way...
> 
> Where do I find the public available protocols, and the secrets? :)
> 
> And for the list, who should I notify that I am working on autodetecting IBM 
> thinkpad  ps/2 repeaters in mouse driver?

recently I spent a lot of time figuring out how to make a chordless wheel
mouse, which had two extra buttons on the left and on the right, work
on Linux with gpm and XFree86 4.0.3. The mouse was supposed to support
both the IntelliMouse and IntelliMouse Explorer protocol extensions,
but no matter which protocol selection I tried with gpm, the mouse would
stick in its 3 byte standard PS/2 mode. The same happened without gpm,
when I tried to use the mouse with XFree86's "ExplorerPS/2" setting.

After many hours of research I finally discovered why. The initialization
sequence used by both programs is not exactly what the mouse needs:

  - XFree86's "ExplorerPS/2" setting sends an initialization sequence of
    { 243, 200, 243, 200, 243, 80 }. For this mouse, however, the sequence
    must be { 243, 200, 243, 100, 243, 80, 243, 200, 243, 200, 243, 80 }.

  - The initialization sequence used by gpm 1.19.3 includes the byte 246
    which is meant to reset some mouse settings back to normal. However,
    for this mouse, it also resets it to 3 byte standard PS/2 mode.

I already submitted a patch to the XFree86 team, but don't know whom to
contact for the gpm fix.

I hope this helps you with your mouse!
Arndt

PS1: A good reading for mouse related stuff is Adam Chapweske's page at
http://panda.cs.ndsu.nodak.edu/~achapwes/PICmicro/mouse/mouse.html.

PS2: FWIW, my mouse is a NEO AirView 405 RF, which is a OEM product sold
in Germany under multiple brand (at least Neolec, Typhoon, Dexxa) and
product names (see e.g. http://neolec.de/news/indexAirView405RF.html).

-- 
 /////    Quelltext AG -- Professional Software Services
//   //   Arndt Schoenewald <abs@src00024x007.mc.schoenewald.de>. CEO
//   //   Ostenhellweg 31, 44135 Dortmund, Germany
//  \\/   Tel +49 231 9503750, Fax +49 231 9503751
 ////\\   Web http://quelltext.com

  reply	other threads:[~2001-07-25 18:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-24 17:32 ps2/ new data for mouse protocol (fwd msg attached) Nico Schottelius
2001-07-24 23:23 ` Erik Mouw
2001-07-25 11:09   ` Gunther Mayer
2001-07-25 14:43     ` Allan Sandfeld Jensen
2001-07-25 16:08       ` James Simmons
2001-07-25 18:02         ` Arndt Schoenewald [this message]
2001-07-26 18:01   ` Nico Schottelius

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=20010725200204.A21273@digda.intern.quelltext.com \
    --to=abs@src00024x007.mc.schoenewald.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxconsole-dev@lists.sourceforge.net \
    --cc=snowwolf@one2one-networks.com \
    /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