aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* libqmi-glib,device: port create_iostream to use GTaskBen Chan2017-04-181-83/+88
|
* libqmi-glib,device: port qmi_device_release_client to use GTaskBen Chan2017-04-181-40/+23
|
* qmi-codegen: port client code generation to use GTaskBen Chan2017-04-181-30/+17
|
* libqmi-glib,device: port qmi_device_open to use GTaskBen Chan2017-04-181-124/+155
|
* libqmi-glib,device: port qmi_device_allocate_client to use GTaskBen Chan2017-04-181-58/+57
|
* libqmi-glib,device: port qmi_device_set_instance_id to use GTaskBen Chan2017-04-181-14/+13
|
* libqmi-glib,device: port qmi_device_get_service_version_info to use GTaskBen Chan2017-04-181-18/+9
|
* libqmi-glib,device: port initable_init_async to use GTaskBen Chan2017-04-181-60/+41
|
* loc: add boilerplate and start/stop message skeletonsDan Williams2017-04-1711-7/+204
|
* utils: drop useless g_file_test() callMikhail Efremov2017-04-141-2/+4
| | | | | canonicalize_file_name() returns NULL if file doesn't exist, so no need to check file existence with g_file_test().
* qmi-firmware-update: remove explicit GDestroyNotify cast on g_free / ↵Ben Chan2017-03-295-9/+9
| | | | | | | | g_object_unref g_free and g_object_unref are in form of `void (*)(gpointer)`, which matches the GDestroyNotify signature. An explicit GDestroyNotify cast on g_free and g_object_unref is thus not needed.
* libqmi-lib: remove explicit GDestroyNotify cast on g_free / g_object_unrefBen Chan2017-03-291-1/+1
| | | | | | g_free and g_object_unref are in form of `void (*)(gpointer)`, which matches the GDestroyNotify signature. An explicit GDestroyNotify cast on g_free and g_object_unref is thus not needed.
* build: post release version bump to 1.19.0Aleksander Morgado2017-03-221-1/+1
|
* release: bump version to 1.18.0Aleksander Morgado2017-03-221-4/+4
|
* NEWS: update for 1.18.0Aleksander Morgado2017-03-221-0/+142
|
* AUTHORS: updateAleksander Morgado2017-03-221-8/+16
| | | | Based on git stats: git shortlog -s -n --all --no-merges
* docs,man: generate man page for qmi-firmware-updateAleksander Morgado2017-03-222-2/+18
|
* qmicli,wds: only need to initialize enum member fields in structAleksander Morgado2017-03-221-8/+3
| | | | | | | | When doing member initializations when the struct variable is declared, only initialize the enum fields to valid enum values, the remaining fields will be initialized to zero. This is a different approach to the fix done in 4c678418.
* README: add note about licensing of qmi-firmware-updateAleksander Morgado2017-03-181-1/+2
|
* build: skip building qmi-firmware-update if requested to do soAleksander Morgado2017-03-031-1/+5
|
* docs: improve QMI_CHECK_VERSION documentationAleksander Morgado2017-03-011-0/+2
|
* docs: fix QMI_PROXY_N_CLIENTS documentationAleksander Morgado2017-03-011-1/+1
|
* docs: fix QmiProxy:qmi-proxy-n-clients documentationAleksander Morgado2017-03-011-1/+1
|
* docs: fix qmi_wds_data_system_get_string() documentationAleksander Morgado2017-03-011-1/+1
|
* docs: add missing 'WDS Bind MUX data port' documentationAleksander Morgado2017-03-011-0/+1
|
* libqmi-glib: fix enum nicknames with '3gpp' on itAleksander Morgado2017-03-013-11/+12
|
* docs: fix QMI_WDS_CDMA_CAUSE_CODE_GENERAL_SMS_NOT_SUPPORTED docsAleksander Morgado2017-03-011-2/+2
|
* docs: add missing documentation fo QmiWdsClientTypeAleksander Morgado2017-02-281-0/+5
|
* docs: add missing documentation for QmiDataEndpointTypeAleksander Morgado2017-02-281-0/+5
|
* wds: added WDS Bind Mux Data Port messageCarlo Lobrano2017-02-284-1/+213
| | | | | | | | | | | | | | This message is used to bind a muxed data port to a controller device. The Muxed data port has to be managed by qmi_wwan driver. The Muxed data port is identified by: - mux_id: the numeric ID given to qmi_wwan once created - interface number: the interface number of the qmi controller device on the modem Once the binding is completed, all the commands sent (and I expect also received, but I could not test it) using the same Client ID are for the binded data port instead of the real one.
* wda: extended wda set format message to enable QMUXCarlo Lobrano2017-02-285-13/+304
| | | | | | | | | | | | | | | | | | | | | | Added the following configurable values: - upload datagram protocol - download datagram protocol - download datagram max size - download max datagrams - endpoint type - endpoint interface number According to last GobiNet from CodeAura project, it is necessary to set the following values to enable multiple data connection through one controller device: - upload datagram protocol = QMAP - download datagram protocol = QMAP - download datagram max size = 32 (it seems working even without setting it) - download max datagrams = 32768 (it seems working even without setting it) - endpoint type = HSUSB (it seems working even without setting it) - endpoint interface number = this depends on the modem, but it seems working even without setting it
* libqmi-glib,errors: Fix 'INVALID_TRANSITION' nicknameAleksander Morgado2017-02-281-1/+1
|
* build: bump version to 1.17.901Aleksander Morgado2017-02-231-1/+1
|
* build: mm-runtime-check is an optional feature not an optional packageAleksander Morgado2017-02-234-11/+11
|
* docs: add missing references to Operator Name messagesAleksander Morgado2017-02-232-0/+22
|
* qmi-firmware-update: new optional runtime check to see if MM runningAleksander Morgado2017-02-234-15/+129
| | | | | Enabled by default, may be disabled using --without-mm-runtime-check during configure.
* qmicli,helpers: make sure flags are reset before parsing the stringAleksander Morgado2017-02-151-0/+4
| | | | | | | We OR each flag value found in the output directly, so make sure that output is clear before adding any new flag. Reported-by: Paul Gildea <gildeap@tcd.ie>
* qmicli: add support for --nas-get-operator-nameDan Williams2017-02-144-1/+418
|
* nas: add Get Operator Name and Operator Name indicationDan Williams2017-02-143-1/+219
|
* qmi-firmware-update: fix multiline command backslashes in --help-examplesAleksander Morgado2017-02-141-3/+3
|
* qmi-firmware-update: fix 9x20 typo in --help-examples outputAleksander Morgado2017-02-141-2/+2
|
* qmi-firmware-update: fix build when udev support includedAleksander Morgado2017-02-131-0/+2
|
* libqmi-glib,wds: add missing 'Returns' in method docAleksander Morgado2017-02-131-0/+2
|
* qmi-firmware-update: allow building without udevAleksander Morgado2017-02-1311-119/+297
| | | | | | We allow running FW updates even when udev isn't available in the system. In this case, though, only the manual operations will be supported (i.e. --reset and --update-qdl).
* qmi-firmware-update: improve examplesAleksander Morgado2017-02-131-66/+103
| | | | Added example of how to manually update 9x15 and 9x30 devices.
* qmicli,uim: split SIM power on/off operations in two separate actionsAleksander Morgado2017-02-131-54/+61
| | | | | The actions map to different QMI messages, and we try to keep one action per QMI message.
* docs,uim: add missing links for 'UIM Power Off/On' requestsAleksander Morgado2017-02-131-0/+2
|
* uim: added SIM power on/off functionalityKasper Holtze2017-02-132-1/+191
|
* qmi-firmware-update: plug memleakAleksander Morgado2017-02-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ==14200== 308 (208 direct, 100 indirect) bytes in 1 blocks are definitely lost in loss record 1,163 of 1,191 ==14200== at 0x4C2AB8D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==14200== by 0x5D34B98: g_malloc (in /usr/lib/libglib-2.0.so.0.5000.2) ==14200== by 0x5D4D0D2: g_slice_alloc (in /usr/lib/libglib-2.0.so.0.5000.2) ==14200== by 0x5D4D6FD: g_slice_alloc0 (in /usr/lib/libglib-2.0.so.0.5000.2) ==14200== by 0x5AC62B3: g_type_create_instance (in /usr/lib/libgobject-2.0.so.0.5000.2) ==14200== by 0x5AA81FA: ??? (in /usr/lib/libgobject-2.0.so.0.5000.2) ==14200== by 0x5AA9C0C: g_object_newv (in /usr/lib/libgobject-2.0.so.0.5000.2) ==14200== by 0x5AAA3C3: g_object_new (in /usr/lib/libgobject-2.0.so.0.5000.2) ==14200== by 0x5789694: g_task_new (in /usr/lib/libgio-2.0.so.0.5000.2) ==14200== by 0x40D2E1: qfu_udev_helper_wait_for_device (qfu-udev-helpers.c:580) ==14200== by 0x40753D: qfu_device_selection_wait_for_tty (qfu-device-selection.c:211) ==14200== by 0x40A380: run_context_step_wait_for_tty (qfu-updater.c:798) ==14200== ==14200== 308 (208 direct, 100 indirect) bytes in 1 blocks are definitely lost in loss record 1,164 of 1,191 ==14200== at 0x4C2AB8D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==14200== by 0x5D34B98: g_malloc (in /usr/lib/libglib-2.0.so.0.5000.2) ==14200== by 0x5D4D0D2: g_slice_alloc (in /usr/lib/libglib-2.0.so.0.5000.2) ==14200== by 0x5D4D6FD: g_slice_alloc0 (in /usr/lib/libglib-2.0.so.0.5000.2) ==14200== by 0x5AC62B3: g_type_create_instance (in /usr/lib/libgobject-2.0.so.0.5000.2) ==14200== by 0x5AA81FA: ??? (in /usr/lib/libgobject-2.0.so.0.5000.2) ==14200== by 0x5AA9C0C: g_object_newv (in /usr/lib/libgobject-2.0.so.0.5000.2) ==14200== by 0x5AAA3C3: g_object_new (in /usr/lib/libgobject-2.0.so.0.5000.2) ==14200== by 0x5789694: g_task_new (in /usr/lib/libgio-2.0.so.0.5000.2) ==14200== by 0x40D2E1: qfu_udev_helper_wait_for_device (qfu-udev-helpers.c:580) ==14200== by 0x4074DD: qfu_device_selection_wait_for_cdc_wdm (qfu-device-selection.c:195) ==14200== by 0x409977: run_context_step_wait_for_cdc_wdm (qfu-updater.c:579)
* qmi-firmware-update: plug memleakAleksander Morgado2017-02-101-1/+1
| | | | | | | | | | | | ==14200== 52 bytes in 1 blocks are definitely lost in loss record 792 of 1,191 ==14200== at 0x4C2AB8D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==14200== by 0x5D34B98: g_malloc (in /usr/lib/libglib-2.0.so.0.5000.2) ==14200== by 0x5D4EC3E: g_strdup (in /usr/lib/libglib-2.0.so.0.5000.2) ==14200== by 0x40C16D: udev_helper_get_udev_device_details (qfu-udev-helpers.c:94) ==14200== by 0x40C72C: udev_helper_find_by_device_info_in_subsystem (qfu-udev-helpers.c:263) ==14200== by 0x40C978: qfu_udev_helper_find_by_device_info (qfu-udev-helpers.c:314) ==14200== by 0x4076A9: qfu_device_selection_new (qfu-device-selection.c:264) ==14200== by 0x406A99: main (qfu-main.c:559)