On Fri, 6 Sep 2013, Victor Leschuk wrote: > Hello, thanks for the answer. Maybe I sound stupid but how can I tell > g_mass_storage which controller to use? If I unload dummy_hcd and then > try to modprobe g_mass_storage I get an error "no such device". There is no way to tell g_mass_storage which device controller to use. It will bind to the first one that is available. Note that unless your computer has special hardware, without dummy-hcd there will be _no_ controllers for g_mass_storage to bind to. > # lsusb > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > Bus 002 Device 003: ID 046d:c050 Logitech, Inc. RX 250 Optical Mouse > Bus 002 Device 004: ID 046d:c31d Logitech, Inc. > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub This listing is irrelevant. lsusb is a host-side program, but g_mass_storage is a device-side driver. Alan Stern -- 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
