From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Kosina Subject: Re: [PATCH 0/2] Provide a driver for the Apple Magic Mouse Date: Wed, 10 Feb 2010 14:57:37 +0100 (CET) Message-ID: References: <1265710460.2383.5685.camel@localhost.localdomain> <201002090736.55576.edt@aei.ca> <87y6j2eeqv.fsf_-_@troilus.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: In-Reply-To: <87y6j2eeqv.fsf_-_-IZmAEv5cUt1AfugRpC6u6w@public.gmane.org> Sender: linux-bluetooth-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Michael Poole Cc: linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Marcel Holtmann , linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-input@vger.kernel.org On Tue, 9 Feb 2010, Michael Poole wrote: > I think this patch is ready for real review. The Magic Mouse requires > that a driver send an unlock Report(Feature) command, similar to the > Wacom wireless tablet and Sixaxis controller quirks. This turns on an > Input Report that isn't published in the input Report descriptor that > contains touch data (and usually overrides the normal motion and click > Report). > > Because the mouse has only one switch and no scroll wheel, the driver > (under control of parameters) emulates a middle button and scroll wheel. > User space could also ignore and/or re-synthesize those events based on > the reported events. > > The first patch exports hid_register_report() so the driver can turn on > the multitouch report. The second patch adds the device ID and the > driver. Some user-space tools to talk to the mouse directly (that is, > when it is not associated with the host's HIDP stack) are at > http://github.com/entrope/linux-magicmouse . I have applied the driver into apple_magic_mouse branch and merged this branch into for-next, so it should appear in the upcoming linux-next. Thanks, -- Jiri Kosina SUSE Labs, Novell Inc.