Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
Configuring unsolicited events involves:
* Setup unsolicited events. This handles the setup of the unsolicited message
handlers in the AT ports, including the setup of the callback to get called
when the unsolicited messages are received.
* Enable unsolicited events. This tells the modem to actually send the
unsolicited messages.
* Disable unsolicited events. This tells the modem to stop sending unsolicited
messages.
* Cleanup unsolicited events. This removes the unsolicited message handlers
in the AT ports.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Plugins can subclass the MMSim object and provide custom implementations of the
actions performed by the object.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Just rely on a single Bearer object created.
|
|
|
|
|
|
|
|
Each enum will have its own #_get_string (),
and each flags will have its own #_build_string_from_mask ().
|
|
|
|
|
|
|
|
|
|
Currently, only LAC/CI if the modem has 3GPP capabilities.
|
|
|
|
|
|
|
|
Seems like an unnecessary complication, as the client anyway needs to handle
asynchronously reported errors.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* assume CDMA1x is 2G
* consider CS/PS/CDMA1x/EVDO network support flags specified by the plugins
|