From: qwx@sciops.net
To: 9front@9front.org
Subject: Re: [9front] wtb: usb gamepad that works reliably with joy(1)
Date: Fri, 16 Feb 2024 18:10:03 +0100 [thread overview]
Message-ID: <83F57A9AF23B51F453034FE4C5536299@wopr.sciops.net> (raw)
In-Reply-To: <BD3522D43FA20C9AF1CD58A63A819AAC@gaff.inri.net>
On Fri Feb 16 17:44:28 +0100 2024, sl@stanleylieber.com wrote:
> i got an ibuffalo class usb gamepad bsgp801 and 9front treats it as a
> mouse. when i try to use it with joy(1), i get the following error:
>
> nusb/joy: getdev: device or object already in use:
> '/dev/usb/ep8.0/data'
>
> sl
What happens if you kill nusb/kb?
; kill kb | rc
Does it release it or does another nusb/kb immediately start?
If it works fine before, it would be enough to force this in
nusbrc (requires recompiling the kernel), for example:
diff 957863b064ed01ebb1297ddd368ce5a78c957f5e uncommitted
--- a//sys/src/9/boot/nusbrc
+++ b//sys/src/9/boot/nusbrc
@@ -15,6 +15,10 @@
if(~ $#* 5 && ! test -e /env/nousbhname)
id=$1:$5
switch($2$3){
+ case 20110715
+ # avoid nusb/kb on mpk mini
+ case 17810a99 17810a96 05832060
+ # let nusb/joy take this one
case 0b957720 0b95772a 0db0a877 13b10018 15577720 20013c05 07d13c05 05ac1402
nusb/ether -t a88772 $etherargs $id
case 0b951780 14eaab11 17370039 0411006e 050d5055
next prev parent reply other threads:[~2024-02-16 17:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 22:57 sl
2024-02-05 18:58 ` mkf9
2024-02-05 20:40 ` qwx
2024-02-05 20:49 ` Kurt H Maier
2024-02-05 21:05 ` qwx
2024-02-10 4:15 ` sl
2024-02-10 5:19 ` qwx
2024-02-10 5:24 ` Stanley Lieber
2024-02-10 6:12 ` qwx
2024-02-16 16:43 ` sl
2024-02-16 16:46 ` sl
2024-02-16 17:10 ` qwx [this message]
2024-02-16 17:34 ` sl
2024-02-16 18:01 ` qwx
2024-02-16 23:40 ` sl
2024-02-17 0:55 ` qwx
2024-02-17 1:33 ` sl
2024-02-17 2:37 ` Sigrid Solveig Haflínudóttir
2024-02-16 18:02 ` qwx
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=83F57A9AF23B51F453034FE4C5536299@wopr.sciops.net \
--to=qwx@sciops.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).