summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* release: bump version to 1.16.01.16.0Aleksander Morgado2016-07-071-3/+3
|
* NEWS: update for 1.16.0Aleksander Morgado2016-07-071-0/+40
|
* build: distcheck always uses qmi-over-mbim supportAleksander Morgado2016-07-071-1/+3
|
* docs: add missing reference for 'NAS force network search'Aleksander Morgado2016-07-071-0/+1
|
* libqmi-glib,device: avoid unref-ing MBIM message if none receivedAleksander Morgado2016-07-071-1/+2
|
* libqmi-glib,device: fix build with mbim-qmux disabledAleksander Morgado2016-07-071-7/+12
|
* libqmi-glib,version: new symbol to flag qmi-over-mbim supportAleksander Morgado2016-07-073-1/+23
|
* libqmi-glib,mbim: run the mbim close operation synchronouslyAleksander Morgado2016-07-071-20/+40
|
* libqmi-glib,mbim: don't create mbim device multiple timesAleksander Morgado2016-07-071-0/+9
|
* libqmi-glib,mbim: rework transaction management on mbim backendAleksander Morgado2016-07-072-56/+159
| | | | | | | | | | | | | | | 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.
* libqmi-glib,mbim: destroy mbim device on port closeAleksander Morgado2016-07-071-10/+28
|
* libqmi-glib,device: include steps for mbim device create/openAleksander Morgado2016-07-071-39/+78
|
* libqmi-glib,device: fix indentationAleksander Morgado2016-07-071-12/+12
|
* build: update `--enable-mbim-qmux' rulesAleksander Morgado2016-07-072-14/+25
| | | | If libmbim 1.14.0 found, enable QMI over MBIM support.
* qmicli: support MBIM EXT_QMUX devicesBjørn Mork2016-07-071-0/+7
| | | | Signed-off-by: Bjørn Mork <bjorn@mork.no>
* libqmi: support MBIM EXT_QMUX serviceBjørn Mork2016-07-074-5/+171
| | | | Signed-off-by: Bjørn Mork <bjorn@mork.no>
* qmicli: remove unused user_data in qmi_device_new() callbackAleksander Morgado2016-07-071-1/+1
| | | | Reported-by: Jing Chen <jing.chen@spirent.com>
* qmi-network: avoid more bashisms when comparing stringsAleksander Morgado2016-06-301-1/+1
|
* qmi-network: avoid bashisms when checking argumentsAleksander Morgado2016-06-191-1/+1
|
* nas: support 'Force Network Search'Aleksander Morgado2016-06-102-0/+55
|
* libqmi-glib,test: fix implicit conversions to long typesAleksander Morgado2016-06-011-2/+2
| | | | | | | 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: avoid redefining 'index'Aleksander Morgado2016-04-031-3/+3
| | | | | | | 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
* libqmi-glib: handle api break introduced in 7fe1238 (released in 1.14.0)Aleksander Morgado2016-04-032-0/+14
| | | | | We provide a compatibility symbol to try to provide a better backwards compatibility.
* libqmi-glib: handle api break introduced in 7ca279e9a42 (released in 1.14.0)Aleksander Morgado2016-04-036-0/+181
| | | | | Commit 7ca279e9a42 introduced a couple of method renames that we now try to recover in order to provide a better backwards API compatibility.
* docs: add missing entries for 'NAS Get LTE Cphy CA Info'Aleksander Morgado2016-04-032-0/+11
|
* nas: no exact version for 'Get LTE Cphy CA Info'Aleksander Morgado2016-04-031-1/+0
| | | | We're not sure about it, so just don't specify it.
* nas: untabifyAleksander Morgado2016-04-031-27/+26
|
* nas: implement 'Get LTE Cphy CA Info'Bjørn Mork2016-04-033-0/+202
| | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* libqmi-glib: use ((guint64) 1) << 31 for QMI_*_BAND_CAPABILITY_BC_15Reinhard Speyerer2016-03-252-2/+2
| | | | | | | | | | | | | | 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>
* qmicli,voice: it's gplv2+, not gplv3+Aleksander Morgado2016-03-221-1/+1
| | | | | | | 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>
* build: README and NEWS always existAleksander Morgado2016-03-211-1/+1
|
* build: run configure script from builddir rather than srcdirAleksander Morgado2016-03-211-3/+4
| | | | | | | Based on an equivalent patch from Philip Withnall <philip@tecnocode.co.uk> for libmbim; see: https://bugs.freedesktop.org/show_bug.cgi?id=94639
* qmicli: fix --dms-get-band-capabilities output on 32-bit platformsReinhard Speyerer2016-03-201-1/+1
| | | | | | | | | | | The @enum_name@_build_string_from_mask template in qmi-flags64-types-template.c uses a local gulong number variable. On platforms where sizeof(gulong) < sizeof(Qmi*BandCapability) this may cause bands to be missing from qmicli output or incorrect bands to be contained in the output. Replace gulong number with guint64 number to fix this. Signed-off-by: Reinhard Speyerer <rspmn@arcor.de>
* build: post release version bump to 1.15.0 (development)Aleksander Morgado2016-03-171-1/+1
|
* release: bump version to 1.14.01.14.0Aleksander Morgado2016-03-171-4/+4
|
* NEWS: update for 1.14.0Aleksander Morgado2016-03-171-5/+74
|
* docs: updated copyright yearsAleksander Morgado2016-03-171-0/+4
|
* docs: include 1.12 and 1.14 symbols listAleksander Morgado2016-03-171-0/+8
|
* libqmi-glib,device: add documentation of when the new methods were introducedAleksander Morgado2016-03-171-0/+6
|
* qmi-network: don't explicitly quote start network argumentAleksander Morgado2016-03-041-1/+1
|
* qmi-network: support APN user/passwordAleksander Morgado2016-03-041-4/+29
|
* qmicli,test: add key/value parser testsAleksander Morgado2016-03-041-1/+96
|
* qmi-network: update checks of variable contentsAleksander Morgado2016-03-041-28/+28
| | | | Use -z and -n consistently.
* trivial: whitespace fixesDan Williams2016-03-0313-435/+435
|
* qmi-codegen: fix too-small transaction id in internal message codeDan Williams2016-02-101-1/+1
| | | | | | Found by John. https://bugs.freedesktop.org/show_bug.cgi?id=94083
* qmicli: fix PLMN printingBjørn Mork2016-02-081-2/+6
| | | | | | | | 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>
* build: bump micro version to 1.13.7Aleksander Morgado2016-01-301-1/+1
| | | | | This is not an official release, just an easy way to identify when the new support for the UIM PIN actions was introduced.
* uim: implement 'UIM Change PIN'Aleksander Morgado2016-01-303-0/+177
|
* uim: implement 'UIM Unblock PIN'Aleksander Morgado2016-01-303-0/+177
|
* uim: implement 'UIM Verify PIN'Aleksander Morgado2016-01-303-0/+172
|
View Lorry Controller Status