proxmox-mirrors/fwupd
1
0
Fork 0
mirror of https://git.proxmox.com/git/fwupd synced 2025-05-18 16:32:33 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
8fada51919
fwupd/plugins/modem-manager
History
Aleksander Morgado 8a1dce9472 modem-manager: increase the timeout to wait for modem after uninhibited 
The timeout to wait for the modem after being uninhibited was until
now exclusively to cover the port probing time, because the device
would be already available and ready to be used as soon as the
inhibition was removed.

With the change to include carrier config selection as part of the
fwupd upgrade process, the time to wait for the modem after being
uninhibited should now cover a full reboot of the module, and so the
original timeout of 45s could be a bit tight under some circumstances
(e.g the MM device probing logic is quite slow when there is no SIM
card detected by the module).

We increase this timeout to a much safer value of 120s, which is
extremely long for most cases, but should also be enough to cover even
the worst case scenario.
2019-04-09 07:54:46 -04:00
..
fu-mm-device.c modem-manager: increase the timeout to wait for modem after uninhibited 2019-04-09 07:54:46 -04:00
fu-mm-device.h modem-manager: implement support for qmi-pdc 2019-02-27 16:09:13 +00:00
fu-mm-utils.c modem-manager: implement support for qmi-pdc 2019-02-27 16:09:13 +00:00
fu-mm-utils.h modem-manager: implement support for qmi-pdc 2019-02-27 16:09:13 +00:00
fu-plugin-modem-manager.c modem-manager: implement qmi pdc active config selection as attach() 2019-04-09 07:54:46 -04:00
fu-qmi-pdc-updater.c modem-manager: implement qmi pdc active config selection as attach() 2019-04-09 07:54:46 -04:00
fu-qmi-pdc-updater.h modem-manager: implement qmi pdc active config selection as attach() 2019-04-09 07:54:46 -04:00
meson.build modem-manager: implement support for qmi-pdc 2019-02-27 16:09:13 +00:00
README.md modem-manager: implement support for qmi-pdc 2019-02-27 16:09:13 +00:00

README.md

ModemManager

Introduction

This plugin adds support for devices managed by ModemManager.

GUID Generation

These device use the ModemManager "Firmware Device IDs" as the GUID, e.g.

  • USB\VID_413C&PID_81D7&REV_0318&CARRIER_VODAFONE
  • USB\VID_413C&PID_81D7&REV_0318
  • USB\VID_413C&PID_81D7
  • USB\VID_413C

Update method: fastboot

If the device supports the 'fastboot' update method, it must also report which AT command should be used to trigger the modem reboot into fastboot mode.

Once the device is in fastboot mode, the firmware upgrade process will happen as defined e.g. in the 'flashfile.xml' file. Every file included in the CAB that is not listed in the associated 'flashfile.xml' will be totally ignored during the fastboot upgrade procedure.

Update method: qmi-pdc

If the device supports the 'qmi-pdc' update method, the contents of the CAB file should include files named as 'mcfg.*.mbn' which will be treated as MCFG configuration files to download into the device using the Persistent Device Configuration QMI service.

If a device supports both 'fastboot' and 'qmi-pdc' methods, the fastboot operation will always be run before the QMI operation, so that e.g. the full partition where the MCFG files are stored can be wiped out before installing the new ones.