Skip to content
Snippets Groups Projects
  1. Jul 19, 2012
  2. Jul 18, 2012
    • Dan Williams's avatar
      gsm: fix sending SMS messages on some modems and use PDU by default · 65f13f41
      Dan Williams authored
      It turns out we really do have to wait for the modem to return the
      ">" prompt before sending the message data, otherwise a number of
      modems will complain about the data and fail the message.  Fix that
      by sending the first bit of the CMGS, waiting for the ">", and then
      sending the rest.
      
      This also switches all modems over to PDU mode by default if they
      support it, since it's more compatible and most recent modems don't
      even bother to support text mode anyway.
      65f13f41
  3. Jul 17, 2012
  4. Jul 16, 2012
  5. Jul 12, 2012
  6. Jul 02, 2012
  7. Jun 25, 2012
  8. Jun 22, 2012
  9. Jun 06, 2012
    • Dan Williams's avatar
      zte: try to handle Icera devices that use PPP · 535ae3a1
      Dan Williams authored
      Not all devices present a network interface, and on these devices
      we need to fall back to PPP using the standard setup commands.  But
      they appear to support the Icera custom commands for access technology
      and such, so still use those.
      
      Hopefully fixes ZTE MF665C.
      535ae3a1
  10. Jun 04, 2012
  11. May 31, 2012
  12. May 23, 2012
  13. Mar 26, 2012
    • Aleksander Morgado's avatar
      option: hso_get_cid() always returns >= 0 · 16a00296
      Aleksander Morgado authored
      This patch fixes undesired disconnection attempts during modem disabling. The
      new `hso_has_cid()' allows to check whether there is a valid CID stored before
      trying to get it with `hso_get_cid()', as this last method ensures that a valid
      CID number is returned, even if there is none.
      
      Relevant logs of the issue:
      
      modem-manager[24085]: hso_get_cid: runtime check failed: (cid >= 0)
      modem-manager[24085]: hso_get_cid: runtime check failed: (cid >= 0)
      modem-manager[24085]: (ttyHS4): --> 'AT_OWANCALL=0,0,1<CR>'
      modem-manager[24085]: (ttyHS4): <-- '<CR><LF>ERROR<CR><LF>'
      modem-manager[24085]: Got failure code 100: Unknown error
      16a00296
    • Aleksander Morgado's avatar
      option: fix reading port-specific setup file · 1887d75e
      Aleksander Morgado authored
      The `physdev' stored in the probe is the sysfs path of the parent device, that
      owning all ports. We need to build the setup file path using the port's sysfs
      path instead.
      1887d75e
  14. Mar 23, 2012
  15. Mar 22, 2012
  16. Mar 13, 2012
  17. Mar 05, 2012
Loading