Skip to content
Snippets Groups Projects
  1. Aug 29, 2012
    • Dan Williams's avatar
      release: bump version to 0.5.4 · c1777930
      Dan Williams authored
      2 tags
      c1777930
    • Dan Williams's avatar
      release: update NEWS · 91eec4d8
      Dan Williams authored
      91eec4d8
    • Dan Williams's avatar
      02aa7580
    • Dan Williams's avatar
      sierra: fix CSQ handling on APP1 port · d1be19d2
      Dan Williams authored
      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.
      d1be19d2
    • Dan Williams's avatar
      core: speed up QCDM probing a bit · 01201860
      Dan Williams authored
      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.
      01201860
    • Dan Williams's avatar
      sierra: use DHCP for the USB 305 (AT&T Lightning) · 44f70121
      Dan Williams authored
      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.
      44f70121
    • Dan Williams's avatar
      icera: allow implementors to supply custom call control commands · 7605ea7f
      Dan Williams authored
      Some devices should use custom call control commands instead of
      AT%IPDPACT.
      7605ea7f
    • Dan Williams's avatar
      icera: handle additional IPv4 configuration options · c8153b1e
      Dan Williams authored
      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.
      c8153b1e
    • Dan Williams's avatar
      zte: handle Icera-based devics that use DHCP · d2654a28
      Dan Williams authored
      Since we can't autodetect that the devices use DHCP, we'll need to
      tag them with udev rules for the time being.
      d2654a28
    • Dan Williams's avatar
      gsm: if the generic CNMI request fails, try a Qualcomm-compatible one · 1d9164ec
      Dan Williams authored
      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.
      1d9164ec
    • Dan Williams's avatar
      sms: fix handling of 'data' property for multipart messages · 1c29ce59
      Dan Williams authored
      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.
      1c29ce59
    • Dan Williams's avatar
      sms: suppress warnings when reconstructing multipart messages · 889e8114
      Dan Williams authored
      Not all properties are strings, so when copying the GValue we
      have to use the source GValue's type, not STRING.
      889e8114
    • Dan Williams's avatar
    • Dan Williams's avatar
      gsm: better handling of IMSI response · 0b051f9c
      Dan Williams authored
      Moto EZX devices prefix the response with "+CIMI:" while most
      devices do not.
      0b051f9c
  2. Aug 24, 2012
    • Dan Williams's avatar
      novatel: fix checking ERI for roaming/home decision · c21e29c5
      Dan Williams authored
      More fallout from b22b2d99
      which changed the return type of the qcdm_result_get_*() functions.
      c21e29c5
    • Dan Williams's avatar
      icera: be more paranoid about cleaning up connect operations · 4c1791f2
      Dan Williams authored
      In case the connect gets interrupted by a disconnect or something.
      4c1791f2
    • Eric Shienbrood's avatar
      icera: retry configuring PDP context if it fails. · fb318784
      Eric Shienbrood authored and Dan Williams's avatar Dan Williams committed
      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: default avatarEric Shienbrood <ers@chromium.org>
      Reviewed-by: default avatarNathan J. Williams <njw@chromium.org>
      fb318784
    • Dan Williams's avatar
      ef44795f
    • Dan Williams's avatar
      core: send State property change signals · 15239299
      Dan Williams authored
      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.
      15239299
    • Dan Williams's avatar
      sierra: fix detection of APP1 port · e0242b4d
      Dan Williams authored
      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.
      e0242b4d
    • Dan Williams's avatar
      core: add function to open probe ports without removing echo · 21e66dfa
      Dan Williams authored
      Some devices (Sierra GSM ones) return stuff we need but don't
      bother to prefix it with <CR><LF>, so we need to optionally turn
      off the echo removal at probe time.
      21e66dfa
  3. Aug 16, 2012
    • Dan Williams's avatar
      build: clean marshallers from git master · 4de93241
      Dan Williams authored
      When switching branches from git master to MM_06 and 05, the
      marshallers generated by git master in src/ get #included
      rather than the ones from marshallers/.  So make sure we clean
      them when doing 'make clean'.
      4de93241
  4. Aug 09, 2012
  5. Aug 08, 2012
  6. Jul 30, 2012
    • Aleksander Morgado's avatar
      huawei: limit the number of deferred tasks · f84f641a
      Aleksander Morgado authored
      The Huawei plugin requires to probe first the USB interface 0; all the other
      probing tasks in the remaining ports will get deferred until the interface 0
      gets probed. But, some modems (e.g. Huawei ET8282), don't expose the USB
      interface 0 as an AT port, so we get an infinite loop as no port ends up being
      probed.
      
      In order to fix this, we will limit to a predefined maximum the number of times
      a given probing task is deferred, 4 in this case. So, if a given probing task is
      deferred for more than 4x3s=12s, probing will get forced.
      f84f641a
  7. Jul 25, 2012
  8. Jul 23, 2012
  9. Jul 21, 2012
  10. Jul 19, 2012
  11. Jul 18, 2012
Loading