--- On Thu, 7/22/10, Michał Nazarewicz <m.nazarewicz@xxxxxxxxxxx> wrote: \ > > > > I would propose one of two solutions: < > (A) Reject the configuration as > > we do today, but only if there are additional > > configurations available > > to choose from (i.e. bNumConfigurations > 1), or > > (B) Reject the > > configuration only if there are no additional > interfaces in the config > > besides RNDIS. > > > > I lean toward (A). > > > > In the broader case, to some extent I wonder if > > the logic in > > usb_choose_configuration() should be as simple as > choosing the one and > > only config regardless of any heuristics in all cases > where only a > > single config is present. Is there value in > > failing to select any > > configuration at all? Probably not; I don't recall the original code working that way. > > I had an idea once to make the code choose configuration > with the smallest > bConfigurationValue. This way, composite > devices could provide RNDIS > configuration as the first one with bConifgurationValue == > 2 and the other > configuration, as second one, with bConfigurationValue == > 1. This is what > Ethernet gadget does for instance. ... which ISTR made MS-Windows happier. - Dave -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
