Age | Commit message (Collapse) | Author | |
---|---|---|---|
2012-03-15 | iface-modem-3gpp: handle network scan requests | Aleksander Morgado | |
2012-03-15 | modem-helpers: provide list of scanned networks in a list of structs | Aleksander Morgado | |
We provide the result of the +COPS=? parsing in a GList of MM3gppNetworkInfo structures. We avoid the previous hash table, or using a dictionary, as a list of structs with a predefined set of elements, which should be easier for plugins wanting to make their own version | |||
2012-03-15 | broadband-modem: implement Operator Code and Name loading | Aleksander Morgado | |
2012-03-15 | iface-modem-3gpp: when going into REGISTERED, load Operator Name and Code | Aleksander Morgado | |
2012-03-15 | iface-modem-3gpp: report registration state change in the log | Aleksander Morgado | |
2012-03-15 | broadband-modem: implement registration to 3GPP network | Aleksander Morgado | |
2012-03-15 | iface-modem-3gpp: always run CS and PS registration checks together | Aleksander Morgado | |
And report a single error, only if all available registration checks failed. | |||
2012-03-15 | iface-modem-3gpp: handle network registration requests | Aleksander Morgado | |
2012-03-15 | iface-modem: don't report LOCKED state if SIM PIN2/PUK2 | Aleksander Morgado | |
If unlock required reports needing SIM PIN2 or PUK2, don't report LOCKED state, as the device is fully operational without it. | |||
2012-03-15 | iface-modem: launch reinitialization only when going from LOCKED to DISABLED | Aleksander Morgado | |
2012-03-15 | broadband-modem: implement CS/PS registration checks | Aleksander Morgado | |
Running a CS/PS registration check may not return any direct result (this is, no MMModem3gppRegistrationStatus returned), as usually replies to +CREG? and +CGREG? are parsed as unsolicited messages. | |||
2012-03-15 | test-modem-helpers: fix C(G)REG parsing tests | Aleksander Morgado | |
2012-03-15 | modem-helpers: use MMModemAccessTech when parsing C(G)REG responses | Aleksander Morgado | |
2012-03-15 | iface-modem-3gpp: load registration states during enable | Aleksander Morgado | |
2012-03-15 | broadband-modem: implement unsolicited registration message setup | Aleksander Morgado | |
We setup custom handlers for unsolicited registration state messages. Plugins are allowed to setup their own handlers. | |||
2012-03-15 | iface-modem-3gpp: allow changing the RegistrationState from outside the ↵ | Aleksander Morgado | |
interface The 3GPP registration state will always be set from outside the 3GPP interface, for example when parsing unsolicited registration messages, on when the interface requests manual checking of registration state. We'll also update the State property in the Modem interface when we switch to a connected state, so we also set the Modem interface as a prerrequisite of the 3GPP interface. | |||
2012-03-15 | iface-modem: allow changing the State from outside the interface | Aleksander Morgado | |
Some states need to be set from outside the scope of the Modem interface, like Registration-related ones (REGISTERED, SEARCHING, ...) or Connection-related ones (CONNECTED, ...). | |||
2012-03-15 | broadband-modem: override the RegistrationState property | Aleksander Morgado | |
2012-03-15 | modem-helpers: use MMModem3gppRegistrationState when parsing C(G)REG responses | Aleksander Morgado | |
2012-03-15 | base-modem: setup NULL callbacks in unsolicited CREG message handlers | Aleksander Morgado | |
When the port is grabbed, we setup NULL callbacks for all unsolicited registration message handlers. If we do enable 3GPP registrations afterwards, we'll set proper callbacks. | |||
2012-03-15 | iface-modem: new RegistrationState property, bound to the one in DBus | Aleksander Morgado | |
2012-03-15 | iface-modem-3gpp: setup unsolicited registration messages handling during enable | Aleksander Morgado | |
2012-03-15 | at-serial-port: allow overwriting unsolicited message handlers | Aleksander Morgado | |
Existing unsolicited message handlers can be overwritten at any time now. This allows initializing the port with all possible message handlers configured with a NULL callback, and then setup the proper handlers when we go on enabling the different interfaces. | |||
2012-03-15 | broadband-modem: implement CS/PS registration notifications setup | Aleksander Morgado | |
2012-03-15 | iface-modem-3gpp: setup CS and PS registrations during enable | Aleksander Morgado | |
2012-03-15 | broadband-modem: setup enabling steps | Aleksander Morgado | |
When the modem is enabled, we'll go one by one enabling all our interfaces. | |||
2012-03-15 | iface-modem-3gpp: interface can be enabled | Aleksander Morgado | |
In addition to initializing the interface, to load initial values of all properties and export the object in DBus, the interface can now also be enabled. Enabling the 3GPP interface will take care of running the network registration process. | |||
2012-03-15 | broadband-modem: implement IMEI loading | Aleksander Morgado | |
2012-03-15 | broadband-modem: implement the Modem 3GPP interface | Aleksander Morgado | |
It will only be initialized and exported in DBus if the modem has 3GPP capabilities. | |||
2012-03-15 | iface-modem-3gpp: export DBus interface when properly initialized | Aleksander Morgado | |
2012-03-15 | iface-modem-3gpp: load `IMEI' during init | Aleksander Morgado | |
2012-03-15 | iface-modem-3gpp: setup interface initialization and shutdown | Aleksander Morgado | |
2012-03-15 | iface-modem: complete the result before freeing init context | Aleksander Morgado | |
2012-03-15 | iface-modem: avoid inner async operation during initialization | Aleksander Morgado | |
2012-03-15 | core: always pass open port to interface initializations | Aleksander Morgado | |
When the first AT port is grabbed, modem initialization is launched, using that specific port. This port is also passed to all interface initialization methods. | |||
2012-03-15 | iface-modem-3gpp: new interface to handle the Modem 3GPP DBus interface | Aleksander Morgado | |
2012-03-15 | iface-modem: simplify interface handling | Aleksander Morgado | |
Interfaces won't have a 'status', just initialize(), enable(), disable() and shutdown(). Also, shutdown() should never fail. We will take care of cancelling any ongoing operation afterwards, before calling shutdown(). | |||
2012-03-15 | broadband-modem: setup initialization of all interfaces | Aleksander Morgado | |
2012-03-15 | iface-modem: handle Enable() calls | Aleksander Morgado | |
2012-03-15 | broadband-modem: disable the Modem iface when disabling the modem | Aleksander Morgado | |
2012-03-15 | broadband-modem: enable the Modem iface when enabling the modem | Aleksander Morgado | |
2012-03-15 | broadband-modem: implement charset loading and setup | Aleksander Morgado | |
2012-03-15 | broadband-modem: implement flow control setup | Aleksander Morgado | |
2012-03-15 | broadband-modem: implement modem power-up commands | Aleksander Morgado | |
2012-03-15 | broadband-modem: implement modem initialization commands | Aleksander Morgado | |
2012-03-15 | broadband-modem: override the Current Capabilities property | Aleksander Morgado | |
2012-03-15 | iface-modem: close primary port during disable | Aleksander Morgado | |
2012-03-15 | iface-modem: send power-down command during disable | Aleksander Morgado | |
2012-03-15 | iface-modem: flash primary port during disable | Aleksander Morgado | |
2012-03-15 | iface-modem: interface can be disabled | Aleksander Morgado | |
The Modem interface can be disabled, going from enabled back to initialized. The disabling process will include closing the ports opened during the enabling. |