From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <26d0b9b2ecc3671c07dcdc4de9bcd8f6@felloff.net> Date: Mon, 25 Aug 2014 11:59:53 +0200 From: cinap_lenrek@felloff.net To: 9fans@9fans.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] simple mouse problem Topicbox-Message-UUID: 12302d4a-ead9-11e9-9d60-3106f5b1d025 here is how i would start debugging this: plug the mouse in, it gets detected by usbd and nusbrc spawns a nusb/kb process to handle the device. you can open a rio window and run "cat /dev/usbevent" to see what the usb address of the device is. ps -a and look at the process arguments to get the usb address (in your case, the address was 8). now, you need to kill the automatically spawned kb process so you can attach your own nusb/kb with debug flag. use kill kb and select the lines with the pid from the previous ps and send them to the prompt. now, you can run nusb/kb -d addr (addr is numeric usb address) on the device and get debug prints. it should hexdump the hid descriptor of the mouse and give values of the items in the report descriptor. it might also be a good idea to pull the latest version and rebuild nusb/kb afterwards, so we'r debugging the same code. you might join the #cat-v irc channel on freenode, then we can do a debug session step by step. lets do this offlist as the code is 9front specific in this case. -- cinap