Hi Stefan,
thanks for testing on real hw.
It looks like there is corner case, that Greg mentioned in this thread. atusb_get_and_show_build() reads firmware build info, which may have various length.
Maybe we can change atusb_control_msg() to usb_control_msg() in atusb_get_and_show_build(), since other callers do not have this problem
That works for me.
I will also have a look at the use of the modern USB API for next. The
fix here has a higher prio for me to get in and backported though. Once
we have this we can look at bigger changes in atusb.