All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Brose <bob@jriver.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: usb mouse in 2.2.10
Date: Mon, 26 Jul 1999 21:58:05 -0500	[thread overview]
Message-ID: <379D203D.FAAA971@jriver.com> (raw)


Thanks for those that helped with the usb keyboard and 2.2.10. Now that the
keyboard is working
on the iMac, I've got one observation and a question.

1) The keyboard response is somewhat odd. If I type "cd /anything" at the
prompt, it fairly
regularly does cdcd /anything on the echo. It's hard to pin down because it
isn't
completely consistent. I'm guessing an odd debounce problem.. It seems to only
happen on
a few characters. The same machine works fine with 2.2.5.

2) The mouse is inoperative in X. The links are...
[bob@imac /dev]$ ls -l *mouse*
crw-r--r--   1 root     root      10,  10 Apr 30 10:54 adbmouse
lrwxrwxrwx   1 root     root            8 Jun 16 12:08 mouse -> usbmouse
crw-rw-r--   1 root     root      10,   6 May  5  1998 sunmouse
lrwxrwxrwx   1 root     root           11 Jun 16 11:45 usbmouse -> hidbp-mse-0

The X pointer section..
Section "Pointer"
    Protocol    "BusMouse"
    Device      "/dev/mouse"

If I cat /dev/mouse and move it I get moving lines of junk as I would expect.
The bus mouse
protocol looks suspicious but it works in 2.2.5 and I haven't found anything to
replace it with
yet.

Bob
-- 
Robert E. Brose II    N0QBJ
http://www.jriver.com/~bob/
bob@kunk.jriver.com

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

             reply	other threads:[~1999-07-27  2:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-27  2:58 Robert Brose [this message]
1999-07-27  4:27 ` usb mouse in 2.2.10 Brad Midgley
1999-07-28  1:46 ` Paul Mackerras
1999-07-28 21:24   ` Robert E. Brose II

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=379D203D.FAAA971@jriver.com \
    --to=bob@jriver.com \
    --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 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.