On Thu, 3 Feb 2005, Paulo Marques wrote: > There is something weird though... in unsual_devs.h this PID/VID seems > to be this one: > > UNUSUAL_DEV( 0x090a, 0x1001, 0x0100, 0x0100, > "Trumpion", > "t33520 USB Flash Card Controller", > US_SC_DEVICE, US_PR_BULK, NULL, > US_FL_NEED_OVERRIDE ), > > which seems to be this product: > > http://www.trumpion.com.tw/prod_m03_3352x.htm > > which seems very different from the one you've shown (www.cmdrive.com) > > Is "cmdrive" using the VID/PID from another vendor (or vice-versa)? Or > am I missing something?
You need to realize that in many cases the storage device itself and its USB interface chip are made by different manufacturers. Sometimes the design is such that the default descriptors from the interface's manufacturer are overridden and sometimes not. So you can easily get different devices with different vendor and product strings but the same vendor and product IDs. It happens all the time. Fortunately it doesn't matter. The vendor and product strings listed in the unusual_devs.h entry are used only if the device itself doesn't provide any strings. > If this is the case, I guess there is not much we can do, since there is > no way for the kernel to tell those devices appart... :( No there isn't, and furthermore there's no reason for the kernel to tell them apart. Since they have the same interface chip they will behave the same way. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
