All of lore.kernel.org
 help / color / mirror / Atom feed
From: tph@rmi.net (Tom Harrington)
To: jacobs@azstarnet.com (john s jacobs anderson)
Cc: linuxppc-user@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: TurboMouse fix
Date: Tue, 22 Dec 1998 09:51:23 -0700 (MST)	[thread overview]
Message-ID: <m0zsV1o-001C7HC@shell.rmi.net> (raw)
In-Reply-To: <Pine.LNX.3.96.981221225654.1012A-100000@lazarus> from "john s jacobs anderson" at Dec 21, 98 11:03:14 pm


> system: 7500 chasis with 166 MHz 604 card, 2.1.127 kernel. Kensington
> TurboMouse 4.0 (the 2 button kind), window maker 0.20.3
> 
> (do you need to know anything else? sorry, I'm still a wet behind the
> ears...)
> 
> exported mail to ~, trimmed file in pico, then `cc mousehack.c`.
> 
> gives :
> /tmp/cca082751.o: In function `sethandler':
> /tmp/cca082751.o(.text+0x148): undefined reference to `ADB-WRITEREG'
> (same error repeated at (.text+0x1dc) in function `moveadb'
>                         (.text+0x26c) in function `initreg2'
>                         (.text+0x364) in function `setreg2'
> collect2: ld returned 1 exit status
> 
> ack! what now? I'm drooling at the thought of a functional 2 button mouse,
> and if it only ends up working with v5.0 TurboMice, Santa might have to
> make a late delivery...

Hmm, maybe something in your header files?  ADB_WRITEREG is defined (on
my system) in /usr/include/asm/adb_mouse.h.  Look for this file and see 
what's there.

I'm surprised it complains about "ADB-WRITEREG" when the code uses
"ADB_WRITEREG".  You didn't happen to "fix" this while trimming the
file in pico, did you?

I really don't know if mousehack is useful (or even necessary) with a v4.0
TurboMouse.  I assume you've tried the "mousemode" command?

Tom


[[ 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 ]]

  reply	other threads:[~1998-12-22 16:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-22  4:16 TurboMouse fix Tom Harrington
1998-12-22  6:03 ` john s jacobs anderson
1998-12-22 16:51   ` Tom Harrington [this message]
1998-12-22 21:59     ` john s jacobs anderson
1998-12-23  4:58       ` Tom Harrington
1998-12-23  5:24         ` john s jacobs anderson
1998-12-22 18:29   ` Mark Abene
1998-12-22 21:49     ` john s jacobs anderson
1998-12-22  6:11 ` FD_SET/FD_ZERO, vi clone compiling john s jacobs anderson

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=m0zsV1o-001C7HC@shell.rmi.net \
    --to=tph@rmi.net \
    --cc=jacobs@azstarnet.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-user@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.