9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] simple mouse problem
Date: Mon, 25 Aug 2014 11:59:53 +0200	[thread overview]
Message-ID: <26d0b9b2ecc3671c07dcdc4de9bcd8f6@felloff.net> (raw)
In-Reply-To: <CAF1zXhkMtN899Q6u+hogC25kD5ZoFGVPN_eV0pZX4RXh1=FR1w@mail.gmail.com>

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



      parent reply	other threads:[~2014-08-25  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-24 12:41 Fausto Saporito
2014-08-24 14:34 ` erik quanstrom
2014-08-25  9:59 ` cinap_lenrek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=26d0b9b2ecc3671c07dcdc4de9bcd8f6@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).