Potential issues with NetBSD uhid backend #797
Labels
No labels
3rdparty
Android
API
Author does not respond
bsd
bug
build system/CI
ci-virtual-device
CMake
Contributions Welcome
Core
dependencies
device-specific
documentation
don't_merge
duplicate
enhancement
Example
Haiku
hidraw
hotplug
info required
invalid
libusb
macOS
Misc
Not an issue
question
Release
Test
Test GUI
Windows
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-libusb/hidapi#797
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
From the testing results here NetBSD uhid example does not work for me with the FX2HID example even if I force it to full speed USB mode.
However, it does not seem to work with the FX2HID example.
Using the original FX2HID example from Jan Axelson.
http://janaxelson.com/hidpage.htm
Run log with the FX2HID default example with two bytes HID Input/Output report.
I will test with a physical machine and another generic USB HID device.
Still using VM but changes to another Generic USB HID device mentioned here. The device works fine under FreeBSD 15 VM using PR #730.
Feature Report loopback is working fine but Input/Output loopback does not work under NetBSD 10.1 VM.
Still using VirtualBox VM.
CircuitPython USB HID example from here, using Raspberry Pi Pico 2 (loop back the contents of Output Report 2 to Input Report 1, other than the first byte which is the Report ID).
https://github.com/libusb/hidapi/discussions/590#discussioncomment-6201631
It is mostly working except for the last case -- somehow Input Report ID 1 is missing.
Using a physical machine, Intel N4200 CPU based mini PC
CircuitPython USB HID example from here, using Raspberry Pi Pico 2 (loop back the contents of Output Report 2 to Input Report 1, other than the first byte which is the Report ID).
Interestingly it work for the odd time but failed for the even time.
Same for the physical machine.