Nevertheless, the usb-modeswitch-data is still a bit chaotic: NoDriverLoading has not been removed contrary to what ChangeLog claims and the generated rule file still tries to bind the drivers. That perhaps still needs fixing.
It is only a matter of cleaning up old code, probably forgotten by Josh during a late night package production session..
Also, there probably still are devices without proper aliases in Linux kernel drivers. At least one of my devices was not recognized (patch sent)
So you recognized this because usb_modeswitch does no longer mask the lack of real driver support. Good!
and by the quick look at the device list I suspect there are more (e.g. 0408:ea16 and 0408:ea26 -- can't test them as I don't have the hardware). Those are going to fail silently now.
Yes, so users who want to have them supported must do something to get them supported, usb_modeswitch is a mode switching tool and not a driver loading tool.
I'm wondering if a warning message could be produced if there are interfaces with no driver bound after the mode switch, so that users could report those and the driver could be fixed?
There is often interfaces which should be excluded from serial driver binding so it is not possible to check that all interfaces has a driver attached, you can not automate this unless you have a database of interface numbers by usb id.
There was a warning message in the past when usb_modeswitch had loaded the option driver and used the new_id function for binding the driver. The result was not more devices being reported to linux maintainers for driver support, most users didn't care to do that because of the "it is working for me, why care" syndrome.
The few reported cases were mostly false positives due to detection timing errors.