From: "Jerry Quinn" <jquinn@nortelnetworks.com>
To: Mark Abene <phiber@radicalmedia.com>
Cc: bh40@calva.net, linuxppc-dev@lists.linuxppc.org
Subject: Re: turbo mouse driver fix...
Date: Tue, 25 May 1999 09:23:57 -0400 [thread overview]
Message-ID: <374AA46D.A1A4BAFC@americasm01.nt.com> (raw)
In-Reply-To: 19990525024524.D26885@radicalmedia.com
Mark Abene wrote:
>
> Hey! Please test the following patch to mac_keyb.c which fixes the TurboMouse
> support you added based on my "mousehack" program. I tested my changes on a
> 2.2.7 kernel. The problem is that once you determine we are working with a
> TurboMouse 5 (thanks for adding the reg 1 ID detection, btw!), we need to write
> to id 3, which is how you control the TurboMouse 5's modes, not to id 15.
Naive question here: Does id 3 refer to the adb device? The reason I
ask is that when I had the 2.2.0/1 kernel, 3-button detection wasn't
working properly in my setup. At the time the answer was supposed to be
running
mousemode 3 4
However, in my setup I also had a joystick connected. So in reality I
sometimes had to do mousemode 15 4 randomly. I guess it was whichever
device got recognized first.
Anyway, my point is that if this is the device id, assuming id 3 may not
be the correct thing to do in general.
If it's not device id, just ignore me :-)
--
Jerry Quinn Tel: (514) 761-8737
jquinn@nortelnetworks.com Fax: (514) 761-8505
Speech Recognition Research
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-05-25 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-25 6:45 turbo mouse driver fix Mark Abene
1999-05-25 13:23 ` Jerry Quinn [this message]
1999-05-25 14:49 ` Mark Abene
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=374AA46D.A1A4BAFC@americasm01.nt.com \
--to=jquinn@nortelnetworks.com \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=phiber@radicalmedia.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;
as well as URLs for NNTP newsgroup(s).