Andrew Bird 2db79a8b54 api: add new LTE constant to the MM_ACCESS_TECHs
The 10.4 version of TS27.007 extends the range of values possible from AT+COPS?
The range of values are as follows:
3GPP TS 27.007 V10.4.0, +COPS
<AcT>: integer type; access technology selected
0       GSM
1       GSM Compact
2       UTRAN
3       GSM w/EGPRS
4       UTRAN w/HSDPA
5       UTRAN w/HSUPA
6       UTRAN w/HSDPA and HSUPA
7       E-UTRAN

All but the LTE (E-UTRAN) value can be represented in MM 0.5, this patch adds a
new constant to correct that, until the MM API is redesigned later for 0.6.

Signed-off-by: Andrew Bird <ajb@spheresystems.co.uk>
2011-07-29 16:56:10 -05:00
2008-07-31 17:14:50 +03:00
2010-01-27 15:48:55 -08:00
2011-07-27 21:38:31 -05:00
2010-02-19 18:23:19 -08:00
2011-07-25 01:18:22 -05:00
2008-07-31 09:43:00 +03:00
2008-07-31 09:43:00 +03:00
2009-02-06 13:32:45 +02:00

ModemManager.
The problem ModemManager tries to solve is to provide a unified high level API
for communicating with (mobile broadband) modems. While the basic commands are
standardized, the more advanced operations (like signal quality monitoring 
while connected) varies a lot.

Using.
ModemManager is a system daemon and is not meant to be used directly from
the command line. However, since it provides DBus API, it is possible to use
'dbus-send' command to control it from the terminal. There's an example
program (tests/mm-test.py) that demonstrates the basic API usage.

Implementation.
ModemManager is a DBus system bus activated service (meaning it's started 
automatically when a request arrives). It is written in C. The devices are
queried from HAL and automatically updated based on hardware events. There's
a GInterface (MMModem) that defines the modem interface and any device specific
implementation must implement it. There are two generic MMModem implementations
to support the basic operations (one for GSM, one for CDMA,) which are common
for all cards.

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 HAL UDI and to create custom MMModem 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's a
fully working plugin in the plugins/ directory for Huawei cards that can be
used as an example for writing new plugins. Writing new plugins is highly
encouraged!

API.
The 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!
Languages
C 98.6%
Meson 0.8%
Python 0.4%
Shell 0.1%