linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Martin Costabel <costabel@wanadoo.fr>,
	bh40@calva.net, linuxppc-dev@lists.linuxppc.org
Subject: Re: pre8(vger) kills button 3 on 1-button mouse
Date: Thu, 21 Jan 1999 12:58:11 +0100	[thread overview]
Message-ID: <19990121125811.027884@smtp.calvacom.fr> (raw)


On Thu, Jan 21, 1999, Martin Costabel <costabel@wanadoo.fr> wrote:

>The latest changes for 2-to-4-button mice on vger in
>drivers/macintosh/mac_keyb.c (rev 1.24) break the emulation of button 3
>on my 1-button Apple adb mouse.
>
>This happens both in Xpmac, where option_right+click is hard-coded to
>button 3, and in XF68_FBDev, where I use a patch by Franz Sirl for the
>adb_buttons kernel command to get the same effect.
>
>The reason seems to be that in rev 1.24 option_right gets mapped to
>option_left even in raw mode (same for ctrl, BTW). I don't understand
>this from the code, which is too complicated for me, anyway, but from
>looking at the effect, as witnessed by xev in Xpmac, for example.
>
>For the moment, I went back to rev 1.23 which doesn't have this problem.

I removed most of my patches to mac_keyb.c before submitting them, I was
pretty sure I didn't break anything, but I was probably wrong. I'll have
a look at it as soon as I manage to get this vger tree (today probably)
and submit a new patch.

Here, I have rewritten most of the buttons handling in console and
buttons emulation, but my new version is not ready and was not included
in the patches I sent to Cort. I just checked my patches, and they should
not change anything to buttons emulation. I'll test all this later today.
Thanks for pointing this out.

Ah yes, could you send me a dmesg log ? I would like to soo how your
mouse was recognized at startup.


-- 
           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-21 11:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-21 11:58 Benjamin Herrenschmidt [this message]
     [not found] <36A733F6.79E148C7@univ-rennes1.fr>
1999-01-22 10:44 ` pre8(vger) kills button 3 on 1-button mouse Benjamin Herrenschmidt
1999-01-22 18:30   ` Martin Costabel
  -- strict thread matches above, loose matches on Subject: below --
1999-01-20 22:20 3-button mouse Benjamin Herrenschmidt
1999-01-21  9:34 ` pre8(vger) kills button 3 on 1-button mouse Martin Costabel

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=19990121125811.027884@smtp.calvacom.fr \
    --to=bh40@calva.net \
    --cc=costabel@wanadoo.fr \
    --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).