fwupd/plugins/modem-manager
Richard Hughes 7afd7cba0d Use FuFirmware as a container for firmware images
In many plugins we've wanted to use ->prepare_firmware() to parse the firmware
ahead of ->detach() and ->write_firmware() but this has the limitation that it
can only return a single blob of data.

For many devices, multiple binary blobs are required from one parsed image,
for instance providing signatures, config and data blobs that have to be pushed
to the device in different way.

This also means we parse the firmware *before* we ask the user to detach.

Break the internal FuDevice API to support these firmware types as they become
more popular.

This also allows us to move the Intel HEX and SREC parsing out of the dfu plugin
as they are used by a few plugins now, and resolving symbols between plugins
isn't exactly awesome.
2019-08-08 13:10:57 +01:00
..
fu-mm-device.c Use FuFirmware as a container for firmware images 2019-08-08 13:10:57 +01:00
fu-mm-device.h modem-manager: implement support for qmi-pdc 2019-02-27 16:09:13 +00:00
fu-mm-utils.c trivial: Fix a missing config.h include in a new source file 2019-05-02 09:59:47 +01: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 Allow handling FORCE for devices that subclass FuDevice 2019-05-05 15:29:00 -05: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: add counterpart GUID for the DW5821e 2019-08-05 16:15:09 +01:00
modem-manager.quirk modem-manager: add counterpart GUID for the DW5821e 2019-08-05 16:15:09 +01:00
README.md modem-manager: implement support for qmi-pdc 2019-02-27 16:09:13 +00:00

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.