From: Jiri Slaby <jirislaby@gmail.com>
To: "Christof Kälin" <christof.kaelin@gmail.com>
Cc: linux-input@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Mighty mouse (bluetooth) with ID 0x1000 (vendor ID 0x05ac apple) any chance for mousewheel?
Date: Mon, 10 Nov 2008 11:53:19 +0100 [thread overview]
Message-ID: <4918129F.5000106@gmail.com> (raw)
In-Reply-To: <3d0c012d0811100104o6de42b6er279498eec6781698@mail.gmail.com>
On 11/10/2008 10:04 AM, Christof Kälin wrote:
> Hi
>
> 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)?
>
> Sorry for my annoying questions.
>
> Thanks in advance for any suggestions and best regards
I guess, they map Z axis to be a wheel instead a wheel be a wheel like in the
0x030c case.
Could you add
{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, 0x030c),
.driver_data = APPLE_MIGHTYMOUSE }
there and
HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, 0x030c)
to hid_blacklist in drivers/hid/hid-core.c and try? If the wheel is inverted
with your device, then you need also APPLE_INVERT_HWHEEL aswell.
<me goes to implement new_id like in the PCI case to not bother users with
recompiling the kernel for testing such things>
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Slaby <jirislaby@gmail.com>
To: "Christof Kälin" <christof.kaelin@gmail.com>
Cc: linux-input@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Mighty mouse (bluetooth) with ID 0x1000 (vendor ID 0x05ac apple) any chance for mousewheel?
Date: Mon, 10 Nov 2008 11:53:19 +0100 [thread overview]
Message-ID: <4918129F.5000106@gmail.com> (raw)
In-Reply-To: <3d0c012d0811100104o6de42b6er279498eec6781698@mail.gmail.com>
On 11/10/2008 10:04 AM, Christof Kälin wrote:
> Hi
>
> 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)?
>
> Sorry for my annoying questions.
>
> Thanks in advance for any suggestions and best regards
I guess, they map Z axis to be a wheel instead a wheel be a wheel like in the
0x030c case.
Could you add
{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, 0x030c),
.driver_data = APPLE_MIGHTYMOUSE }
there and
HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, 0x030c)
to hid_blacklist in drivers/hid/hid-core.c and try? If the wheel is inverted
with your device, then you need also APPLE_INVERT_HWHEEL aswell.
<me goes to implement new_id like in the PCI case to not bother users with
recompiling the kernel for testing such things>
next parent reply other threads:[~2008-11-10 10:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3d0c012d0811100104o6de42b6er279498eec6781698@mail.gmail.com>
2008-11-10 10:53 ` Jiri Slaby [this message]
2008-11-10 10:53 ` Mighty mouse (bluetooth) with ID 0x1000 (vendor ID 0x05ac apple) any chance for mousewheel? Jiri Slaby
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=4918129F.5000106@gmail.com \
--to=jirislaby@gmail.com \
--cc=christof.kaelin@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.