> 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 .