Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
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.
|
|
|
|
'--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.
|
|
|
|
|
|
|
|
If libmbim 1.14.0 found, enable QMI over MBIM support.
|
|
Signed-off-by: Bjørn Mork <bjorn@mork.no>
|
|
Signed-off-by: Bjørn Mork <bjorn@mork.no>
|
|
Reported-by: Jing Chen <jing.chen@spirent.com>
|
|
|
|
cc1: warnings being treated as errors
test-generated.c: In function 'dms_get_time_ready':
test-generated.c:292: error: integer constant is too large for 'long' type
test-generated.c:298: error: integer constant is too large for 'long' type
|
|
qmicli-nas.c: In function 'get_lte_cphy_ca_info_ready':
qmicli-nas.c:2780:12: error: declaration of 'index' shadows a global declaration [-Werror=shadow]
cc1: all warnings being treated as errors
make[7]: *** [qmicli-qmicli-nas.o] Error 1
|
|
We provide a compatibility symbol to try to provide a better backwards
compatibility.
|
|
Commit 7ca279e9a42 introduced a couple of method renames that we now try to
recover in order to provide a better backwards API compatibility.
|
|
Carrier aggregation is much more fun when you can watch it being
activated :)
$ qmicli -p -d /dev/cdc-wdm0 --nas-get-lte-cphy-ca-info
[/dev/cdc-wdm0] Successfully got carrier aggregation info
DL Bandwidth: '20'
Secondary Cell Info
Physical Cell ID: '101'
TX Channel: '3050'
DL Bandwidth: '20'
LTE Band: 'eutran-7'
State: 'activated'
Primary Cell Info
Physical Cell ID: '299'
TX Channel: '1450'
DL Bandwidth: '20'
LTE Band: 'eutran-3'
Secondary Cell index: '1'
I have absolutely no clue about the required NAS version, so I just put
the current version I have there...
Signed-off-by: Bjørn Mork <bjorn@mork.no>
|
|
The current definition of QMI_*_BAND_CAPABILITY_BC_15 gets converted to a
negative value (0xffffffff80000000) which causes false positives for BC15
to be returned from dms_add_qmi_bands() and nas_add_qmi_bands() in
ModemManager/src/mm-modem-helpers-qmi.c when a matching QMI band (e.g.
WCDMA900) is present in qmi_bands like in this example
https://lists.freedesktop.org/archives/libqmi-devel/2016-March/001572.html .
Replace 1 << 31 with ((guint64) 1) << 31 for QMI_*_BAND_CAPABILITY_BC_15
to avoid incorrect mmcli "Bands | supported: 'cdma-bc15-aws, ...'" output.
Signed-off-by: Reinhard Speyerer <rspmn@arcor.de>
|
|
The license in this source file wasn't updated as all the others because it was
cherry-picked later on from an old branch.
Reported by Michael Biebl <mbiebl@gmail.org>
|
|
|
|
|
|
|
|
BCD PLMNs with 2 digit MNCs will have an 'F' digit between
the MCC and the MNC. This maps to \0, which would cause
a truncated result string with only the MCC.
Signed-off-by: Bjørn Mork <bjorn@mork.no>
|
|
|
|
|
|
|
|
|
|
These new actions allow to query or update the data format expected by the
kernel in the WWAN interface associated to the cdc-wdm device used.
|
|
Userspace is in charge of defining the data format to be used in the WWAN net
interface, both in the device itself (e.g. through CTL or WDA requests) and also
in the kernel (e.g. through /sys/class/net/<WWAN>/qmi/raw_ip sysfs files).
These new API methods allow to query and modify the data format expected by the
kernel.
|
|
|
|
|
|
|
|
3gpp2-profile parameters
|
|
|
|
This would be equivalent to the new format used in mbimcli's --connect
operation, and will allow us to add new parameters easily.
Note that The old legacy format will still be supported, for backwards
compatibility.
|
|
|