linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@linuxcare.com.au>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Patches for 2.4.0-test7
Date: Mon, 28 Aug 2000 09:54:08 +1100 (EST)	[thread overview]
Message-ID: <14761.39952.597917.43823@argo.linuxcare.com.au> (raw)
In-Reply-To: <Pine.LNX.4.10.10008271823320.3745-100000@opal.biophys.uni-duesseldorf.de>


Michael Schmitz writes:

> That would have been me - I still claim that keeping adbmouse working for
> backwards compatibility would be a good thing, but my word doesn't carry
> much weight.
>
> The adbmouse driver only relies on the keyboard driver for mouse button
> emulation. At least in 2.2.17, it won't interfere with the new input code,
> I haven't tried 2.4.0 yet.

The way it is at the moment in the linuxppc_2_3 bk tree and in my
rsync tree, you have 3 choices:

1. use mac_keyb.c/adbmouse.c and don't have the input layer at all
2. use the input layer for USB devices and mac_keyb.c/adbmouse.c for
   ADB keyboard and mouse
3. use the input layer for both USB and ADB devices.

The adbmouse driver references some external variables which are
declared in mac_keyb.c.  If there is really a need to have adbmouse.c
in the system without mac_keyb.c, we can probably work out a way to
allow that, but I don't see the need.

Paul.

--
Paul Mackerras, Senior Open Source Researcher, Linuxcare, Inc.
+61 2 6262 8990 tel, +61 2 6262 8991 fax
paulus@linuxcare.com.au, http://www.linuxcare.com.au/
Linuxcare.  Support for the revolution.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-08-27 22:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-26 13:12 Patches for 2.4.0-test7 Martin Costabel
2000-08-26 16:41 ` Benjamin Herrenschmidt
2000-08-26 21:33   ` Martin Costabel
2000-08-26 22:36     ` Benjamin Herrenschmidt
2000-08-27 16:28     ` Michael Schmitz
2000-08-27 22:54       ` Paul Mackerras [this message]
2000-08-28  7:38         ` Martin Costabel
2000-08-28  9:34           ` Benjamin Herrenschmidt
2000-08-28 10:43             ` Michael Schmitz
     [not found]             ` <Pine.LNX.4.10.10008281239570.28749-100000@opal.biophys.uni -duesseldorf.de>
2000-08-28 11:51               ` Franz Sirl
2000-08-27  9:59 ` Paul Mackerras
2000-08-27 12:02   ` Benjamin Herrenschmidt

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=14761.39952.597917.43823@argo.linuxcare.com.au \
    --to=paulus@linuxcare.com.au \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    /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).