Re: turbo mouse woes

Re: turbo mouse woes

[J. Benjamin]

The maintainer of the FAQoMatic created something called "mousehack" which
worked for me but it only works with an outdated kernel, 2.1.14. Perhaps
someone can download it's source and update it for the latest kernels? It
can be found at <ftp://ftp.cs.dartmouth.edu/pub/jonh/linux-pmac/>


>> I have a kensington turbo mouse 5.0 hooked up to my linuxppc machine and
>> like so many, am trying to get reasonable 3-button behavior out of it. I've
>
>Unfortunately it begins to look as though version 5.0 of the Turbo
>Mouse does not support the ADB extended mouse protocol, which makes
>three-button operation a problem.  Neither mousemode nor xmodmap seems
>to help in distinguishing one mouse button from another.
>
>> done a search on the archives and in the interactive faq and have exhaused
>> the suggestions there. The familiar problem is that all of the buttons
>> produce the same behavior which is to emulate button 2 (I think--It pops up
>> contextual menus). When I run 
>> 
>> xmodmap -e "pointer = default"
>> 
>> All of the buttons act like button one, which is at least usable. I can get
>> the other buttons by holding down options, cmd etc.
>
>That's interesting, as I had never seen anything but button 1 behavior
>from my TurboMouse.  I'd be interested to see what xmodmap reports
>about the pointer _before_ you do this ("xmodmap -pke", if I recall).
>
>> What's odd is that when I was booting with the installer.coff file on the
>> v4 cd-rom, the 3 buttons responded as I expected them to. Since I've
>> started booting with bootx, using a 2.1x kernal, the mousing is funny.
>
>Most interesting, that.  I shall have to look at the installer.coff
>and see if there are any clues for fixing this with 2.1.x.  How did the
>four TurboMouse buttons map to three-button behavior?  That is, which
>TurboMouse button did what?
>
>> Are there magic mousemode arguments that I need or do I need to be passing
>> the kernal different arguments on startup? Any help is appreciated...
>
>I don't think so.  But if you happen to find some, please post your
>results to this list.
>
>Tom
>
>
>[[ This message was sent via the linuxppc-user mailing list. Replies are ]]
>[[ not forced back to the list, so be sure to  Cc linuxppc-user  if your ]]
>[[ reply is of general interest. To unsubscribe from linuxppc-user, send ]]
>[[ the message 'unsubscribe' to linuxppc-user-request@lists.linuxppc.org ]]
>


[[ 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. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: turbo mouse woes

[Mark Abene]

On Sun, Dec 20, 1998 at 03:45:30AM +0000, J. Benjamin wrote:
> 
> The maintainer of the FAQoMatic created something called "mousehack" which
> worked for me but it only works with an outdated kernel, 2.1.14. Perhaps
> someone can download it's source and update it for the latest kernels? It
> can be found at <ftp://ftp.cs.dartmouth.edu/pub/jonh/linux-pmac/>
> 
> 

Actually, I wrote mousehack.  Jon Howell wrote mousemode, which works with
"generic" extended mice.  Newer Turbo Mouse trackballs need a little proprietary
nonsense (read "magic") sent to ADB register 2.  That's where my program
comes in.  It uses the ADB semantics of the 2.1.24 kernel, but could easily
be adapted to the newer kernels.  Anyways, here's the source...

---cut here---
/* mousehack.c
 *
 * A program for linux-pmac by jonh Tue Feb 18 00:46:10 EST 1997
 * hacked mercilessly by warner@lothar.com: don't blame jonh for my bugs!
 *
 * Now does magic for the Kensington turbo mouse trackball (phiber@phiber.com)
 * 8/30/98
 */

#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <errno.h>
#include <fcntl.h>
#include <asm/adb_mouse.h>
#include <asm/cuda.h>

int fd;

void
send(unsigned char *y, int len)
{
    int n;

#ifdef DEBUG
    printf("send: ");
    for (n=0; n < len; n++)
	printf("0x%02x ",y[n]);
    printf("\n");
#endif

    n = write(fd, y, (size_t) len);
    if (n < len) {
	perror("writing /dev/adb");
	close(fd);
	exit (EXIT_FAILURE);
    }
}

void
listen(unsigned char *y)
{
    int n;
    
    n = read(fd, y, 80);

#ifdef DEBUG
    printf("%d: ",n);
    if (n > 0) {
	int i;
	for (i=0; i < n; i++)
	    printf("0x%02x ",y[i]);
    }
    printf("\n");
#endif

    if (n < 0) {
	perror("reading /dev/adb");
	close(fd);
	exit(EXIT_FAILURE);
    }
}

void
sethandler(int addr, int handler)
{
    unsigned char y[15];

    y[0] = ADB_PACKET;
    /* mouse (0x30) listen (0x08) reg 3 (0x03) */
    y[1] = ADB_WRITEREG(addr, 3);
    /* service request enable (0x20), device addr 3 (0x03) */
    y[2] = 0x20 + addr;
    y[3]= handler;

    send(y, 4);
    listen(y);
}

void
moveadb(int src, int dst)
{
	unsigned char y[15];
	
	y[0] = ADB_PACKET;
	y[1] = ADB_WRITEREG(src, 3);
	y[2] = 0x20 + dst;
	y[3] = 0xfe;

	send(y, 4);
	listen(y);
}

void
initreg2()
{
	unsigned char x[15];
	unsigned char y[] = { ADB_PACKET, ADB_WRITEREG(3, 2), 0xe7, 0x8c, 0, 0, 0, 0xff, 0xff, 0x94 };
	send(y, 10);
	listen(x);

	x[0] = ADB_PACKET;
	x[1] = 0x31;	/* flush device 3 */
	send(x, 2);
	listen(x);
}


void
setreg2()
{
	unsigned char y[] = { ADB_PACKET, ADB_WRITEREG(3, 2), 0xa5, 0x14, 0, 0, 0x69, 0xff, 0xff, 0x27 };
	send(y, 10);
	listen(y);
}

int
main(int argc, char **argv)
{
	fd = open("/dev/adb", O_RDWR);
	if (fd <= 0) {
		perror("opening /dev/adb");
		exit(EXIT_FAILURE);
	}
    
	sethandler(3, 4);
	moveadb(3, 15);
	initreg2();
	setreg2();

	close(fd);
	return 0;
}
---cut here---

Cheers!
-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. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]