From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Middle button on usb mice
Date: Fri, 30 Sep 2016 08:41:16 +0200 [thread overview]
Message-ID: <00a9d62e89edb3b24e4c3decfb184298@felloff.net> (raw)
In-Reply-To: <20160930034741.GA2201@speakerbox>
> Thanks for giving it a shot. It compiles cleanly but did not fix the
> issue and when running nusb/kb -ddd N I had the same output as before.
are you really sure? you should see:
hidparse: t=8 f=2 usage=90001 v=0
hidparse: t=8 f=2 usage=90002 v=0
hidparse: t=8 f=2 usage=90003 v=0
hidparse: t=8 f=2 usage=0 v=0
hidparse: t=8 f=2 usage=0 v=0
hidparse: t=8 f=2 usage=0 v=0
hidparse: t=8 f=2 usage=0 v=0
hidparse: t=8 f=2 usage=0 v=0
...
(notice, usage=90003 should appear only once per report and usage=0
should appear 5 times after the usage=90003 line)
have you run this manually? because to make this effective for hotplug you'll
have to update both /bin/nusb/kb and build a new kernel as the *effective* command
is included in (and run from) the kernel image (so you have keyboard's and mouse
work before a root filesystem can be mounted).
to build new kernel, run mk install in /sys/src/9/pc and then copy
the 9pcf file to 9fat. (9fs 9fat; cp 9pcf /n/9fat)
> If there's any more information I can share that'll help, let me know.
yes, print the first byte from the packet please. like in readerproc()
fprint(2, "p0 = %x\n", p.p[0]);
> --
> lemon
--
cinap
next prev parent reply other threads:[~2016-09-30 6:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 3:26 lemon
2016-09-24 13:03 ` [9front] " cinap_lenrek
2016-09-26 23:13 ` lemon
2016-09-26 23:30 ` cinap_lenrek
2016-09-28 2:13 ` lemon
2016-09-28 13:27 ` cinap_lenrek
2016-09-28 14:20 ` cinap_lenrek
2016-09-30 3:47 ` lemon
2016-09-30 6:41 ` cinap_lenrek [this message]
2016-10-18 0:46 ` lemon
2016-09-30 7:37 ` cinap_lenrek
2016-09-30 7:40 ` cinap_lenrek
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=00a9d62e89edb3b24e4c3decfb184298@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/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).