proxmox-mirrors/fwupd
1
0
Fork 0
mirror of https://git.proxmox.com/git/fwupd synced 2025-05-09 15:53:00 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
52441f28a4
fwupd/plugins/modem-manager
History
Richard Hughes 1981c63d58 Remove FuFirmwareImage and just use FuFirmware instead 
This allows us to 'nest' firmware formats, and removes a ton of duplication.

The aim here is to deprecate FuFirmwareImage -- it's almost always acting
as a 'child' FuFirmware instance, and even copies most of the vfuncs to allow
custom types. If I'm struggling to work out what should be a FuFirmware and
what should be a FuFirmwareImage then a plugin author has no hope.

For simple payloads we were adding bytes into an image and then the image into
a firmware. This gets really messy when most plugins are treating the FuFirmware
*as* the binary firmware file.

The GBytes saved in the FuFirmware would be considered the payload with the
aim of not using FuFirmwareImage in the single-image case.
2021-03-09 21:14:12 +00:00
..
fu-mm-device.c Remove FuFirmwareImage and just use FuFirmware instead 2021-03-09 21:14:12 +00:00
fu-mm-device.h Only include the start year in the copyright header 2021-01-07 14:48:16 +00:00
fu-mm-utils.c trivial: Fix a compile error with older versions of gudev 2019-11-02 07:47:02 -05:00
fu-mm-utils.h trivial: Fix a compile error with older versions of gudev 2019-11-02 07:47:02 -05:00
fu-plugin-modem-manager.c Use FWUPD_COMPILATION define to indicate an in tree build 2021-01-22 14:01:25 -06:00
fu-qmi-pdc-updater.c modem-manager: add support for compiling libqmi-glib 1.26.0 and later 2020-06-23 15:21:09 -05:00
fu-qmi-pdc-updater.h trivial: Remove G_BEGIN_DECLS from all private headers 2019-10-09 20:02:16 +01:00
meson.build Move the plugin build logic to the plugins themselves 2021-02-18 14:46:20 +00:00
modem-manager.quirk Simplify the quirk file format 2021-03-03 08:30:34 +00:00
README.md Add a new internal flag to opt-in to GUID matching 2021-02-25 15:47:25 +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

Vendor ID Security

The vendor ID is set from the USB vendor, for example USB:0x413C

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 Protocol: com.google.fastboot

For this reason the REPLUG_MATCH_GUID internal device flag is used so that the fastboot and runtime modes are treated as the same device.

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.

Update protocol: com.qualcomm.qmi_pdc

For this reason the REPLUG_MATCH_GUID internal device flag is used so that the fastboot and runtime modes are treated as the same device.

External interface access

This plugin requires read/write access to /dev/bus/usb.