Open jamesadevine opened 1 year ago
Which USB devices are you using? This seems to be a device-specific request by Linux driver.
You can find the definition of 0xc0
at https://www.beyondlogic.org/usbnutshell/usb6.shtml#SetupPacket
Hi @jiegec , I faced same issue. My usb device is USB uart (0403:6010 Future Technology Devices International Limited Dual RS232-HS) Did you test with usb serial device?
Hi @jiegec , I faced same issue. My usb device is USB uart (0403:6010 Future Technology Devices International Limited Dual RS232-HS) Did you test with usb serial device?
I see, the linux ftdi driver generates the request:
#define FTDI_SIO_GET_LATENCY_TIMER_REQUEST_TYPE 0xC0
#define FTDI_SIO_GET_MODEM_STATUS_REQUEST_TYPE 0xc0
#define FTDI_SIO_READ_PINS_REQUEST_TYPE 0xc0
#define FTDI_SIO_READ_EEPROM_REQUEST_TYPE 0xc0
Will try to fix this. Currently I don't have a FTDI serial at hand, I can access one later this month.
I pushed code to master branch, could you please test? I don't have testbed for now.
Thanks! I am indeed emulating an ftdi device.
If you emulating in Rust code, you might need to implement the new trait UsbDeviceHandler
to handle the requests.
yup - on it! Will contribute FTDI device handler when I have something that looks like it works...
Hiya!
I have an app exposing a usbip virtual device and getting the following when running
sudo lsusb -v
from Linux:First, I'm not entirely sure what the
0xc0
request type is, any ideas? Second, it seems a bit harsh to simply panic - on a normal USB device I think it is conventional to stall? Is there a usbip equivalent that could be implemented instead?