Andrey Konovalov

Ah, I suspect this is related to #12. Please run the proxy with verbose log enabled (so that `print_eps_info` prints its stuff) and show the log. And also share the...

Yeah, looks like the same issue: the device uses endpoint addresses 6 and 7 (`0x86 and 0x87`), but your UDC only supports addresses up to 4. You can try modifying...

And do you see any data flowing through the endpoints (the proxy should print it if you run it with debugging output enabled). If you do, then maybe the data...

Thank you for testing on R Pi Zero 2! For saying `Yes`, we should provide the [test results](https://github.com/xairy/raw-gadget/tree/master/tests), like for the other boards. But you can just change the `Yes`...

Awesome analysis @fellair, thank you! With regards to the drivers that fail various USB descriptor checks (speed, endpoints, etc.) — adding new `syz_usb_connect$` variants is the way to go. These...

> However, some usb drivers actually use BULK and INT requests during driver probe instead of CTRL. This happens after the `SET_CONFIGURATION` request, right? I think then handling these requests...

> Got a little confused by the order here. Did you mean: > > * during probe: `syz_usb_connect` + `syz_usb_finish_probe` (`SET_CONFIGURATION `and then deal with other CTRL-requests in a fixed...

1. Yes, this makes sense. You can also look through the existing `dev_*.txt` descriptions - I suspect some of them can be easily adapted to handle USB-emulated devices as well...

Thank you for working on this @fellair! Keeping `syz_usb_connect_scripted` separate on the syzlang level for now is fine, but I think the C implementations should be merged. With the current...

Looks much better! I left some comments/questions. > Less duplicate code (although there is still some - that is by design FOR NOW) Yes, definitely some duplication between the new...