Chen

> > I put cdc/acm in src because it is a standard usb interface. But ftdi is not. > > I think that's a rather arbitrary distinction. A driver is...

The code intends to support a large range of usb devices, however due to lack of test, there are many incompatibilities issues. If you are interested, you are welcomed to...

I don't know what's the best practice, but it might break existing code not impl-ing Debug?

I believe the core protocol part can be built to WebAssembly, but the rusb/tokio parts may need some porting to allow custom transport.

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

> > 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 pushed code to master branch, could you please test? I don't have testbed for now.

If you emulating in Rust code, you might need to implement the new trait `UsbDeviceHandler` to handle the requests.

It is possible that the SMBus feature uses something not well-implemented.

Remember to lower ENVREQ for riscv64 machines.