On Thu, Jul 22, 2010 at 5:44 AM, Adam Kropelin <akropel1@xxxxxxxxxxxxxxxx> wrote: > I have a composite device which consists of an RNDIS interface as well > as several additional standard interfaces (cdc-serial, umass, etc.). > These are all contained in a single configuration using IADs. I've > discovered that kernels without CONFIG_USB_NET_RNDIS_HOST enabled will > refuse to select any configuration, rendering the standard interfaces > inaccessible (at least without additional jiggering). > > 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? > > Thoughts? > Why reject the configuration at all? It is just there will be no rndis support from the host Linux OS. But it is still a valid USB device. -- Xiaofan http://sourceforge.net/projects/libusb-win32/ -- 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
