Comment 5 for bug 246526

The MX revolution mouse I'm using has a different ID from the revoco.c file, and what you're talking about here (it's 0xc70c).

I changed the code in revoco.c to this ID, but there is still no functionality. I'm guessing my mouse is using a newer or older protocol than what's being used in revoco.

I see this in the source:
#define MX_REVOLUTION 0xc51a // version RR41.01_B0025
#define MX_REVOLUTION2 0xc525 // version RQR02.00_B0020

From my lsusb output for my mouse, I can see the version is: RR40.07_B0092

I've been trying to reverse-engineer the different protocol from the lsusb output, but have been unsuccessful so far. I've also tried capturing the protocol in Windows while using SetPoint to switch between free-spin and click-to-click mode, also to no avail.

Is any having similar problems, or can offer any assistance to update revoco for this version of the MX revolution mouse?

I've attached my lsusb output for the mouse.