On Fri, 2012-06-22 at 16:00 +0200, Bjørn Mork wrote: > Forest Bond <forest@xxxxxxxxxxxxxxxxxxx> writes: > > > I guess this indicates no QMI support? > > Yes, I guess it does. > > > Or is there some other problem? > > Uncertain. I haven't seen the exact result you got before. > Demonstrates just how much of this I understand ;-) > > > > # ./qmiver.pl --device=1410:b001 > > Debugging: off > > Device: 1410:b001 > > Candidate: ifnum=0 > > control_msg() failed (-32): Broken pipe > > Unsupported endpoint configuration on ifnum=1 > > Unsupported endpoint configuration on ifnum=2 > > Unsupported endpoint configuration on ifnum=4 > > Candidate: ifnum=6 > > control_msg() failed (-108): Cannot send after transport endpoint shutdown > > So that's -ESHUTDOWN returned there. A bit unexpected. I don't really > know why... I did try my qmitest (from git.fdo) on all ports of the device except the ether port, and got nothing. I'll do some Windows traces to see if it does use QMI on the Ethernet endpoints. I know it doesn't do QMI on any of the serial interfaces (ff/ff/ff) based on the Windows drivers. I could be completely wrong, but I'm really expecting QMI on this device, given that it's a MDM9600. 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
