~modemmanager/modemmanager/MM

~modemmanager/modemmanager/MM_05 » Changes from revision 1007

From Revision 1007 to 988

Rev	Summary	Authors	Tags	Date
1007	release: bump version to 0.5.4 release: bump version to 0.5.4	Dan Williams	0.5.4, 0.5.4.0	11 years ago
1006	release: update NEWS release: update NEWS	Dan Williams		11 years ago
1005	huawei: add two more strings to detect secondary port huawei: add two more strings to detect secondary port	Dan Williams		11 years ago
1004	sierra: fix CSQ handling on APP1 port sierra: fix CSQ handling on APP1 port The APP1 port doesn't always prefix its replies with <CR><LF> which runs afoul of the built-in echo removal. Since Sierra modems are on the whole well-behaved WRT echo removal, just disable it on the secondary ports. Only changes behavior for PPP-based devices since they are the only ones that use the APP1 ports.	Dan Williams		11 years ago
1003	core: speed up QCDM probing a bit core: speed up QCDM probing a bit The point of sending two "version info" commands was to ensure that the terminating 0x7E of the first one was processed as a QCDM frame boundary and that any random data in the buffer (like AT commands from probing) got cleared out. The second command would always get processed as a valid QCDM command if the device supported QCDM, since there was no garbage before it. Instead of that dance, just prepend the version info message with an extra 0x7E to ensure a clean QCDM frame which the device hopefully responds to immediately. Second, actually process that response instead of throwing it away. Should save about 3 seconds when probing QCDM ports.	Dan Williams		11 years ago
1002	sierra: use DHCP for the USB 305 (AT&T Lightning) sierra: use DHCP for the USB 305 (AT&T Lightning) For some reason, my AT&T Lightning just doesn't work with static IP (AT%IPDPADDR) any more. No traffic passes even though everything is set up the way it was before. No idea what happened. Using latest firmware 2.0.0.11. But what's interesting is on Windows the generic Sierra Watcher app uses DHCP. But on Linux, when using AT%IPDPACT, DHCP doesn't work. That's odd. But it turns out the modem supports the "standard" Sierra proprietary AT!SCACT commands, and that does make DHCP work. Crazy no? So since the Windows app uses DHCP, it's likely that the non-DHCP case (AT%IPDPACT/AT%IPDPADDR) either isn't well tested or isn't well supported. With that in mind, let's just use DHCP for this device in Linux too.	Dan Williams		11 years ago
1001	icera: allow implementors to supply custom call control comm... icera: allow implementors to supply custom call control commands Some devices should use custom call control commands instead of AT%IPDPACT.	Dan Williams		11 years ago
1000	icera: handle additional IPv4 configuration options icera: handle additional IPv4 configuration options Newer devices like the ZTE/Vodafone K3805-z have an enhanced %IPDPADDR command that includes a netmask and gateway, and these are necessary to configure the device since it uses /24 instead of a /32. Since the device is nice enough to tell us that, we should probably use that information. Unfortunately the MM API doens't expose the netmask and gateway yet, so we'll have to add a GetIP4ConfigEx() method or something like that, but this commit sets us up to do that.	Dan Williams		11 years ago
999	zte: handle Icera-based devics that use DHCP zte: handle Icera-based devics that use DHCP Since we can't autodetect that the devices use DHCP, we'll need to tag them with udev rules for the time being.	Dan Williams		11 years ago
998	gsm: if the generic CNMI request fails, try a Qualcomm-compa... gsm: if the generic CNMI request fails, try a Qualcomm-compatible one Many devices based on Qualcomm chipsets don't support a <ds> value of '1', despite saying they do in the AT+CNMI=? response. But they do accept '2'. Since we're not doing much with delivery status reports yet, if we get a CME 303 (not supported) error when setting the message indication parameters via CNMI, fall back to the Qualcomm-compatible CNMI parameters. If we don't do this, we don't get SMS indications on these devices, because the original CNMI failed. Tested on Huawei E1550, Huawei E160G, ZTE MF622, and Novatel XU870.	Dan Williams		11 years ago
997	sms: fix handling of 'data' property for multipart messages sms: fix handling of 'data' property for multipart messages Text was getting concatenated when reconstructing the full message, but the data wasn't. That meant that non-text multipart messages, like the binary APN/MMS settings messages that operators often send, were broken.	Dan Williams		11 years ago
996	sms: suppress warnings when reconstructing multipart message... sms: suppress warnings when reconstructing multipart messages Not all properties are strings, so when copying the GValue we have to use the source GValue's type, not STRING.	Dan Williams		11 years ago
995	mbm: add Ericsson H5321gw (often found in Thinkpad X230) mbm: add Ericsson H5321gw (often found in Thinkpad X230)	Dan Williams		11 years ago
994	gsm: better handling of IMSI response gsm: better handling of IMSI response Moto EZX devices prefix the response with "+CIMI:" while most devices do not.	Dan Williams		11 years ago
993	novatel: fix checking ERI for roaming/home decision novatel: fix checking ERI for roaming/home decision More fallout from b22b2d99db57e4cec8e6c3074dd20acd6845cb62 which changed the return type of the qcdm_result_get_*() functions.	Dan Williams		11 years ago
992	icera: be more paranoid about cleaning up connect operations icera: be more paranoid about cleaning up connect operations In case the connect gets interrupted by a disconnect or something.	Dan Williams		11 years ago
991	icera: retry configuring PDP context if it fails. icera: retry configuring PDP context if it fails. If a connect operation is attempted immediately after a disconnect, it sometimes fails with CME error 583 - "a profile (CID) is currently active". Apparently, even though the preceding operation (%IPDPACT) to deactivate the PDP context returned an OK response, the context is not really completely available until a fraction of a second later. This causes the %IPDPCFG operation that is part of the subsequent connect attempt to fail with error 583. This change retries the %IPDPCFG after a one second delay. BUG=chrome-os-partner:4936 TEST=This can be tested from the UI, but I found it easier to produce the timing needed to trigger the bug by running mm-disconnect and mm-connect from a shell. Start out with the modem in the connected state. In the shell, run sudo /usr/local/lib/flimflam/test/mm-disconnect; sudo /usr/local/lib/flimflam/test/mm-connect --number='*99#' --apn=wap.cingular modem-manager should emit the log line "Invalid error code: 583". Prior to this change, the connect operation would fail. Now it should succeed. Change-Id: I6ae0e6a9f5405b54b0b465fe91d9542529f365c2 Reviewed-on: http://gerrit.chromium.org/gerrit/5781 Tested-by: Eric Shienbrood <ers@chromium.org> Reviewed-by: Nathan J. Williams <njw@chromium.org>	Eric Shienbrood		11 years ago
990	test: add utility to force a modem disconnect test: add utility to force a modem disconnect	Dan Williams		11 years ago
989	core: send State property change signals core: send State property change signals It was already exported via D-Bus, but the change signals weren't getting sent out. I believe this was a holdover from when we weren't sure whether to export the internal state or not. But we should.	Dan Williams		11 years ago
988	sierra: fix detection of APP1 port sierra: fix detection of APP1 port The APP1 port (which has a limited AT parser) doesn't prefix its replies with <CR><LF> like nice modems do, and that means it runs afoul of the echo removal bits of the AT serial port code. We need to parse the whole string even though it's not prefixed properly to find the APP1 string in the response.	Dan Williams		11 years ago

Older »