| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
changed logic a bit to support situation when there is no config activated. In
this case indication generated with error NOT_PROVISIONED.
|
|
|
|
|
|
| |
There won't be any indication if no configs are available.
Based on a patch from Aliaksandr Barouski <alex.borovsky@gmail.com>.
|
| |
|
|
|
|
|
| |
Mostly coding style fixes, although the patch also fixes several allocation
issues when freeing GSlices.
|
| |
|
|
|
|
|
|
| |
The original implementation actually had some bugs when freeing the output
array in error conditions. Also, use g_ascii_xdigit_value() instead of
custom conversions.
|
| |
|
|
|
|
| |
Added calls for configure hp4120 LTE modem
|
|
|
|
|
|
| |
Based on a patch from Aliaksandr Barouski <alex.borovsky@gmail.com>
https://bugs.freedesktop.org/show_bug.cgi?id=96465
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We want to mark some TLV fields as reserved and not exposed through the
public API due to alignment or other issues.
|
|
|
|
|
|
|
|
| |
QMI_WDS_IP_FAMILY_UNSPECIFIED = 8 but ip_type gets initialized to
0, so the "IP Family Preference" was always being sent with an
unrecognized value.
Fixes: 81c21379 qmicli: add support for IP type to --wds-start-networ
|
| |
|
|
|
|
|
| |
Some devices (Quectel EC21) lie about their supported DMS version,
so assume a reasonable DMS version if the WDS version is high enough.
|
|
|
|
|
| |
If the device cannot exit low-power mode it sometimes reports a reason,
like pri-image-misconfiguration.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
But only seems supported on GSM/UMTS firmware. Tested on Novatel USB1000:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Need CDMA/EVDO firmware for it though. Tested on Novatel USB1000:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tested on Novatel USB1000:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
But you usually need a CDMA/EVDO capable device and firmware to
use it. Tested on Novatel USB1000:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
But of course you need a CDMA/EVDO capable device and firmware version
to read it. Tested on Novatel USB1000:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tested on Novatel USB1000:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tested on Novatel USB1000:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] QMI Device supports 6 services:
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] ctl (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wds (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] dms (1.1)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] nas (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] wms (1.0)
[07 Sep 2016, 10:43:19] [Debug] [/dev/cdc-wdm1] pds (1.0)
|
| |
|
| |
|
|
|
|
| |
'--dms-set-firmware-pref'
|
|
|
|
| |
Signed-off-by: Bjørn Mork <bjorn@mork.no>
|
|
|
|
|
|
|
|
|
| |
The firmware preference must be set to the new firmware version
before a firmware download can take place. Add support for setting
the firmware preference independently of the currently installed
images.
Signed-off-by: Bjørn Mork <bjorn@mork.no>
|
| |
|
|
|
|
|
|
|
| |
Don't know what I was thinking here, but the referenced channels
are of course *RX* channels. None of my modems can do TX CA. Yet :)
Signed-off-by: Bjørn Mork <bjorn@mork.no>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The lifecycle for transactions going through the MBIM backend is a bit different
w.r.t. the default one:
* Given that libmbim has its own timeout management for the commands sent, we
will rely on it instead of having our own. This means that we always assume
that mbim_command() finishes, as it should be.
* Instead of using the response QMI message to match a transaction, when using
MBIM we use the transaction key given in the context passed to mbim_command()
and by doing this we make sure that the transaction is always removed from
the tracking table, regardless of whether the QMI message inside matched or
not.
|