Huawei E3276 problem

[Bjørn Mork]

Dan Williams <dcbw at redhat.com> writes:

> I always wondered what the "Jungo" devices that were mentioned in that
> driver were.  Now I know :)  I got my driver out of the bits from
> HuaweiE173Eu-1_Linux.7z which I forget where I found it.
>
> It was somewhat interesting that it does QMI in the driver
> (GetConnectionStatus or something like that) to set the carrier.  Also,
> any idea what the "VDF" thing means? 

According to the Windows driver inf: Vodafone. I guess it's just a
cosmetical thingy, for branding.

> The driver I'm looking at has
> matches for:
>
> mbb_NDIS_OPTIMIZED_INTERFACE
> mbb_NDIS_OPTIMIZED_INTERFACE_VDF
> mbb_NDIS_OPTIMIZED_INTERFACE_JUNGO
> mbb_NDIS_OPTIMIZED_INTERFACE_VDF_JUNGO
>
> but doesn't lock to USB product IDs, just 12d1 + class/subclass/proto.

Yup, that's the same I've seen.

While looking at the "Jungo" Windows driver, I note that there are 5
protocol variants supported:

%NCMDeviceDesc% = ew_jucdcncm.ndi, USBCDCNCM\VID_12D1&Subclass_02&Prot_16
%VDFNCMDesc% = ew_jucdcncm.ndi, USBCDCNCM\VID_12D1&Subclass_02&Prot_46
%ECMDeviceDesc% = ew_jucdcecm.ndi, USBCDCECM\VID_12D1&Subclass_02&Prot_07
%ECMDeviceDesc% = ew_jucdcecm.ndi, USBCDCECM\VID_12D1&Subclass_02&Prot_11
%VDFECMDesc% = ew_jucdcecm.ndi, USBCDCECM\VID_12D1&Subclass_02&Prot_37

The ECM variants could maybe be supported by qmi_wwan, if these
firmwares export QMI (and these devices are Qualcomm based, which I
don't know if we have any info on either?).



Bjørn