aboutsummaryrefslogtreecommitdiff
path: root/plugins/mm-modem-option-utils.c
AgeCommit message (Collapse)Author
2012-03-16hso,option: plugins fully portedAleksander Morgado
2012-02-28core: rework port grabbing and organizationDan Williams
Make port roles more flexible. We have modems that do PPP on interfaces other than the primary interface, and that wasn't possible with the old code. So clean up all that logic and move the port organization code into the core so we can reduce code in the plugins. In the new world order, the plugins say whether the port is a QCDM port, an AT port, or ignored. If it's an AT port the plugins get to tag it as primary, secondary, or PPP, or any combination of the 3. This allows for modems where PPP should really be done on the secondary port (Huawei E220, Sierra devices) so that the primary port stays open for command and status. Modem subclasses no longer get asked to handle port grabbing themselves. Instead, that's now done by the generic classes (MMGenericCdma and MMGenericGsm) and the plugins are notified when a port is grabbed so they can add unsolicited response handlers for it. After all ports are grabbed by the generic classes, they get "organized", which assigns various ports to the roles of PRIMARY, SECONDARY, DATA, and QCDM based on specific rules and hints that the plugin provided (which are expressed as MMAtPortFlags). The plugins then have a chance to perform fixups on the primary port if they choose. The plugin code is responsible for determining the port hints (ie MMAtPortFlags) at probe time, instead of having a combination of the plugin and the modem class do the job. This simplifies things greatly for the plugins at the expense of more complicated logic in the core.
2011-07-25option/hso: check generic access tech first, then specific techDan Williams
During the explicit access technology check, the plugin would request specific 2G (OCTI) and 3G (OWCTI) technologies explicitly. Some devices (like Nozomi) don't support the AT_OWCTI command, which leaves us with only AT_OSSYS for determining whether the device is registered with the 3G network or the 2G network. So like the unsolicited mode change handling code, when requesting access technology explicitly, ask for generic 2G/3G tech first, and then get the specific tech. If the device doesn't support explicit 3G tech then at least we have the generic 3G tech from OSSYS to use.
2011-06-05core, plugins: if modem removed don't process responseAleksander Morgado
We try to avoid a memory leak when info->error is reset, as well as a second re-schedule of the info.
2010-03-26option/hso: implement solicited access technology requestDan Williams
2010-03-22option/hso: ensure unsolicited messages get turned off on disableDan Williams
2010-03-22option/hso: make use of unsolicited access technology signalsDan Williams
2010-03-16option: generalize common Option/HSO mode and unsolicited response handlingDan Williams