summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* fixup! huawei: consolidate command support checksaleksander/huawei-modesDan Williams2013-12-051-1/+2
|
* fixup! huawei: new ^PREFMODE=? test parserDan Williams2013-11-111-1/+1
| | | | | | | | | | Handle spaces when parsing, E168C replies with: <CR><LF>^PREFMODE: (2, 4, 8)<CR><LF><CR><LF>OK<CR><LF> Alternatively you could do this before calling mm_get_uint_from_str(): split[i] = g_strstrip (split[i]);
* huawei: handle empty response to AT^SYSCFG=?Aleksander Morgado2013-11-113-2/+52
| | | | | | Some Huawei modems (e.g. E220) may give an empty response for AT^SYSCFG=?, even if they do support the command. Handle this case by prividing a default fallback format string when this happens.
* huawei: new current mode setting based on the supported combinationsAleksander Morgado2013-11-111-111/+151
|
* huawei: new current mode loading based on the supported combinationsAleksander Morgado2013-11-111-153/+194
|
* huawei: new ^SYSCFGEX? response parserAleksander Morgado2013-11-113-0/+216
|
* huawei: new ^SYSCFG? response parserAleksander Morgado2013-11-113-0/+142
|
* huawei: new ^PREFMODE? response parserAleksander Morgado2013-11-113-0/+109
|
* huawei: load supported modes, not just assume themAleksander Morgado2013-11-111-48/+201
|
* huawei: consolidate command support checksAleksander Morgado2013-11-111-44/+32
|
* huawei: new ^SYSCFGEX=? test parserAleksander Morgado2013-11-113-0/+377
|
* huawei: new ^SYSCFG=? test parserAleksander Morgado2013-11-113-0/+462
|
* huawei: new ^PREFMODE=? test parserAleksander Morgado2013-11-103-0/+256
|
* huawei,tests: enable log traces in the testsAleksander Morgado2013-11-103-1/+31
|
* altair-lte: early fail connect/disconnect attempts when out of coveragePrathmesh Prabhu2013-11-081-3/+38
| | | | | | | | | | A firmware bug in Altair ALT3100 bricks the modem when - The modem is out of coverage (Registration state is unknown (CEREG: 4)) - A disconnect attempt is made using the AT%DPDNACT command. This patch prevents this situation by failing the connect/disconnect attempts in the altair plugin when registration state is unknown, without attempting to connect/disconnect the modem.
* bearer: notify final disconnect status using mm_bearer_report_connection_statusPrathmesh Prabhu2013-11-081-2/+12
| | | | | | | | | | Some MMBearer methods to disconnect the bearer assume that the bearer is disconnected even if the operation fails in a subclass. This leaves MMBearer and MMBroadbandBearer states out of sync. This patch notifies the bearer object of the final disconnection using mm_bearer_report_connection_status. This gives the subclasses a chance to update their state even when the disconnection attempt fails.
* modem-helpers: handle +CGDCONT=? replies with single contextAleksander Morgado2013-11-012-11/+25
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=708983
* tests: enable logging if 'ENABLE_TEST_MESSAGE_TRACES' is definedAleksander Morgado2013-11-013-0/+30
|
* x22x: handle QMI modemsAleksander Morgado2013-10-311-20/+38
| | | | | | With some bits and pieces developed by Dan Williams <dcbw@redhat.com> https://bugzilla.gnome.org/show_bug.cgi?id=710439
* altair-lte: fix LDFLAGS in the helper testsAleksander Morgado2013-10-311-1/+2
|
* huawei: clear only once the timeout to wait for the first interfaceAleksander Morgado2013-10-301-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As soon as we get a match between the current interface being probed, and the first expected interface to probe, clear the timeout. But this doesn't mean that this interface being probed will be the correct one, so it may be the case that we end up expecting a new first interface and probing another one. With an example probably seen better... Modem appears with interfaces 2, 3 and 4. 1. We first try to look for interface 0, which is not in the set: 1.1. Probing interfaces 2, 3 and 4 get deferred. 2. First-interface timeout happens because interface 0 doesn't appear, so we switch to wait for interface 1: 2.1 Probing interfaces 2, 3 and 4 get deferred. 3. First-interface timeout happens because interface 1 doesn't appear, so we switch to wait for interface 2: 3.1. We get a match on interface 2, which exists. We now remove the first-interface timeout and start running the init sequence there. 3.2. Probing interfaces 3 and 4 get deferred. 4. Init sequence in interface 2 fails, because it is not an AT port, so we switch to wait for interface 3: 3.1. We get a match on interface 3, which exists. We do *not* need to remove now the first-interface timeout because this interface we are testing is actually the second one which we tried. So, just check whether the timeout exists or not, and if it exists remove it. Yeah, this commit just fixes a warning at the end.
* blacklist: include the whole Openmoko VIDAleksander Morgado2013-10-301-0/+3
|
* plugin: for non-AT ports, don't expect vendor/product string probingAleksander Morgado2013-10-281-5/+10
| | | | | | | | | | | | | When running the pre-probing VID/PID filters, the ports were not filtered out if the plugin had configured post-probing vendor/product string filters. But, these post-probing filters are only applicable to AT ports. From now on, this logic will not be applied to non-serial ports. In other words, pre-probing VID/PID filters applied to non-serial ports will always result in the port being filtered out or being allowed, regardless of any additional vendor/product string post-probing filter configured by the plugin. https://bugzilla.gnome.org/show_bug.cgi?id=710437
* build: ignore built translation filesAleksander Morgado2013-10-281-0/+1
|
* mtk: fix GOTO tag in udev rulesAleksander Morgado2013-10-281-1/+1
|
* po: add Ukrainian translation (bgo #710513)Yuri Chornoivan2013-10-252-0/+99
|
* blacklist/greylist: add more GPS devices (rh #1023234)Dan Williams2013-10-252-0/+17
| | | | | Attempt to blacklist entire drivers that we know aren't modems, and add a sprinkling of specific devices too.
* sms-part-cdma,test: new tests for Latin and Unicode encodingsAleksander Morgado2013-10-251-2/+156
|
* sms-part-cdma: fix log messageAleksander Morgado2013-10-251-1/+1
|
* sms-part-cdma: improve logging when creating PDUsAleksander Morgado2013-10-251-38/+48
|
* sms-part-cdma: support parsing SMS with Unicode encodingAleksander Morgado2013-10-251-0/+29
|
* sms-part-cdma: support generating SMS with Latin or Unicode encodingsAleksander Morgado2013-10-251-23/+92
|
* sms-part-cdma: support receiving SMS with Latin encodingAleksander Morgado2013-10-252-0/+72
|
* sms: decide whether to create a 3GPP2 or 3GPP SMS based on capsAleksander Morgado2013-10-251-6/+26
| | | | | Don't rely on receiving a Teleservice ID. If none received, and the modem is CDMA-only, default to WMT.
* sms: unknown delivery state in newly created SMS objectsAleksander Morgado2013-10-251-0/+1
|
* sms: handle CDMA SMS when creating new ones from MMSmsPropertiesAleksander Morgado2013-10-251-3/+5
|
* libmm-glib: allow new 'teleservice-id' and 'service-category' keywords in ↵Aleksander Morgado2013-10-255-2/+176
| | | | MMSmsProperties
* sms: clear generated parts when storing/sending failsAleksander Morgado2013-10-251-4/+10
|
* sms-qmi: check whether the modem supports the specific SMS typeAleksander Morgado2013-10-251-2/+49
|
* sms: only set concat reference on multipart messagesAleksander Morgado2013-10-251-8/+12
|
* sms: handle CDMA SMS part creationAleksander Morgado2013-10-251-2/+66
|
* cli,sms: print properties just when they are availableAleksander Morgado2013-10-251-27/+23
| | | | | | The logic to decide whether a property is valid in a given PDU type is kind of fuzzy for 3GPP2 as it is currently implemented; so just print whatever we have in the interface.
* sms-qmi: handle CDMA SMS messagesAleksander Morgado2013-10-252-12/+73
|
* sms-part-cdma: new CDMA SMS creatorAleksander Morgado2013-10-253-0/+473
| | | | | | | Currently very limited: * Only WMT teleservice. * Only DMTF-encoded numbers. * Only either raw binary data or ASCII-7 text.
* sms-part-3gpp: ensure PDU type in part is the correct one when building SUBMITAleksander Morgado2013-10-251-0/+9
|
* sms-part-cdma: consolidate loggingAleksander Morgado2013-10-251-9/+9
|
* sms-part-cdma: read 7-bit ASCII text or raw dataAleksander Morgado2013-10-252-6/+55
|
* broadband-modem-qmi: add CDMA SMS parts if foundAleksander Morgado2013-10-251-24/+25
|
* tests: new CDMA SMS part testerAleksander Morgado2013-10-253-1/+268
|
* tests: rename 3GPP SMS part testerAleksander Morgado2013-10-253-41/+41
|
View Lorry Controller Status