linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org,
	Konstantinos Margaritis <kmargar@cc.uoa.gr>
Subject: Re: MouseSystems MacoPoint Pro, 3 btn mouse
Date: Thu, 7 Jan 1999 18:37:27 +0100	[thread overview]
Message-ID: <19990107183727.001350@mail.mipsys.com> (raw)
In-Reply-To: <Pine.CVX.3.93.990107184738.21285A-100000@atlas.cc.uoa.gr>


On Thu, Jan 7, 1999, Konstantinos Margaritis <kmargar@cc.uoa.gr> wrote:

>Actually, after I tested the MacX patch by Kelly Campbell -although I had
>to tweak it a bit, since I use 2.1.131 kernel- I found out it works
>perfectly with the Macpoint Pro mouse, so instead of sending you my mouse,
>I would suggest that this patch be inserted to the official kernel tree.
>That would be best, IMHO.

This patch is already included in my tree, but I think I have a problem
with one of the buttons, I'll have to re-check my code carefully.

I suggest you try a 2.2-pre4 with my test patch (download just the diffs
next to the test kernel) and enable the MacX option in the config. Tell
me how it works, and if it doesn't, you may eventually be able to tell me
what is broken. I may have missed something simple, I juste putted it in
quickly, it probably needs a little bit of work.

Actually, I'm interested in the theory behind this patch. Is the
"official" behaviour of MacX mice documented somewhere ? I'm thinking
about things like "can a MacX mouse be handler 2 or 4 or can it be only
handler 1 ?". With answers to this, I may be able to auto-disable the
patch when I know for sure it's a normal mouse, and this allow the same
kernel to work with both kind of mice. I already have some "hints" about
the way to do that but I want to be sure and to be able to test ;-)

I think I'll end up just buying one.

-- 
           E-Mail: <mailto:bh40@calva.net>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>





[[ 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:[~1999-01-07 17:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-06  1:01 MouseSystems MacoPoint Pro, 3 btn mouse Konstantinos Margaritis
1999-01-06  2:06 ` Daniel Jacobowitz
1999-01-06 10:41 ` Kelly Campbell
1999-01-06 14:03   ` Benjamin Herrenschmidt
1999-01-07 17:00     ` Konstantinos Margaritis
1999-01-07 17:37       ` Benjamin Herrenschmidt [this message]

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=19990107183727.001350@mail.mipsys.com \
    --to=bh40@calva.net \
    --cc=kmargar@cc.uoa.gr \
    --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).