You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some time now, I've been trying to understand exactly how a USB low-speed device should enumerate. It seems the MN(V-USB) code is written for the "normal" error-free enumeration sequence used by Windows. Both Windows and Linux have secondary enumeration sequences that are attempted iff there is an error encountered with the primary sequence.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
For some time now, I've been trying to understand exactly how a USB low-speed device should enumerate. It seems the MN(V-USB) code is written for the "normal" error-free enumeration sequence used by Windows. Both Windows and Linux have secondary enumeration sequences that are attempted iff there is an error encountered with the primary sequence.
I found the following document that describes the Windows enumeration sequence:
https://techcommunity.microsoft.com/t5/microsoft-usb-blog/how-does-usb-stack-enumerate-a-device/ba-p/270685
I haven't found a concise description for Linux, so I've been reading through some of the drivers/usb/core code (hub.c and config.c).
By better understanding enumeration, it may also be possible to find places the code can be simplified.
Beta Was this translation helpful? Give feedback.
All reactions