Aleksander Morgado
0082587915
The first argument in the GCallback is actually the GCancellable. 0x00005cf40027c2d3 (ModemManager - mm-bearer-mbim.c: 643) ip_configuration_async_cleanup 0x00005cf40027bfb9 (ModemManager - mm-bearer-mbim.c: 671) ip_configuration_async_cancelled 0x00007feda3a6fb33 (libgobject-2.0.so.0 - gclosure.c: 895) _g_closure_invoke_va 0x00007feda3a87da1 (libgobject-2.0.so.0 - gsignal.c: 3472) g_signal_emit_valist 0x00007feda3a88811 (libgobject-2.0.so.0 - gsignal.c: 3622) g_signal_emit 0x00007feda3b0f98d (libgio-2.0.so.0 - gcancellable.c: 519) g_cancellable_cancel 0x00005cf4001dd8fa (ModemManager - mm-base-bearer.c) modem_3gpp_registration_state_changed 0x00007feda3a6f8d2 (libgobject-2.0.so.0 - gclosure.c: 832) g_closure_invoke 0x00007feda3a8728a (libgobject-2.0.so.0 - gsignal.c: 3812) signal_emit_unlocked_R 0x00007feda3a883d4 (libgobject-2.0.so.0 - gsignal.c: 3565) g_signal_emit_valist 0x00007feda3a88811 (libgobject-2.0.so.0 - gsignal.c: 3622) g_signal_emit 0x00007feda3a7aac2 (libgobject-2.0.so.0 - gobject.c: 1428) g_object_dispatch_properties_changed 0x00007feda3a757b8 (libgobject-2.0.so.0 - gobject.c: 359) g_object_notify_queue_thaw 0x00007feda3a773a9 (libgobject-2.0.so.0 - gobject.c: 2793) g_object_set_valist 0x00007feda3a77db8 (libgobject-2.0.so.0 - gobject.c: 2957) g_object_set 0x00005cf40021492a (ModemManager - mm-iface-modem-3gpp.c: 2347) update_non_registered_state Signed-off-by: Aleksander Morgado <aleksandermj@google.com>
ModemManager
ModemManager provides a unified high level API for communicating with mobile broadband modems, regardless of the protocol used to communicate with the actual device (Generic AT, vendor-specific AT, QCDM, QMI, MBIM...).
Getting Started
ModemManager uses the meson build system. Meson is likely available as a package from your Linux distribution, but if not please refer to the Meson project for installation instructions. Once you have Meson installed you'll probably want to install libmbim and libqmi which most modems require.
After dependencies are installed you can build ModemManager with:
$ meson setup build --prefix=/usr --buildtype=release
$ ninja -C build
And after a successful build, install with:
$ sudo ninja -C build install
Using
ModemManager is a system daemon and is not meant to be used directly from the command line. However, since it provides a DBus API, it is possible to use 'dbus-send' commands or the new 'mmcli' command line interface to control it from the terminal. The devices are queried from udev and automatically updated based on hardware events, although a manual re-scan can also be requested to look for RS232 modems.
Implementation
ModemManager is a DBus system bus activated service (meaning it's started automatically when a request arrives). It is written in C, using glib and gio. Several GInterfaces specify different features that the modems support, including the generic MMIfaceModem3gpp and MMIfaceModemCdma which provide basic operations for 3GPP (GSM, UMTS, LTE) or CDMA (CDMA1x, EV-DO) modems. If a given feature is not available in the modem, the specific interface will not be exported in DBus.
Plugins
Plugins are loaded on startup, and must implement the MMPlugin interface. It consists of a couple of methods which tell the daemon whether the plugin supports a port and to create custom MMBroadbandModem implementations. It most likely makes sense to derive custom modem implementations from one of the generic classes and just add (or override) operations which are not standard. There are multiple fully working plugins in the plugins/ directory that can be used as an example for writing new plugins. Writing new plugins is highly encouraged! The plugin API is open for changes, so if you're writing a plugin and need to add or change some public method, feel free to suggest it!
License
The ModemManager and mmcli binaries are both GPLv2+ (See COPYING). The libmm-glib library and the ModemManager API headers are LGPLv2+ (See COPYING.LIB).
Code of Conduct
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms, which you can find in the following link: https://www.freedesktop.org/wiki/CodeOfConduct
CoC issues may be raised to the project maintainers at the following address: modemmanager-devel-owner@lists.freedesktop.org