Differences in behaviour of old and new units of MC8090

[Ajay Garg]

There are still some major differences in the behaviours (I need some more
time to jot all the glaring differences in behaviours, but suffices to say,
"new" units are horrible).

As a first step in debugging the issues, I am posting the pics of the two
units, containing the output of "ATI".
The major difference lies in the line containing "+GCAP:" (apart from the
fact that the firmware-versions have a difference of 4 years).

Any ideas if this "+GCAP:" difference is significant?

On Tue, Oct 18, 2016 at 12:01 AM, Ajay Garg <ajaygargnsit at gmail.com> wrote:

> Ohh... as per https://lists.freedesktop.org/archives/modemmanager-devel/
> 2016-August/003338.html, mmcli talks just to ModemManager.
>
> So, as long as ModemManager does not mix up "external requests from mmcli"
> and "internally generated requests", I guess we are fine on this front.
>
> On Mon, Oct 17, 2016 at 11:35 PM, Ajay Garg <ajaygargnsit at gmail.com>
> wrote:
>
>> I tried switching to Direct-IP mode, and ALL mmcli-commands (including *mmcli
>> -m 0 --set-allowed-modes='2G'*) work fine from mmcli itself (without
>> using any AT-commands as such).
>>
>>
>> a)
>> Is this expected behaviour?
>>
>> b)
>> Now, since qmi-proxy is no more there, there are chances of
>> interminglings due to working of ModemManager and mmcli together, right?
>>
>> On Mon, Oct 17, 2016 at 8:48 PM, Aleksander Morgado <
>> aleksander at aleksander.es> wrote:
>>
>>> On Mon, Oct 17, 2016 at 5:10 PM, Ajay Garg <ajaygargnsit at gmail.com>
>>> wrote:
>>> > :O :O :O :O
>>> >
>>> > Of course I switched it to QMI.
>>> > The previous unit that I did all the tests on, ran perfect when
>>> switched to
>>> > QMI mode.
>>> >
>>> > Your reply suggests that some functionalities (like switching to
>>> > 2G-only-mode) would not work in Direct-IP mode.
>>> > If so, Direct-IP would not serve our purpose.
>>> >
>>>
>>> No, I didn't say that. Switching to 2G mode should be ok in Direct IP
>>> mode, using AT commands.
>>>
>>> > I am in the process of retrieving the "ati" output of the
>>> earlier-modem (on
>>> > which things worked perfect in QMI-mode).
>>> > That could probably help in determining if some firmware-mismatch is
>>> causing
>>> > any issue.
>>> >
>>> >
>>> > But Aleksander, this is really bad news.
>>> > Any idea what might have made things working in the earlier-modem in
>>> QMI?
>>>
>>> I have no idea; was it a MC8090 as well?
>>>
>>> --
>>> Aleksander
>>> https://aleksander.es
>>>
>>
>>
>>
>> --
>> Regards,
>> Ajay
>>
>
>
>
> --
> Regards,
> Ajay
>



-- 
Regards,
Ajay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20161019/3c909e17/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Old-Correct-Unit-Firmware.jpg
Type: image/jpeg
Size: 122759 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20161019/3c909e17/attachment-0002.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: New-Problematic-Unit-Firmware.jpg
Type: image/jpeg
Size: 2511374 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20161019/3c909e17/attachment-0003.jpg>