Great job digging into this! It's really interesting that you see the same issues when dumping from the bluetooth stack directly.
The evdev event buffer is after the bluetooth stack has handed events off to the hid-magicmouse. Also, the input event buffer is set to 60 events, not 60 bytes. Based on these two observations, I agree with your thoughts that it is either a bluetooth hardware/driver bug or a bug in the bluetooth stack.
I would suggest posting your findings to the linux-bluetooth mailing list: http://vger.kernel.org/vger-lists.html#linux-bluetooth. That's where the core bluetooth developers hang out. They may have seen the issue before and know how to fix it, or they may know off the top of their head where to look in the stack.
Daniel,
Great job digging into this! It's really interesting that you see the same issues when dumping from the bluetooth stack directly.
The evdev event buffer is after the bluetooth stack has handed events off to the hid-magicmouse. Also, the input event buffer is set to 60 events, not 60 bytes. Based on these two observations, I agree with your thoughts that it is either a bluetooth hardware/driver bug or a bug in the bluetooth stack.
I would suggest posting your findings to the linux-bluetooth mailing list: http:// vger.kernel. org/vger- lists.html# linux-bluetooth. That's where the core bluetooth developers hang out. They may have seen the issue before and know how to fix it, or they may know off the top of their head where to look in the stack.