#6727: Asus A7N8X-X: USB mouse CPU drain... ------------------------+------------------------- Reporter: Luposian | Owner: nobody Type: bug | Status: new Priority: normal | Milestone: R1 Component: - General | Version: R1/alpha2 Resolution: | Keywords: Blocked By: | Has a Patch: 0 Platform: x86 | Blocking: ------------------------+------------------------- Comment (by mmlr): Replying to [comment:2 Luposian]: > Replying to [comment:1 luroh]: > > Just a thought, are you using the same mouse as a year ago? > > Yes. Same exact Logitech USB Trackman Marble. Dunno how even a different mouse would affect things, tho. Isn't a USB mouse a USB mouse, regardless if it's an actual mouse or trackball (which is, essentially, nothing more than an upside-down mouse)? It can be quite a big difference. Not every mouse has the same resolution for example, many vendors also simply do things a bit differently. How often a report to process is sent can also be quite different from model to model and vendor to vendor. So a USB mouse is far from a USB mouse. They use the same interface so that they can be supported by the same unified driver, but how they use the freedom the HID protocol allows for is entirely up to the implementor (if you generate 10 reports with 1px move at a time or if you generate a single report with a 10px move may generate the same effect on-screen, but the processing overhead is obviously different). Overall the HID driver has been reworked a few times, I don't really remember the timeframe though. It's easily possible that the new framework is more resource hungry with that specific device you have. On the other hand the framework is far more flexible and able to support many more devices now, so... To identify the issue at hand you could attach the hid reports that are dumped to /tmp so the polling frequency can be checked for example. -- Ticket URL: <http://dev.haiku-os.org/ticket/6727#comment:4> Haiku <http://dev.haiku-os.org> Haiku - the operating system.