[ANN] ModemManager 1.2-rc1

[Aleksander Morgado]

>> For the MF60 I only recall some tests done by Bjørn back in the day,
>> where IIRC he said the WDS service wasn't behaving properly. Once I
>> get the one I bought I'll recheck what happens with the WDS service in
>> that one, but anyway, maybe it's not a bad idea to enable QMI for all
>> ZTE devices; especially when the MF60 is actually a MiFi device (e.g.
>> not actually critical if it isn't properly handled by MM).
> 
> Yes, the MF60 is a MiFi device with its own connection management
> appication. So it doesn't really need QMI or AT commands at all. I
> believe that is the reason it behaves odd.
> 
> The management application is most likely talking to the modem using the
> exact same QMI channel that is exported over the USB link. I did look a
> bit at the firmware, and I am pretty sure it is exported via some qmi
> proxy function which
>  - have a dummy implementation of a couple of QMI_WDS commands,
>  - filters out the rest of QMI_WDS,
>  - let everything(!) else through
> 
> I guess the idea is that the internal management needs exclusive access
> to QMI_WDS. Never mind that you can completely screw up using QMI_CTL or
> QMI_NAS...
> 
> The problem with the qmi proxy thing is that it crashes on all the
> commands that were supposed to be filtered out.  That's most likely
> unintentional, and could very well be fixed in newer firmware revisions.
> 
> I beleive there is no reason to assume anything wrt chip revisions or
> Qualcomm firmware.  This is most like a ZTE firmware application
> problem, related to this kind of MiFi device with QMI.  I don't know if
> there are anything similar? I believe most other MiFi devices (or other
> modems with builtin management apps) won't give you access to the QMI
> channel?
> 
> And it does seem a bit strange that they provide QMI access at all over
> the USB link.  They could have just made it a plain CDC ECM link, and
> this odd proxy would not have been necessary.  But my guess is that the
> proxy makes the device work with their Windows driver, and they might
> have some QMI Windows application they wanted to use?
> 

So, the MF60 I bought in ebay works nicely as a MiFi device, but it
seems it isn't recognized as a USB modem in either Linux or Windows :/
Weird thing is that it cannot even setup the internal mass storage
partition, not even in Windows. Could be broken, for what I can say.

Anyway, I think we should then enable all QMI support for ZTE devices
too, and then do the 1.2 release. If problems do arise with some ZTE
devices running in QMI mode, we can always apply the blacklist later I
guess.

-- 
Aleksander