summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* huawei: always use DHCP on QMI modemsaleksander/huawei-qmi-always-dhcpAleksander Morgado2014-08-131-1/+58
|
* huawei: define new specific QMI-based modem objectAleksander Morgado2014-08-134-6/+117
|
* bearer-qmi: allow forcing DHCP instead of static IP configAleksander Morgado2014-08-132-7/+77
|
* broadband-modem,plugins: fix GMatchInfo leaksBen Chan2014-08-125-2/+8
|
* huawei: minor style fixesAleksander Morgado2014-08-111-1/+3
|
* huawei: improve support for network time on Huawei modulesDavid McCullough2014-08-114-65/+404
| | | | | | | | | Third revision of Huawei nwtime support. Takes on feedback from the mailing list including helpers, some basic tests and use of the ^NTCT command to determine network time support (^NWTIME). Expanded test cases, more use of g_assert and more logical helper return values/errors. Signed-off-by: David McCullough <david.mccullough@accelecon.com>
* iface-mode: downgrade "access technology changed" message to debugDan Williams2014-08-111-4/+4
| | | | | | | We have a report of a modem that switches access technologies frequently, in this case almost every 10 seconds. While that's unusual, it's not unexpected depending on the RF environment. We shouldn't spam syslog with that info; if we need it we can get it with mmcli.
* build: INCLUDES -> AM_CPPFLAGS to quiet automake warningDan Williams2014-08-052-2/+2
|
* build: require libmbim 1.10.0Aleksander Morgado2014-08-041-1/+1
| | | | | | We were depending on some new MbimNwError values defined at some point in the 1.9 development series. Depend on the new stable 1.10 version now that it's been released.
* libmbim-glib: handle explicit '+' on positive numbersDavid McCullough2014-07-291-1/+1
|
* plugin: improve probing decision logic for QMI and MBIMAleksander Morgado2014-07-271-17/+2
| | | | | | | | | | | So, we may have modems with multiple /dev/cdc-wdm ports, like Ericsson modems, where only 1 of them is MBIM. With the previous logic, we would probe all /dev/cdc-wdm ports for MBIM as soon as one of the ports was handled by the cdc_mbim driver. That is totally not optimal, as we are already know that they are not MBIM (not handled by cdc_mbim). Instead, fix the logic to just probe for MBIM or QMI if the actual driver managing the port is MBIM or QMI.
* broadband-modem-mbim: increase timeout for powering modem up and downBen Chan2014-07-171-1/+1
| | | | | | | It's been observed that some modems occasionally take a long time to power down (which may be due to some shutdown sequence that involves communicating with network). This patch increases the timeout for powering modem up and down from 10s to 20s.
* bearer-mbim: increase disconnect timeoutBen Chan2014-07-171-1/+1
| | | | | | | It's been observed that modems may take a long time to disconnect from the network under certain network conditions. This patch increases the timeout for the MBIM_CID_CONNECT set command in the disconnect sequence from 10s to 30s.
* polkit: fix Location.Setup() authorization rulesAleksander Morgado2014-07-111-1/+1
|
* broadband-modem-mbim: VZ20M returns ERROR_PIN_REQUIRED in PIN query responseAleksander Morgado2014-07-111-1/+9
| | | | | | | VID/PID: 258d:e000 Instead of returning success and the PIN type + PIN status + Remaining attempts, this modem returns a plain ERROR_PIN_REQUIRED error, so try to handle that...
* broadband-modem-mbim: reset strings to NULL, not 0Aleksander Morgado2014-07-091-2/+2
|
* broadband-modem-mbim: update_registration_info immune to null pointers passedkuonirat2014-07-091-2/+2
|
* sim: rename 'MMSim' to 'MMBaseSim'aleksander/base-object-renamesAleksander Morgado2014-07-0637-615/+614
| | | | Just so that we don't have same header names in src/ and /libmm-glib.
* sms: rename 'MMSms' to 'MMBaseSms'Aleksander Morgado2014-07-0615-389/+384
| | | | Just so that we don't have same header names in src/ and /libmm-glib.
* bearer: rename 'MMBearer' to 'MMBaseBearer'Aleksander Morgado2014-07-0642-558/+554
| | | | Just so that we don't have same header names in src/ and /libmm-glib.
* manager: rename 'MMManager' to 'MMBaseManager'Aleksander Morgado2014-07-065-132/+132
| | | | Just so that we don't have same header names in src/ and /libmm-glib.
* huawei: enable GPS_UNMANAGED for Huawei modemsDavid McCullough2014-07-041-59/+78
| | | | Signed-off-by: David McCullough <david.mccullough@accelecon.com>
* option,hso: add missing GPS unamanged capabilityAleksander Morgado2014-07-041-1/+3
|
* huawei: close GPS port once GPS has been disabledAleksander Morgado2014-07-041-0/+6
|
* libqcdm: new 'reset' testerAleksander Morgado2014-07-033-1/+272
| | | | Just like 'modepref', but not doing any mode changes, just OFFLINE+RESET.
* huawei: GPS support for MU609/MU909David McCullough2014-07-033-2/+337
| | | | | | | | | | | | | Implement GPS support on the MU609 and MU090 Huawei modules. Its highly likely the commands are the same for other Huawei modems and it just needs to be activated via udev rules that flag the GPS port with ID_MM_HUAWEI_GPS_PORT=1. There are a lot of options that can be tweaked on the Huawei GPS setup, this code just chooses a simple default for unassisted, standalone GPS operation. Signed-off-by: David McCullough <david.mccullough@accelecon.com>
* cinterion: allow 'unmanaged' GPS setupAleksander Morgado2014-07-021-23/+44
|
* option,hso: print port type before parsingAleksander Morgado2014-07-021-0/+1
|
* option,hso: allow 'unmanaged' GPS setupAleksander Morgado2014-07-021-62/+83
|
* location: new 'unmanaged' GPS setupAleksander Morgado2014-07-024-11/+64
| | | | | | | | | Standard GPS setup (raw/nmea) will both enable the GPS module and take full control of the GPS port. This prevents other processes from reading the NMEA traces from e.g. a tty. In order to handle this, a new 'unmanaged' GPS location source is introduced, which will just enable/disable the GPS module, without reading anything from the GPS port. Of course, both raw/nmea and unmanaged setups cannot be enabled at the same time.
* bearer-mbim: ignore empty DNS server addressesDan Williams2014-07-011-12/+18
|
* cinterion: enable GPS location reporting for the PHS8 in QMI-modeAleksander Morgado2014-07-017-335/+666
| | | | | The PHS8 in QMI-mode doesn't support GPS location retrieval via QMI, so we will fallback to use the AT-based setup and the TTY for reading NMEA traces.
* ifaces: always include <libmm-glib.h>Aleksander Morgado2014-07-015-0/+15
| | | | As they all use the 'MMSimpleStatus' type.
* huawei: avoid AT^GETPORTMODE in Huawei MU609David McCullough2014-07-012-1/+6
| | | | | | | | | | | | | | | | | | | | | | The MU609 modems from Huawei have a bug (confirmed by Huawei) that causes the modem to reset if AT^GETPORTMODE is issued. I have provided and example udev rule I use to disable this command as a patch, feel free to drop that if its not acceptable. Since I cannot tell the modem type from within the udev rules this is less specific than my previous code based patch, but much simpler ;-) I have two modems that share the same USB ID, however, neither supports the ^GETPORTMODE command (and one of them crashes when it is issued). Perhaps someone with a Huawei that supports ^GETPORTMODE can check their USB ID's and see if they clash. Here is a comment from the Huawei devs: > We confirmed this is a issue. This is Qualcomm baseband command at Data > Card. We didn’t delete and block it. We will fix this issue in next FW. > Thank you very much. Sign-off-by: David McCullough <david.mccullough@accelecon.com>
* cinterion: enable GPS location reporting for the PHS8 in AT-modeAleksander Morgado2014-06-274-3/+376
| | | | | This enables support for GPS location reporting when the PHS8 is NOT used in QMI mode.
* modem-helpers: don't return any result if an error happens when parsing CPMS=?Aleksander Morgado2014-06-272-15/+33
| | | | | We shouldn't rely on the caller to cleanup intermediate results when returning an error.
* modem-helpers: improve +CMTI indication regexAleksander Morgado2014-06-251-1/+1
| | | | | | Allow whitespaces added in several places, like between the comma and the index, which is what the Cinterion PHS8 does: <CR><LF>+CMTI: "MT", 5<CR><LF>
* cinterion: update default setting for new SMS indicationsAleksander Morgado2014-06-251-9/+215
| | | | | | | | | | | | | | | | | The setup in Cinterion modems goes as follows: AT+CNMI=<mode>[, <mt>[, <bm>[, <ds>[, <bfr>]]]] For each field, several setups are available, so we could use a default value, as we were doing until now (+CNMI=2,1,2,2,1). BUT, not every Cinterion modem allows the same set of settings. For example, the new PHS8 only allows '0' for the <ds> value: AT+CNMI=? +CNMI: (0,1,2),(0,1),(0,2),(0),(1) So, instead of hardcoding the setup, try to find the best suitable one for each modem. We'll parse the +CNMI=? test response to know which values are supported during the messaging support check, which is run once during initialization.
* cinterion: new 'AT+CNMI=?' parser helperAleksander Morgado2014-06-253-0/+278
|
* base-modem: quicker find matching cdc-wdm QMI or MBIM portsAleksander Morgado2014-06-231-202/+48
|
* huawei: quicker find matching cdc-wdm AT portAleksander Morgado2014-06-231-68/+15
| | | | | | Without using a new GUdevClient. Based on a patch from Dan Williams <dcbw@redhat.com>
* port: store parent sysfs path in each MMPortAleksander Morgado2014-06-2320-18/+75
|
* huawei: flag /dev/cdc-wdm as primary if no primary found alreadyAleksander Morgado2014-06-231-2/+21
|
* huawei: setup unsolicited message handlers also in the AT cdc-wdm portsAleksander Morgado2014-06-231-52/+79
|
* huawei: use the cdc-wdm port dialing if availableAleksander Morgado2014-06-233-27/+177
| | | | | | With the new 'huawei-cdc-ncm' driver in the kernel, we now may get a /dev/cdc-wdm AT-capable port exposed by the Huawei device. If so, we must use this port for NDISDUP dialling in order to get the network interface connected.
* build: ignore test filesAleksander Morgado2014-06-221-0/+2
|
* build: avoid using 'INCLUDES' in Makefile.amAleksander Morgado2014-06-222-12/+18
| | | | | Avoids warnings during build; e.g.: warning: 'INCLUDES' is the old name for 'AM_CPPFLAGS' (or '*_CPPFLAGS')
* bearer-mbim: fix disconnect error handling case splitPrathmesh Prabhu2014-06-201-1/+1
| | | | | | The first case, with no error, needs to check that there was no original error. Currently, if an error occurs and the resulting NwError is parsed correctly, the case split treats it as a no-error case.
* modem-helpers-mbim: map more MbimNwError to MMMobileEquipmentErrorPrathmesh Prabhu2014-06-191-0/+4
| | | | | | | | Commit 55e40ea b1ae81a in libmbim ("libmbim-glib: add additional GMM cause codes to MbimNwError") added one more GMM cause code to MbimNwError. This patch maps that to MMMobileEquipmentError. This patch requires libmbim >= 1.9.0
* bearer-mbim: disconnect attempt should succeed if bearer is already disconnectedPrathmesh Prabhu2014-06-181-25/+39
| | | | | | When trying to disconnect bearer, if the modem responds with MBIM_STATUS_ERROR_CONTEXT_NOT_ACTIVATED, take it to mean that the bearer has already been disconnected.
View Lorry Controller Status