aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2013-06-18test: remove testers of the old interfaceAleksander Morgado
Old python tests using the old ModemManager interface are removed, as mmcli provides already a much nicer way to test the DBus interface. Also, mm-test.py and the PPPD plugin get removed, which were also using the old interface, and which were not very useful for testing newer non-PPP based modems. https://bugzilla.gnome.org/show_bug.cgi?id=702061
2013-06-18api,introspection: avoid exposing the Contacts interfaceAleksander Morgado
There is no implementation of the Contacts interface yet, just avoid exposing it for now. https://bugzilla.gnome.org/show_bug.cgi?id=701989
2013-06-17bearer-mbim: make packet service attach operation optionalAleksander Morgado
Some modems do require it, but some others won't (e.g. CDMA based ones), so just make the operation optional, but only if the modem replies NoDeviceSupport. https://bugzilla.gnome.org/show_bug.cgi?id=702419
2013-06-17bearer: MMBearerIpFamily is flags, not enumAleksander Morgado
Fixes the following warning... [mm-broadband-modem-mbim.c:1133] modem_create_bearer(): Creating MBIM bearer in MBIM modem GLib-GObject-CRITICAL **: g_param_spec_enum: assertion `G_TYPE_IS_ENUM (enum_type)' failed GLib-GObject-CRITICAL **: g_object_class_install_property: assertion `G_IS_PARAM_SPEC (pspec)' failed
2013-06-15broadband-modem-qmi: fallback to AT if WMS service not available for messagingAleksander Morgado
It is quite common to have modems handled with QMI but with very limited services implemented, e.g. without WMS: [/dev/cdc-wdm0] QMI Device supports 5 services: [/dev/cdc-wdm0] ctl (1.3) [/dev/cdc-wdm0] wds (1.5) [/dev/cdc-wdm0] dms (1.2) [/dev/cdc-wdm0] nas (1.0) [/dev/cdc-wdm0] cat (0.0) We'll now fallback to use plain AT commands when no QMI WMS service is found.
2013-06-13docs: reorder version symbolsAleksander Morgado
2013-06-13api,header: fix MM_MINOR_VERSION definitionAleksander Morgado
2013-06-13build: use new mailing list as contact addressAleksander Morgado
2013-06-13build: setup libtool versioning for libmm-glibAleksander Morgado
We'll use it once we've released 0.8.
2013-06-13api,header: setup and export MM version symbols in the APIAleksander Morgado
2013-06-13build: new strict & permissive polkit policies in '--with-polkit'Aleksander Morgado
The '--with-polkit' configure switch now supports more options than just yes or no: * strict: Active user needs to explicitly authenticate when peforming an operation defined in the Device.Control, Messaging, Location or Contacts interfaces. Polkit policy is set to 'auth_self_keep'. * permissive: Active user doesn't need to explicitly authenticate when peforming an operation defined in the Device.Control, Messaging, Location or Contacts interfaces. Polkit policy is set to 'yes'. * none: don't use polkit. If '--with-polkit' is not given, usage will be automatically decided based on the presence of the Polkit headers in the system (if headers found, strict policy will be applied, otherwise none). Also: * '--with-polkit' is equivalent to '--with-polkit=strict' * '--with-polkit=yes' is equivalent to '--with-polkit=strict' * '--with-polkit=no' is equivalent to '--with-polkit=none' * '--without-polkit' is equivalent to '--with-polkit=none' By default, ModemManager will always apply the strict policy, in order to protect the user from unwanted operations in the modem (e.g. getting the PIN locked forever after wrong PIN/PUK unlock attempts). https://bugzilla.gnome.org/show_bug.cgi?id=701740
2013-06-12broadband-bearer-qmi: log both IPv4 and IPv6 settings for V4V6 connectionsDan Williams
Old code only printed one or the other; but if we have dual-stack connectivity, print everything we can read.
2013-06-12docs,api: new migration referenceAleksander Morgado
2013-06-12NEWS: update, add reference to MBIM devicesAleksander Morgado
2013-06-12AUTHORS: updateAleksander Morgado
2013-06-12README,docs: update basic ModemManager informationAleksander Morgado
2013-06-11api,introspection: update copyright noticesAleksander Morgado
2013-06-10manager: require whitelist for devices in the 'pnp' subsystemAleksander Morgado
2013-06-10build: distribute in .xz formatAleksander Morgado
Up to 30% size reduction: $ du -hs ModemManager-0.7.991.tar.* 1.6M ModemManager-0.7.991.tar.bz2 1.1M ModemManager-0.7.991.tar.xz
2013-06-07manager: handle PNP-connected devices tooDmitry Ivanyushin
I have a modem that is connected to motherboard's built-in serial port. Its parent is listed in udev as "pnp" so this patch handles that situation.
2013-06-07man,mmcli: fix minor typoAleksander Morgado
2013-06-06build: fix distcheckAleksander Morgado
2013-06-06systemd: simplify unit fileAleksander Morgado
Avoid setting up the Alias rule, which was a helper to let us 'disable' the systemd service including dbus-activations. Without the Alias, 'disable' will still let starting ModemManager through dbus-activation. If you really want to fully disallow starting MM also through dbus-activation, you should 'mask' and 'unmask' the service. E.g.: $ sudo systemctl mask ModemManager ln -s '/dev/null' '/etc/systemd/system/ModemManager.service' $ sudo mmcli -L error: couldn't find the ModemManager process in the bus $ sudo systemctl unmask ModemManager rm '/etc/systemd/system/ModemManager.service' $ sudo mmcli -L No modems were found https://bugzilla.gnome.org/show_bug.cgi?id=701229
2013-06-05release: bump version to 0.7.991Aleksander Morgado
Tagging to handle the new API updates, so that applications depending on the libmm-glib library can use the version number to check support.
2013-06-05broadband-modem: run *CNTI=2 to when loading supported modesAleksander Morgado
It sometimes provides a much better view of the supported modes than the WS46=? command, which is not always properly implemented. E.g.: Nokia N950: --------------- at+ws46=? (12) OK at*cnti=2 *CNTI: 2,GSM,GPRS,EDGE,UMTS,HSDPA,HSUPA OK Sierra AC313u --------------- at+ws46=? ERROR at*cnti=2 *CNTI: 2,GSM,GPRS,EDGE,UMTS,HSDPA/HSUPA,HSPA+,LTE OK
2013-06-05broadband-modem: don't set supported mode defaults based on guessesAleksander Morgado
We may be asking to load supported modes while in locked state, so the commands may fail. In order to re-load them properly once we're unlocked, we better just return an error instead of setting defaults.
2013-06-05huawei: default to IPv4 if no specific IP type to use given in NDISDUP modemsAleksander Morgado
2013-06-05api,introspection: Simple.Connect() won't change neither bands nor allowed modesAleksander Morgado
We won't allow changing modes or bands through Simple.Connect(). Applications should instead look at the corresponding SupportedBands or SupportedModes, and then use SetCurrentBands() or SetCurrentModes() explicitly.
2013-06-05iface-modem: allow changing capabilities in every stateAleksander Morgado
Same as done with the firmware switching, we allow capabilities changing even if the modem is in FAILED state, e.g. to switch from 3GPP to 3GPP2 mode.
2013-06-05iface-modem: load current modes and bands during initializationAleksander Morgado
We now load current modes and bands before enabling the modem, and we also allow mode and bands changes while the modem is disabled.
2013-06-05mmcli: new '--set-current-capabilities' commandAleksander Morgado
New command to allow changing modem capabilities, if supported. The modem will power cycle automatically after having changed them.
2013-06-05broadband-modem-qmi: update current capabilities loading logicAleksander Morgado
Changes being: * Don't rely on the band preference TLVs presence. The band preference TLVs are always given, even if the modem doesn't support the specific capability right away. E.g. a GSM/UMTS/LTE modem configured with 'gsm-umts' capability (no 'lte') still shows the LTE band preference TLV in the SSP responses. * Don't automatically add LTE as current capability. We needed this when we were not able to change capabilities, so that we didn't lose the ability to set 4G mode as allowed.
2013-06-05broadband-modem-qmi: implement capabilities settingAleksander Morgado
2013-06-05api,introspection: new 'SetCurrentCapabilities' methodAleksander Morgado
For those modems which expose a valid 'SupportedCapabilities' property with more than one item in the list, we'll allow switching between them.
2013-06-05api,introspection: rename 'ModemCapabilities' to 'SupportedCapabilities'Aleksander Morgado
And also make it a list of masks, specifying which are the specific combinations supported, not just one mask with all. E.g.: ------------------------- Hardware | manufacturer: 'Sierra Wireless, Incorporated' | model: 'MC7710' | revision: 'SWI9200X_03.05.19.04ap r5475 carmd-en-10527 2012/09/17 17:57:14' | supported: 'gsm-umts | gsm-umts, lte' | current: 'gsm-umts, lte' | equipment id: '358178040668164'
2013-06-05api,introspection: merge 'AllowedModes' and 'SupportedMode' into 'CurrentModes'Aleksander Morgado
We now have a single 'CurrentModes' property which contains both values in a tuple with signature "(uu)". Also, rename 'SetAllowedModes()' to 'SetCurrentModes()', and update the list of arguments expected to have a single "(uu)" tuple.
2013-06-05api,introspection: 'SupportedModes' is now a list of possible combinationsAleksander Morgado
Instead of just a mask of MMModemMode values, we now provide a list of the allowed and preferred mode combinations supported by the modem. E.g.: $> sudo mmcli -m 0 ------------------------- Modes | supported: 'allowed: 2g; preferred: none | allowed: 3g; preferred: none | allowed: 2g, 3g; preferred: none | allowed: 2g, 3g; preferred: 2g | allowed: 2g, 3g; preferred: 3g | allowed: 4g; preferred: none | allowed: 2g, 3g, 4g; preferred: none'
2013-06-05api,instrospection: rename 'Bands' to 'CurrentBands'Aleksander Morgado
... and 'SetBands()' to 'SetCurrentBands()'. We'll keep the 'Current' keyword in those properties which also have 'Supported' values.
2013-06-05broadband-modem-mbim: implement supported IP families loadingAleksander Morgado
2013-06-05broadband-modem-qmi: implement supported IP families loadingAleksander Morgado
We'll default to IPv4 if the modem is CDMA-only, and IPv4+IPv6 otherwise.
2013-06-05mmcli,modem: show supported IP families in modem infoAleksander Morgado
2013-06-05broadband-bearer: use the new CGDCONT=? test response parserAleksander Morgado
2013-06-05broadband-modem: implement default supported IP families loadingAleksander Morgado
For CDMA-only devices, we will default to IPv4. For 3GPP devices, we will use the AT+CGDCONT=? test command to query which are the supported PDP types.
2013-06-05modem-helpers: new CGDCONT=? test response parserAleksander Morgado
2013-06-05libmm-glib,modem: handle the new 'SupportedIpFamilies' propertyAleksander Morgado
2013-06-05api,introspection: new 'SupportedIpFamilies' propertyAleksander Morgado
This property will let the clients know which are the IP families supported by the modem.
2013-06-05modem-helpers: rename CGDCONT? testsAleksander Morgado
Adding the 'read' suffix, as they are for CGDCONT? read responses.
2013-06-05api: let MMBearerIpFamily be flags instead of a enumerationAleksander Morgado
We want to expose in the Modem interface the list of supported IP families, and the easiest way to do so is to have the IP family as flags, and provide in the interface a single enum. Also, a value of 0 for a MMBearerIpFamily specifies that no flags are set, so just rename it to 'NONE'. And add a new 'ANY' value which sets all flags to 1.
2013-06-05bearers: update connection logic in 3GPP+3GPP2 devicesAleksander Morgado
https://bugzilla.gnome.org/show_bug.cgi?id=701333
2013-05-31broadband-modem-mbm: *EPIN response often needs a lot of timeDan Williams
If the modem was locked, it'll delay responding until the SIM is ready, which can take a long time.
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2025-06-10 17:33:42 +0000