Thomas Schäfer <tschaefer@xxxxxxxxxxx> writes: >> Actually, the K3565-Z doesn't support QMI either :) It does have the >> possibility of a pseudo-ethernet port, but that's a custom >> implementation by ZTE's firmware team that isn't at all QMI related. >> Thankfully on the K3565-Z it's more or less standard and we don't have >> to go to the lengths to support it that we do for QMI-based devices. It >> appears the K3565-Z is based on the MDM6290 which is the same chipset >> that's in your Sierra 8790 :) Thus no QMI. > > I can't follow. I use the qmi-script and libs from Bjørn Mork to get the > pseudo-ethernet to work and you say there is no qmi? > > Ok, you are the expert. > > libqmi (zte-k3565z)says: > > [24 Apr 2012, 18:14:47] [Debug] Checking version info... > [24 Apr 2012, 18:14:47] [Debug] [/dev/cdc-wdm0] QMI Device supports 4 > services: > [24 Apr 2012, 18:14:47] [Debug] [/dev/cdc-wdm0] ctl (1.2) > [24 Apr 2012, 18:14:47] [Debug] [/dev/cdc-wdm0] wds (1.3) > [24 Apr 2012, 18:14:47] [Debug] [/dev/cdc-wdm0] dms (1.2) > [24 Apr 2012, 18:14:47] [Debug] [/dev/cdc-wdm0] nas (1.0) > [24 Apr 2012, 18:14:47] [Debug] Asynchronously getting IDs... > [/dev/cdc-wdm0] Device IDs retrieved: > ESN: 'not available' > IMEI: '357867027052282' > MEID: 'not available' > [24 Apr 2012, 18:14:47] [Debug] Client CID released I am certainly no expert on this either, but if that works then the device must support QMI :-) >> (Technically QMI and pseudo-ethernet interfaces are completely >> unrelated, it just happens that every Qualcomm-derived device that >> supports QMI has the capability of a pseudo-ethernet interface even if >> the OEM's firmware team doesn't actually expose it.) > > I try to understand. The MDM6200 is listed as a Gobi chipset by Qualcomm, but I have no idea how that relates to MDM6290... 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
