> -----Original Message----- > From: linux-usb-owner@xxxxxxxxxxxxxxx [mailto:linux-usb- > owner@xxxxxxxxxxxxxxx] On Behalf Of Josua Dietze > Sent: vrijdag 22 mei 2009 10:18 > To: Alan Stern > Cc: linux-usb@xxxxxxxxxxxxxxx > Subject: Re: [Bug 13354] Entry in "unusual_devs" keeps modem device > from switching > > > >> The entry for vendor=0x05c6 and product=0x1000 in "unusual_devs.h" > >> is specific for only one maker. There are several other devices > >> which share these IDs (used by a Qualcomm chipset for storage device > >> mode) but need a different handling to switch their mode to "modem". > >> > >> I received a report recently that one device ("Anydata ADU-510L") > >> could not be switched by the userspace tool "usb_modeswitch" when > >> used with 2.6.30rc5, compared to 2.6.27. In the latter, dmesg shows > >> there are problems with the storage device at plugin time, > >> presumably caused from the "option_ms_init" function, but afterwards > >> the storage device is bound correctly. This fails in 2.6.30rc5 with > >> the error: > >> "usb-storage: probe of 6-2:1.0 failed with error -5". > > > Alan Stern schrieb: > > > A usbmon trace of the failed probe might provide a clue. > > > I'll try to get one from the reporter. Anyway, the problem vanished > when commenting out the entry in "unusual_devs.h". > > >> I presently know about three different modem devices (or families) > >> that show vendor=0x05c6 and product=0x1000 (all storage class): > >> > >> - Older "Option" 3G modems > >> - AnyData 3G modems > >> - Samsung SGH-Z810 > >> > >> They need three different switching commands which may interfere if > >> used in a sequence. > > > If there's no way to tell these devices apart but they need different > > switching commands, how do other operating systems handle them? > > > They have their Windows drivers onboard in the 'storage part'; > either these drivers do an (yet unknown) additional ID routine, or > (what I suspect at least in some cases) they don't care at all about > the possibility of a third party device with the same ID. > > I wonder if Filip Aben of Option can comment on this (or did he so > earlier?). Does the Windows driver e.g. of the GlobeSurfer iCON > identify the device apart from the vendor/product ID? The text > description says just "Qualcomm, Inc." ... Those older devices were switched in (windows) user-space and I believe they were identified by their INQUIRY data which, for Option devices, contains "ZCOption <something>" Currently, we don't need to identify vendor=0x05c6 and product=0x1000. Anything except our first Zero-CD products will come up with Option ID's. Thanks, Filip- -- 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
