| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Causes a crash on Android.
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
|
|
|
|
| |
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
|
|
|
|
|
|
|
| |
Some standard C libraries like Android's Bionic don't support
canonicalize_file_name().
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
|
|
|
|
|
|
|
|
|
| |
If e.g. qmi-proxy is started by ModemManager and we send a Ctrl+C to
it, the signal would be propagated to the qmi-proxy process and we
would kill it right away, while leaving ModemManager still around
wondering why the socket to the proxy got a HUP.
Avoid this, by making sure the qmi-proxy gets its own process group.
|
| |
|
|
|
|
|
|
|
|
| |
Commit c96725e7e "libqmi-glib: fix G_DEPRECATED_FOR annotations"
replaced macro defintions with `static const int' definitions for those
deprecated enumerators. However, gtk-doc doesn't seem to document
`static const int' defintions. This patch works around the issue by
adding a macro defintion on top of a `static const int' defintion.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
qmi-compat.h defines a few deprecated enumerators as an alias to their
equivalence using macros and annotates those macros with
G_DEPRECATED_FOR, which may be expanded to
`__attribute__((deprecated))'.
Neither gcc nor clang supports `__attribute__((deprecated))' on macros.
Thus, a G_DEPRECATED_FOR annotation before a macro definition is
actually associated with the next identifier found after the macro
definition, which is incorrect.
Alternatively, the G_DEPRECATED_FOR annotation can be used on the
deprecated enumerators. But only gcc 6 or above supports enumerator
attributes.
To address the issue, this patch defines the deprecated enumerators as
`static const int' values, which can then be annotated with
G_DEPRECATED_FOR.
|
|
|
|
| |
Reports bogus current TX/RX rates on my Huawei E397 though.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The GetStoredImageResult must exist before getting into the array item
loop, so that we fill the contents of the struct when we find the
images (modem and pri) we were looking for.
This also fixes the build when -Werror=maybe-uninitialized is used:
/var/lib/jenkins/workspace/libqmi/master-without-mbim/source/src/qmicli/qmicli-dms.c:2800:5: error: ‘result’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
g_task_return_pointer (task, result, (GDestroyNotify)get_stored_image_result_free);
^
|
|
|
|
|
|
| |
The updated code also avoids a potential memory leak of
GetStoredImageContext in get_stored_image_list_stored_images_ready when
the operation fails.
|
|
|
|
|
|
|
| |
Add qmicli --wds-set-ip-family command as suggested by Aleksander Morgado
to enable proper dual stack support.
Signed-off-by: Reinhard Speyerer <rspmn@arcor.de>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
canonicalize_file_name() returns NULL if file doesn't exist,
so no need to check file existence with g_file_test().
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
Based on git stats: git shortlog -s -n --all --no-merges
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Enabled by default, may be disabled using --without-mm-runtime-check
during configure.
|
|
|
|
|
|
|
| |
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>
|