Closed GoogleCodeExporter closed 9 years ago
nsub/kb is build into the kernel image (as is nusb/disk and nusb/usbd) to
support usb devices before we mount the root filesystem. if theres no other usb
driver hogging that
endpoint, you can test and debug your modified nusb/kb passing it the device
id. (cat /dev/usb/ctl or cat /dev/usbevent to get the id)
Original comment by cinap_le...@felloff.net
on 10 Aug 2012 at 8:47
I had to kill bootfs's nusbrc to keep it from ever attaching to the device. (I
had thought that I would be able to attach my patched driver after the other
one exited, but that didn't work within VirtualBox.)
The fix is to change nusb/kb's buffer size from 32 to 64 (bytes). (The mouse's
maxpkt is 64, and it stops working after a while if nusb/kb only does 32-byte
reads.) I have a patch to fix this, and a patch to make nusb/kb print the
weird maxpkt and try to cope with too-large values, but I can't transfer them
out of my 9front VM.
Original comment by rransom....@gmail.com
on 11 Aug 2012 at 8:45
See attached for my patches.
Original comment by rransom....@gmail.com
on 12 Aug 2012 at 1:50
Attachments:
commited in rc657571d19d1
thank you very mutch! :)
Original comment by cinap_le...@felloff.net
on 13 Aug 2012 at 8:45
Original issue reported on code.google.com by
rransom....@gmail.com
on 10 Aug 2012 at 5:51