From: Mark Abene <phiber@radicalmedia.com>
To: bh40@calva.net
Cc: linuxppc-dev@lists.linuxppc.org
Subject: turbo mouse driver fix...
Date: Tue, 25 May 1999 02:45:24 -0400 [thread overview]
Message-ID: <19990525024524.D26885@radicalmedia.com> (raw)
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.
Observe:
--- mac_keyb.c.orig Tue May 25 02:07:29 1999
+++ mac_keyb.c Tue May 25 02:25:36 1999
@@ -908,13 +908,10 @@
adb_request(&req, NULL, ADBREQ_SYNC, 1, ADB_FLUSH(id));
- adb_request(&req, NULL, ADBREQ_SYNC, 3,
- ADB_WRITEREG(id,3), 0x20 | id, 4);
-
- adb_request(&req, NULL, ADBREQ_SYNC, 1, ADB_FLUSH(id));
+ adb_request(&req, NULL, ADBREQ_SYNC, 1, ADB_FLUSH(3));
adb_request(&req, NULL, ADBREQ_SYNC, 9,
- ADB_WRITEREG(id,2),
+ ADB_WRITEREG(3,2),
0xe7,
0x8c,
0,
@@ -924,10 +921,10 @@
0xff,
0x94);
- adb_request(&req, NULL, ADBREQ_SYNC, 1, ADB_FLUSH(id));
+ adb_request(&req, NULL, ADBREQ_SYNC, 1, ADB_FLUSH(3));
adb_request(&req, NULL, ADBREQ_SYNC, 9,
- ADB_WRITEREG(id,2),
+ ADB_WRITEREG(3,2),
0xa5,
0x14,
0,
That should work fine. If it does for everyone else, it should be committed!
-Mark
[[ 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 reply other threads:[~1999-05-25 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-25 6:45 Mark Abene [this message]
1999-05-25 13:23 ` turbo mouse driver fix Jerry Quinn
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=19990525024524.D26885@radicalmedia.com \
--to=phiber@radicalmedia.com \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).