linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "J.R. Mauro" <jrm8005@gmail.com>,
	Marcel Holtmann <marcel@holtmann.org>,
	linux-input@vger.kernel.org, locoxella@gmail.com
Subject: Re: Apple Wireless Mighty Mouse HWheel quirk
Date: Tue, 09 Jun 2009 23:26:51 +0200	[thread overview]
Message-ID: <4A2ED39B.30100@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0904142307260.13028@wotan.suse.de>

On 04/14/2009 11:09 PM, Jiri Kosina wrote:
> On Tue, 14 Apr 2009, Jiri Slaby wrote:
> 
>>> I have an Apple bluetooth mouse (info below) and have noticed that the 
>>> horizontal scrolling is inverted. I've noticed some bug reports from 
>>> others getting the same behavior. I looked at drivers/hid/hid-apple.c 
>>> , and around line 444 I see that APPLE_INVERT_HWHEEL gets ORed in. I 
>>> tried to trace the origins of the code, but I lost track of it before 
>>> 8c19a515, where you moved Apple quirks to their own file. Is this 
>>> quirk definitely correct?
>>> Mouse's entry in /proc/bus/input/devices
>>> I: Bus=0005 Vendor=05ac Product=030c Version=0200
>>> I'm running Gentoo, vanilla 2.6.29 with no patches.
>> I have no idea whether the inversion is correct or not. Or where the
>> information comes from :).
>> It was added in
>> cb3fecc2f29056e89658e7eb371e7f9be66cda6d
>> by Jiri Kosina, maybe he may shed some light on it?
> 
> I created this patch based solely on a bugreport, I didn't physically own 
> the hardware at that time.
> 
> I think I have it somewhere. I will try to find it tomorrow or the day 
> after tomorrow and verify whether the quirk is really needed. Maybe the 
> original bug reporter messed up, or he had different hardware revision.

Any news here?

I think this is what you hit too, Andres?


Interesting part from the Andres' email follows:

I have an Apple Mighty Mouse. This is how it looks with 'cat
/proc/bus/input/devices'

I: Bus=0005 Vendor=05ac Product=030c Version=0200
N: Name="Mighty Mouse"

And the trackball on it has it x axis inverted.

Ive searched about this problem and found a Linux kernel mailing list
conversation where this error maybe had raised. A guy but a similar
mouse (also a mightymouse), but different ID (0x1000 instead of 0x030c),
was told to invert the x axis in order to have his 0x1000 mighty mouse
working with the wrong ID: 0x030c instead of adding a while new device.
Probably, inverting the trackball for the rest of us with the right id.

I will quote the mailing list post to you:

> As a newbie, I just saw your email in the source-file when I was looking
> into the sources of hid-apple.c to find my mighty mouse somewhere:
>
> /* Apple wireless Mighty Mouse */
> { HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, 0x030c),
> .driver_data = APPLE_MIGHTYMOUSE | APPLE_INVERT_HWHEEL },
>
> According to hid-ids.h, the ID 0x030c is a TDK mighty mouse. On my
> Alu-iMac (last year edition), it's a Apple's owned mighty mouse (vendor
> 0x05ac, ID 0x1000), which is not currently listed in hid-ids.h. My
> mighty mouse anyway runs o.k. with the "wrong" ID, but since the start
> withouth the mouse-wheel.
> It did not help when I changed the ID's accordingly. So my question is:
> Is there anything to be done in bluetooth driver area too to get this
> mighty mouse fully supported (some quirks needed)?

  parent reply	other threads:[~2009-06-09 21:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3aaafc130904141224w3bb76cc1ic39c8c4fd738a458@mail.gmail.com>
2009-04-14 19:45 ` Apple Wireless Mighty Mouse HWheel quirk Jiri Slaby
2009-04-14 21:09   ` Jiri Kosina
2009-04-14 21:15     ` J.R. Mauro
2009-06-09 21:26     ` Jiri Slaby [this message]
2009-06-09 23:07       ` Bastien Nocera
2009-06-10  8:23       ` Jiri Kosina
2009-06-10  8:55         ` Jiri Kosina
     [not found]           ` <1244639316.5003.8.camel@DellStudio>
2009-06-10 13:15             ` Jiri Kosina

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=4A2ED39B.30100@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=jrm8005@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=locoxella@gmail.com \
    --cc=marcel@holtmann.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).