On Mon, 2013-11-11 at 18:27 +0100, Bjørn Mork wrote: > Gustavo Zacarias <gustavo@xxxxxxxxxxxxxxx> writes: > > On 11/11/2013 01:10 PM, Dan Williams wrote: > > > >> 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? > > > > I'm not 100% sure how to test the wwan0 interface: init modem, > > AT^NDISUP... to leave it ready and then run a dhcp client on wwan0? > > If that's it then no, wwan0 doesn't work, just cdc-wdm0 is providing > > something "useful". > > If dhcp doesn't work after a successful AT^NDISDUP connection, then > there is still a chance that this actuall is a NCM device. That would > make things easier in many ways :-) > > Please try the huawei_cdc_ncm driver, although I am not completely sure > that works at all at the moment. Snooping on the device in Windows is > another option... > > Or the device might just not support DHCP. You could try the AT^DHCP? > command after connecting, and then configure the wwan0 device manually > using addresses from the output of that command. Yeah, do that. Not all devices reliably support DHCP on the port. Configuring manually with the results of ^DHCP would be a more reliable test. Dan -- 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
