On Fri, Jan 30, 2009 at 6:52 PM, Greg KH <greg@xxxxxxxxx> wrote: > On Fri, Jan 30, 2009 at 06:23:36PM -0600, Meher wrote: >> Hi, >> I am working on a USB composite device that has a serial interface, >> and a mass storage interface. I added the vendorID and productID to >> the generic_device_ids[] in usb serial generic driver >> (drivers/usb/serial/generic.c). > > You probably really do not want to use the generic driver, but for > initial testing, that should be fine. > any specific reason for not using the generic driver? >> I also added an entry into the >> storage/unusual_devs.h > > Why add an entry here? Does your device not match the usb-storage spec? > i never written a driver for a mass storage device. Can you explain what do you mean by matching usb-storage spec? what does the mass storage class driver look for to determine if the device match the spec? when I use the new_id approach or the bind method, usb-storage driver does detect the mass storage interface and enable the interface. What triggers the auto detection of a mass storage device by the driver? >> but when I plug-in the device at run time, only USB serial devices are >> detected and nonw of the storage devices get detected. I have to >> manually do a echo on bind for the storage driver to bind with this >> device. Is there a way to do this automatically at hotplug? Does Linux >> USB subsystem probe the driver list for the device until it finds a >> first match or does it go through all the drivers? Does this system >> work differently on a composite device? > > It should "just work". What is the output of /proc/bus/usb/devices with > your device plugged in? > I just looked at it and for some reason my system does not have this.. I have all the info in the /sys but I can't find the /proc/bus/usb.. Did I miss anything in the config? > thanks, > > greg k-h > -- Regards, Meher -- 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
