Skip to content
Snippets Groups Projects
  1. Jan 24, 2025
  2. Jan 23, 2025
  3. Nov 30, 2024
    • Aleksander Morgado's avatar
      mbimcli: new '--query-register-state' action · 95b9b0e5
      Aleksander Morgado authored
      Just a rename, we keep '--query-registration-state' as a valid but
      hidden action. This is to be in line with the MBIM message name, which
      is "Register State".
      95b9b0e5
    • Aleksander Morgado's avatar
      mbimcli: new '--set-register-state' action · 2d2c3764
      Aleksander Morgado authored
      The new '--set-register-state' action allows configuring automatic or
      manual registration, also specifying the MCCMNC to bind to and
      optionally the list of data modes to prefer.
      
      The '--register-automatic' action is considered deprecated, and can be
      replaced with '--set-register-state="action=automatic".
      
      Automatic registration setup:
        $ sudo mbimcli -d /dev/cdc-wdm1 -p --set-register-state='
                     action=automatic'
      
      Manual registration to a specific operator:
        $ sudo mbimcli -d /dev/cdc-wdm1 -p --set-register-state='
                     action=manual,
                     provider-id=21407'
      
      Manual registration to a specific operator on limited access techs:
        $ sudo mbimcli -d /dev/cdc-wdm1 -p --set-register-state='
                     action=manual,
                     provider-id=21407,
                     data-class=lte|umts'
      2d2c3764
  4. Nov 29, 2024
  5. Nov 27, 2024
  6. Aug 21, 2024
  7. Aug 06, 2024
  8. Aug 04, 2024
  9. Jul 26, 2024
  10. Jun 19, 2024
  11. Jun 17, 2024
  12. Jun 14, 2024
  13. Jun 11, 2024
  14. Jun 05, 2024
  15. May 27, 2024
  16. May 23, 2024
    • Lubomir Rintel's avatar
      mbimcli-intel-tools: parse trace command & value in a more straightforward way · 65d02fc6
      Lubomir Rintel authored
      Don't conditionalize setting trace_command and trace_value on split
      substrings being non-NULL. It makes a static analysis tool think they
      might be used uninitialized. That can-not happen, because the substrings
      can in fact never be NULL.
      
      Let's keep the check in form of an assert (perhaps to guard against
      a possible glib bug, etc.).
      65d02fc6
  17. May 13, 2024
  18. Apr 22, 2024
  19. Apr 08, 2024
  20. Apr 07, 2024
  21. Mar 28, 2024
    • Slark Xiao's avatar
      mbim-proxy: remove same shortName for --verbose-full · 001993c5
      Slark Xiao authored
      When calling mbim-proxy with parameter '-v', it will report an
      error "cannot specify --verbose and --verbose-full at the same
      time". This issue was caused by the same shorName of --verbose
      and --verbose-full. Remove the shortName of '--verbose-full'
      align with mbimcli.
      
      Fixes #b1ca8388
      001993c5
  22. Mar 18, 2024
  23. Feb 12, 2024
  24. Dec 13, 2023
  25. Dec 04, 2023
    • Aleksander Morgado's avatar
      libmbim-glib,proxy: no need to block MBIM_DEVICE_SIGNAL_ERROR during open · da129826
      Aleksander Morgado authored and Aleksander Morgado's avatar Aleksander Morgado committed
      If the proxy is checking whether a given device is really open or not,
      it sends a caps query request, which may be replied with a
      FUNCTION_ERROR stating that the device is not open. If this happens,
      the proxy will explicitly force close the device, and try to reopen it
      again.
      
      The MBIM_DEVICE_SIGNAL_ERROR is always scheduled to be emitted after
      the response processor has been executed. In the case of the proxy,
      the response processor force-closes the MBIM device, which in turn
      would cancel any scheduled MBIM_DEVICE_SIGNAL_ERROR emission.
      
      There is really no need to block MBIM_DEVICE_SIGNAL_ERROR any more due
      to this.
      da129826
    • Aleksander Morgado's avatar
      libmbim-glib,device: avoid emitting SIGNAL_ERROR if device closed · c445aee9
      Aleksander Morgado authored and Aleksander Morgado's avatar Aleksander Morgado committed
      The SIGNAL_ERROR signal is supposed to be emitted whenever we receive
      a FUNCTION_ERROR response. The signal is emitted *after* the message
      response processor has been executed, and this means that there is
      a chance that the response processor may have already closed the MBIM
      device. If this happens, we should not emit the SIGNAL_ERROR signal,
      as the user has already expressed their desire to fully close the
      ongoing MBIM session.
      
      This avoids the SIGNAL_ERROR signal being processed after the user has
      already requested a new MBIM device open following a forced close.
      
      Issue found by Maciej S. Szmigiero <mail@maciej.szmigiero.name>, and
      this patch implemented as an alternative to the one he wrote in
      !193
      
      Fixes #43
      c445aee9
    • Maciej S. Szmigiero's avatar
      libmbim-glib,device: set open_status to OPEN_STATUS_CLOSED in mbim_device_close_force · f459174c
      Maciej S. Szmigiero authored and Aleksander Morgado's avatar Aleksander Morgado committed
      Otherwise mbim_device_open ->
      device_open_context_step (DEVICE_OPEN_CONTEXT_STEP_FIRST) will refuse
      re-opening as it will think the device is already open.
      
      This refusal broke device re-opening on MBIM_PROTOCOL_ERROR_NOT_OPENED.
      
      Fixes: 0a119a7a ("libmbim-glib,device: ensure CLOSED state always in mbim_device_close()")
      f459174c
    • Aleksander Morgado's avatar
      bdfccccd
    • Ulrich Mohr's avatar
      mbimcli: Add sms functionality · 9f385e8b
      Ulrich Mohr authored and Aleksander Morgado's avatar Aleksander Morgado committed
      This adds a new group for sms functionality with two new functions:
       - --sms-delete
       - --sms-read
      9f385e8b
Loading