Ben Chan
3342739798
If PIN1 is disabled and we have tried to enable it with a wrong PIN, a MBIM modem would have indicated the number of remaining attempts for PIN1 (unless PUK1 is engaged) in the response to the failed MBIM_CID_PIN set operation. However, a MBIM_CID_PIN query may be issued (e.g. MMBaseSim calls mm_iface_modem_update_lock_info()) after the MBIM_CID_PIN set operation to query the number of remaining attempts for a PIN type. Unfortunately, we can't specify a particular PIN type in a MBIM_CID_PIN query. The modem may not reply with information about PIN1 if PIN1 is disabled. When that happens, we would like to preserve our knowledge about the number of remaining attempts for PIN1. This patch modifies MMBroadbandModemMbim's load_unlock_retries() operation to carry over any previously observed information on PIN1 if the MBIM_CID_PIN query reports something other than PIN1.
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...). 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 provice 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+. The libmm-glib library is LGPLv2+.