On Mon, 2013-11-11 at 15:43 +0100, Bjørn Mork wrote: > Gustavo Zacarias <gustavo@xxxxxxxxxxxxxxx> writes: > > > With minicom on /dev/cdc-wdm0 after patching qmi_wwan it seems to be > > responsive to AT commands so yes it seems we are dealing with ECM here. > > I'll send a followup patch to include qmi_wwan. This is a bit confusing... so you added the device to qmi_wwan, and now one of the AT ports works (cdc-wdm0) and the net port also works, as exposed by qmi_wwan? What's the full lsusb -v for this device after it's modeswitched? I looked through all the recent mails you've sent and couldn't find one. Are the descriptors for standard USB specifications (ACM, WDM, ECM, NCM, etc), or are they vendor-specific 0xFF-type ones but implement the standard protocols? > Maybe run a small discussion on the ModemManager list first? This would > be the first non-QMI device there, and I don't think userspace is > prepared for that.... We've got a bug open for this in ModemManager: https://bugzilla.gnome.org/show_bug.cgi?id=699741 Quite a few 2008 - 2009-era SonyEricsson phones (TM-506 and others) and many of the Ericsson MBM WWAN minicards expose a cdc-wdm AT port, so this device wouldn't be the first to expose an AT-capable cdc-wdm port. ModemManager does not currently support AT-capable cdc-wdm interfaces though, since the SE devices didn't use them for the primary/secondary AT ports. > I expected this type of device might exist, but we haven't really tried > to support it before (AFAIK). Although the qmi_wwan driver doesn't care > about whether the embedded control protocol is QMI or AT or something > else, current userspace applications do. I am not entirely sure about > how this should be handled, but it should be sorted out before we start > adding non QMI devices to the driver. If we start adding non-QMI devices to the driver, then we should rename it to something more generic. Or, better yet, make the driver generic, and keep qmi_wwan a sub-driver with all the current device IDs. Dan > > >> This device use ff/ff/ff for class/subclass/protocol on all interfaces, > >> is that right? > > > > Yes, for bInterfaceNumber 0..3 i've got Class/SubClass/Protocol 255. > > 4 and 5 are mass storage which surely correspond with the MicroSD slot > > and internal flash cdrom emulation/image. > > Interface 1 has an alternate setting with one endpoint (#0) or 3 > > endpoints (#1) if that's of any use. > > You can take a peek at lsusb -vv output @ > > https://www.zacarias.com.ar/e173s.txt > > > Thanks > > > Bjørn > -- > 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 -- 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
