proxmox-mirrors/fwupd
1
0
Fork 0
mirror of https://git.proxmox.com/git/fwupd synced 2025-05-30 03:20:56 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
f1c79a8eae
fwupd/plugins/modem-manager
History
Richard Hughes eddaed0c11 Allow specifying more than one VendorID for a device 
Asking the user for the UID mapping isn't working very well, as it requires lots
of manual handholding. It also doesn't work very well when the device vendor
does not actually have a PCI ID or if the vendor has split into two entities.

Just use the OUI address as an additional VendorID and match any of the device
IDs against any of the metadata-supplied values.
2021-01-04 22:30:20 +00:00
..
fu-mm-device.c Allow specifying more than one VendorID for a device 2021-01-04 22:30:20 +00:00
fu-mm-device.h modem-manager: make sure the correct interface number is used for QMI 2020-11-29 07:08:05 +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 modem-manager: udev monitoring only if device switches layout 2020-11-29 07:08:05 +00: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 Convert libfwupdprivate to a shared library libfwupdplugin 2019-11-27 11:32:43 +00:00
modem-manager.quirk Revert "trivial: add Vendor ID into Modem manager devices" 2020-06-23 07:57:22 +01:00
README.md Add external interface messages 2020-10-26 12:05:20 -05: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

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

External interface access

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