Age | Commit message (Collapse) | Author | |
---|---|---|---|
2012-03-15 | core: new MMBroadbandModem object, inherits from MMBaseModem | Aleksander Morgado | |
New object to implement broadband modem specific behaviour. | |||
2012-03-15 | iface-modem: allow requesting signal quality check | Aleksander Morgado | |
The new `mm_iface_modem_signal_quality_check()' method will reload the signal quality value on demand, set the value of the `SignalQuality' property in DBus, and also return the results. | |||
2012-03-15 | iface-modem: handle SetAllowedModes() | Aleksander Morgado | |
2012-03-15 | iface-modem: handle SetAllowedBands() | Aleksander Morgado | |
Also considering that playing with bands may not be supported. | |||
2012-03-15 | iface-modem: handle FactoryReset() calls | Aleksander Morgado | |
Also considering that reseting may not be implemented. | |||
2012-03-15 | iface-modem: handle Reset() calls | Aleksander Morgado | |
Also considering that reseting may not be implemented. | |||
2012-03-15 | iface-modem: create MMSim object during init | Aleksander Morgado | |
2012-03-15 | sim: handle SendPin() and SendPuk() calls | Aleksander Morgado | |
2012-03-15 | sim: handle EnablePin() calls | Aleksander Morgado | |
2012-03-15 | sim: handle ChangePin() calls | Aleksander Morgado | |
2012-03-15 | sim: allow re-launching initialization | Aleksander Morgado | |
It may happen that we cannot load property values when the SIM is locked, so we need to enable re-launching initialization in the object API. | |||
2012-03-15 | sim: load OperatorName during init | Aleksander Morgado | |
2012-03-15 | sim: load OperatorIdentifier during init | Aleksander Morgado | |
2012-03-15 | sim: load IMSI during init | Aleksander Morgado | |
2012-03-15 | sim: load SIM Identifier during init | Aleksander Morgado | |
2012-03-15 | core: new MMSim object, inherits from MmGdbusSim | Aleksander Morgado | |
2012-03-15 | iface-modem: relaunch init when being unlocked | Aleksander Morgado | |
2012-03-15 | iface-modem: new `State' property, bound to the one in the MmGDbusModem skeleton | Aleksander Morgado | |
2012-03-15 | iface-modem: load `SupportedModes' and `SupportedBands' during init | Aleksander Morgado | |
2012-03-15 | iface-modem: load `UnlockRequired' and `UnlockRetries' during init | Aleksander Morgado | |
And also allow being loaded upon user request, with `mm_iface_modem_unlock_check()'. | |||
2012-03-15 | iface-modem: load `EquipmentIdentifier' and `DeviceIdentifier' during init | Aleksander Morgado | |
2012-03-15 | iface-modem: load `Manufacturer', `Model' and `Revision' during init | Aleksander Morgado | |
2012-03-15 | iface-modem: load `MaxBearers' and `MaxActiveBearers' during init | Aleksander Morgado | |
2012-03-15 | iface-modem: load `ModemCapabilities' and `CurrentCapabilities' during init | Aleksander Morgado | |
When the interface gets initialized, start loading modem and current capabilities. | |||
2012-03-15 | iface-modem: set `Device', `Driver' and `Plugin' during init | Aleksander Morgado | |
Values taken from the MMBaseModem object, which are not expected to change during the lifetime of the Modem object. | |||
2012-03-15 | core: new MMIfaceModem interface | Aleksander Morgado | |
This interface controls the availability of the DBus Modem interface, and implements the actions that may be performed in the interface. | |||
2012-03-15 | base-modem: new `enable()' and `disable()' async methods | Aleksander Morgado | |
Users will be able to enable or disable modems using the DBus interface. We will chain up the `Enable(boolean)' call from the DBus interface to these new methods in the base modem class. | |||
2012-03-15 | base-modem: new virtual initialize() method | Aleksander Morgado | |
Whenever the first AT port is grabbed, we launch the initialize() method, which must have been implemented by the corresponding modem subclass. | |||
2012-03-15 | base-modem: new property to keep the Connection object | Aleksander Morgado | |
2012-03-15 | base-modem: new properties for vendor and product IDs | Aleksander Morgado | |
These will be set during modem object creation. | |||
2012-03-15 | base-modem: getters for primary/secondary/qcdm ports | Aleksander Morgado | |
2012-03-15 | base-modem: set v1 serial parser always | Aleksander Morgado | |
CDMA modems used to use the v1_e1 serial parser; but we'll try to setup a common one in all modems. | |||
2012-03-15 | base-modem: new properties to handle Device, Driver and Plugin | Aleksander Morgado | |
They will be set when constructing the object. | |||
2012-03-15 | base-modem: ported all port grabbing/releasing logic to the base object | Aleksander Morgado | |
2012-03-15 | base-modem: expect a GDBusMethodInvocation as context of the auth request | Aleksander Morgado | |
2012-03-15 | core: new MMBaseModem abstract type | Aleksander Morgado | |
Basically, a replacement of the MMModemBase type, being prepared to handle multimode devices. This object derives from a MmGdbusObjectSkeleton, which makes it suitable to be controlled within the GDBusObjectManagerServer. | |||
2012-03-15 | core: new AT command and sequence processors | Aleksander Morgado | |
This setup, allows: - Running a single command and processing its result. - Running a set of N commands, providing a global result after all have been executed. - Running a set of N commands out of M (N<M), where the global result is obtained without having executed all configured commands. This is useful when probing, for example. | |||
2012-03-15 | manager: make it export the Object Manager interface | Aleksander Morgado | |
2012-03-15 | manager: let it be initable | Aleksander Morgado | |
The MMManager object creation may fail due to environment reasons (i.e. no plugins found, or problems exporting DBus interfaces), so we can use the initable interface to properly handle those situations. | |||
2012-03-15 | manager: keep the GDBus connection reference in a 'connection' property | Aleksander Morgado | |
2012-03-15 | manager: use G_TYPE_INSTANCE_GET_PRIVATE() just to create the private struct | Aleksander Morgado | |
A new 'priv' pointer is added in the MMManager struct, which will contain the address of the private structure. | |||
2012-03-15 | core: implement the Manager1 DBus interface, based on GDBus | Aleksander Morgado | |
The MMManager object now derives from the gdbus-codegen-generated MmGdbusOrgFreedesktopModemManager1Skeleton object, and implements the handlers for the SetLogging() and ScanDevices() DBus methods. The main program is also modified to be based on GDBus. | |||
2012-03-15 | plugin-base: properly handle Core errors | Aleksander Morgado | |
2012-03-15 | plugin-base: clear internally tracked probe if port unsupported | Aleksander Morgado | |
If the port is supported by the plugin, leave the probe in the internal HT until the port gets grabbed afterwards. | |||
2012-03-15 | manager: clear cached port probe when device is removed | Aleksander Morgado | |
2012-03-15 | plugin-base: remove `MM_PLUGIN_SUPPORTS_PORT_IN_PROGRESS' status | Aleksander Morgado | |
Support checks are fully asynchronous and result is always reported when the check is considered ready, so in-progress replies to `mm_plugin_supports_port_finish()' don't make any sense. | |||
2012-03-15 | plugin-base: don't report numeric support level in the [0-100] range | Aleksander Morgado | |
There is no single case where more than one plugin may end up wanting to support a given port, and therefore there is no need to report the numeric support level when reporting SUPPORTED. | |||
2012-03-15 | plugin-base: avoid trying to probe 'net' devices | Aleksander Morgado | |
Some devices support 'net' devices, which cannot be AT or QCDM probed. If the port being checked for support corresponds to an already existing modem, the port will be reported as SUPPORTED. If this is the first port of the modem being checked for support, we will just DEFER the support check until we get a modem created. | |||
2012-03-15 | plugin-base: keep a MMPluginSupportsResult in the async result | Aleksander Morgado | |
Instead of just a boolean, provide a MMPluginSupportsResult, so that we can pass it as is during `supports_port_finish()'. | |||
2012-03-15 | plugin-base: improve the logic to check whether vendor or product probing needed | Aleksander Morgado | |
If the plugin does a Vendor ID check and it passes, it doesn't need Vendor string probing. If the plugin does a Vendor ID check and it fails: - If Vendor strings reported, it needs Vendor probing. - If Vendor strings not reported, fail as unsupported. If the plugin does a Product ID check and it passes, it doesn't need Product string probing. If the plugin does a Product ID check and it fails: - If Product strings reported, it needs Product probing. - If Product strings not reported, fail as unsupported. |