- Feb 10, 2015
-
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
Aleksander Morgado authored
Some new devices, like the Dell DW5770, will return an internal error when trying to bring the power mode to online. We can avoid this by sending the magic "DMS Set FCC Auth" message before retrying. Bumping libqmi version to 1.12.4, which is the one that supports this new message in the stable libqmi branch. https://bugzilla.kernel.org/show_bug.cgi?id=92101
-
- Jan 29, 2015
-
-
-
Aleksander Morgado authored
Based on a patch from Bastiaan Jacques <bastiaan@bjacques.org> https://bugzilla.redhat.com/show_bug.cgi?id=1177799 https://bugs.freedesktop.org/show_bug.cgi?id=88864
-
- Jan 26, 2015
-
-
Dan Williams authored
MM probing appears to make 'visor' module die; and anyway most of the devices driven by 'visor' are not phones, and of the 3 that are phones they are so old (2002 - 2005 era) that nobody is likely using them for dialup anymore. http://www.spinics.net/lists/linux-usb/msg120483.html
-
- Jan 13, 2015
-
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
Aleksander Morgado authored
-
- Jan 09, 2015
-
-
This patch increases the response timeout for the probe AT commands for altair modems. We've been noticing some altair modems taking upto 6 seconds to respond to the initial probe command after a reset which results in modem-manager timing out and sending a second probe command. The modem sends a response after about 6 seconds for the initial probe command which modem-manager treats as response to second probe command and this results in the modem-manager and modem going out of sync because the modem's second probe response is treated as response to the next initialization AT command sent by modem-manager and so on. Change-Id: Iad8b0786327b153fd95c8ee4516f352325a42cf7
-
Aleksander Morgado authored
If we get multiple message lists, we need to make sure the previous one is cleared out before going to the next one.
-
- Dec 30, 2014
-
-
Aleksander Morgado authored
Since libmbim 1.11.1, mbim_device_command_finish() may return messages of type 'Function Error', so we shouldn't assume 'Command Done' messages are returned. This commit is equivalent to this one in git master, but instead of bumping the libmbim requirement to 1.11.1, we provide a fallback implementation so that the same logic works when libmbim is < 1.11.1. commit 46b707f8 Author: Aleksander Morgado <aleksander@aleksander.es> Date: Sun Dec 28 17:55:50 2014 +0100 mbim: use the new response checker helper method mbim_message_response_get_result() is available in libmbim-glib 1.11.1.
-
- Dec 26, 2014
-
-
For certain devices the name changes with their status. Notably, RFCOMM devices move from /devices/virtual/ to underneath the HCI that is used for the connection as the session is estabilished, and return back when it's torn down.
-
- Dec 03, 2014
-
-
Aleksander Morgado authored
Icera-based modems need to return a correct response to the AT%IPSYS? command, so that they are properly detected as being Icera-based. Now, some modems, like the Nokia 21M-02, don't seem to return a correct response to AT%IPSYS just after being plugged in. So, setup a retry mechanism (3 retries, with 2 seconds between retries) to try to cope with this issue. https://bugs.freedesktop.org/show_bug.cgi?id=85012 Logs from the error situation: [mm-port-serial-at.c:440] debug_log(): (ttyACM0): --> 'ATE1 E0<CR>' [mm-port-serial-at.c:440] debug_log(): (ttyACM2): --> 'ATE1 E0<CR>' [mm-port-serial-at.c:440] debug_log(): (ttyACM1): --> 'ATE1 E0<CR>' [mm-port-serial-at.c:440] debug_log(): (ttyACM0): <-- 'E0' [mm-port-serial-at.c:440] debug_log(): (ttyACM0): <-- '<CR><CR><LF>ERROR<CR><LF>' [mm-serial-parsers.c:364] mm_serial_parser_v1_parse(): Got failure code 100: Unknown error [mm-port-probe-at.c:43] mm_port_probe_response_processor_is_at(): Parsing AT got: 'Unknown error' [mm-port-probe.c:155] mm_port_probe_set_result_at(): (tty/ttyACM0) port is AT-capable [mm-port-serial-at.c:440] debug_log(): (ttyACM2): <-- 'ATE1 E0' [mm-port-serial-at.c:440] debug_log(): (ttyACM1): <-- ' E0' [mm-port-serial-at.c:440] debug_log(): (ttyACM2): <-- '<CR>' [mm-port-serial-at.c:440] debug_log(): (ttyACM1): <-- '<CR><CR><LF>ERROR<CR><LF>' [mm-serial-parsers.c:364] mm_serial_parser_v1_parse(): Got failure code 100: Unknown error [mm-port-probe-at.c:43] mm_port_probe_response_processor_is_at(): Parsing AT got: 'Unknown error' [mm-port-probe.c:155] mm_port_probe_set_result_at(): (tty/ttyACM1) port is AT-capable [mm-port-serial-at.c:440] debug_log(): (ttyACM2): <-- '<CR><LF>OK<CR><LF>' [mm-port-probe.c:155] mm_port_probe_set_result_at(): (tty/ttyACM2) port is AT-capable [mm-port-serial-at.c:440] debug_log(): (ttyACM0): --> 'AT%IPSYS?<CR>' [mm-port-serial-at.c:440] debug_log(): (ttyACM1): --> 'AT%IPSYS?<CR>' [mm-port-serial-at.c:440] debug_log(): (ttyACM2): --> 'AT%IPSYS?<CR>' [mm-port-serial-at.c:440] debug_log(): (ttyACM0): <-- 'AT%IPSYS?' [mm-port-serial-at.c:440] debug_log(): (ttyACM0): <-- '<CR>' [mm-port-serial-at.c:440] debug_log(): (ttyACM1): <-- 'AT%IPSYS?' [mm-port-serial-at.c:440] debug_log(): (ttyACM1): <-- '<CR><CR><LF>ERROR<CR><LF>'
-
Aleksander Morgado authored
Also, allow IPDPADDR returns where only DNS IPv6 is given (i.e. no IPv6 address to set), and in that case default to DHCP method in the bearer. https://bugs.freedesktop.org/show_bug.cgi?id=85012
-
Aleksander Morgado authored
Newer huawei modems, like the E3372, use the following ^GETPORTMODE response format: ^GETPORTMODE: TYPE: WCDMA: ,pcui:1,modem:2,ncm:3,mass:4,mass_two:5, This patch updates the parser that looks for the control TTY (pcui) and data TTY (modem). https://bugs.freedesktop.org/show_bug.cgi?id=86658
-
- Nov 14, 2014
-
-
- Oct 29, 2014
-
-
Aleksander Morgado authored
Stupid me, introduced a bug when manually writing the previous patch. :/
-
My modem (Samsung GI B3740) responded "IPV4" to "CGDCONT=?". This was not handled in mm-modem-helpers.c. The obvious fix was to return MM_BEARER_IP_FAMILY_IPV4.
-
When the MBIM modem unexpectedly loses connection the port state never gets set as disconnected thus when trying to reestablish a new connection the bearer cannot find a port in the disconnected state. Signed-off-by: Greg Suarez <gpsuarez2512@gmail.com>
-
- Oct 28, 2014
-
-
Dan Williams authored
-
- Oct 07, 2014
-
-
Dan Williams authored
b2823041 moved up the self->priv->forced_close = TRUE, which caused mm_port_serial_close() to just return without actually closing the port and cleaning up. Also, cancel the reopen separately from closing the port since the two operations are actually independent of each other.
-
- Sep 05, 2014
-
-
Aleksander Morgado authored
The MF60 exposes a QMI+net pair, but they are unusable as the WDS service returns error when e.g. launching a connection. So, fallback to AT+PPP in this device.
-
Aleksander Morgado authored
The new 'ID_MM_PORT_IGNORE' tag will tell ModemManager to fully avoid using a given port. This commit is a the backport of 31f81725 to the mm-1-4 branch. Instead of grabbing but ignoring the port, in this case we just fully ignore it from the very beginning.
-
Aleksander Morgado authored
-
- Aug 22, 2014
-
-
Aleksander Morgado authored
-
Aleksander Morgado authored
$ git shortlog -s -n
-
- Aug 18, 2014
-
-
Dan Williams authored
Some newer modems (Huawei E1750, Sierra 73xx) provide what looks like legitimate static IPv4 configuration through the WDSGetCurrentSettings call, but when configured the interface does not pass traffic. Running DHCP on the same interface provides a slightly different IPv4 configuration but does allow traffic to pass. Since QMI was switched to static originally for consistency with IPv6 and for speed of IP configuration (since DHCP takes a bit of time), but not for any known problems with modems, let's switch back to DHCP until we have time to figure out what's actually going on.
-
-
- Aug 12, 2014
-
-
- Aug 11, 2014
-
-
Aleksander Morgado authored
-
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>
-
Dan Williams authored
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.
-
- Aug 05, 2014
-
-
Dan Williams authored
-
- Aug 04, 2014
-
-
Aleksander Morgado authored
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.
-
- Jul 29, 2014
-
-
- Jul 27, 2014
-
-
Aleksander Morgado authored
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.
-
- Jul 17, 2014
-
-
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.
-
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.
-