From: "Robert Thompson" <rothomp3@vt.edu>
To: "Benjamin Herrenschmidt" <bh40@calva.net>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: trackpad
Date: Wed, 12 Jul 2000 21:35:31 -0400 [thread overview]
Message-ID: <012301bfec6a$b5474aa0$1a6a1504@strayer.edu> (raw)
In-Reply-To: 20000712233159.26202@192.168.1.10
> What I wrote can be a bit confusing. I meant:
>
> - The new layer will create new devices that mix all mice (including
> trackpad) and route them to the new /dev/input/mice device. Of course,
> you need to create this device (with mknod) and eventually link /dev/
> mouse, /dev/adbmouse and /dev/usbmouse (yes, all 3 of them) to /dev/
> input/mice. There are some explanation on how to do that on my page.
> Those will output imps2 protocol.
>
Right, did that, and usbmice work fine. No, I made sure /dev/adbmouse still
had it's old major and minor, it is not a symlink to /dev/input/mice.
> - The latest kernel (pre10-ben1) will keep the old /dev/adbmouse device
> alive. That means that if you don't set /dev/adbmouse to point to the new
> /dev/input/mice but instead keep it to it's old major/minor, you'll still
> get a busmouse-like device on /dev/adbmouse
>
In theory, but it isn't working that way. Or, at least, *something* isn't
working... I'm not lying here, the trackpad really isn't working :)
> - I also added this new "adb_xpmac_compat" kernel command line option
> (at least until Xpmac is fixed). With this, the driver will, by default,
> enable sending of ADB mouse moves as fake keycodes to the console, like
> MkLinux, in a way compatible with Xpmac. The new driver won't do it any
> more unless you use that option or your do
>
> echo "1" >/proc/sys/dev/mac_hid/adb_mouse_sends_keycodes
>
I tried both using the kernel command line and/or setting this /proc flag,
but nothing works, in any combination. Sorry to seem... I don't know,
annoying (if I do) but this is a rather important bug to fix, I'd say...
Later,
Robbie Thompson
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-13 1:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-10 19:38 trackpad Robert Thompson
2000-07-11 7:34 ` trackpad Hollis Blanchard
2000-07-11 14:51 ` trackpad Robert Thompson
2000-07-11 15:29 ` trackpad Franz Sirl
2000-07-11 16:05 ` trackpad Robert Thompson
2000-07-11 20:54 ` trackpad Franz Sirl
2000-07-11 21:09 ` trackpad Robert Thompson
2000-07-12 23:05 ` trackpad Robert Thompson
2000-07-12 23:19 ` trackpad Benjamin Herrenschmidt
2000-07-12 23:31 ` trackpad Benjamin Herrenschmidt
2000-07-13 1:35 ` Robert Thompson [this message]
2000-07-12 23:33 ` trackpad Robert Thompson
2000-07-13 5:30 ` trackpad Hollis Blanchard
2000-07-13 2:43 ` trackpad Robert Thompson
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='012301bfec6a$b5474aa0$1a6a1504@strayer.edu' \
--to=rothomp3@vt.edu \
--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).