mirror of
https://git.proxmox.com/git/fwupd
synced 2025-06-05 05:37:36 +00:00
fc8093626c
If a device reports that qmi-pdc is supported (e.g. DW5821e that supports both fastboot and qmi-pdc), we'll end up first running the fastboot installation before doing the qmi-pdc installation procedure. These changes also make sure that the MM device inhibition is kept for as long as the whole process is ongoing. Only after the last method is run, the inhibition will be removed. In order to handle devices being exposed in the system while the MM inhibition is in place, e.g. to be able to run qmi-pdc after fastboot, a simple udev based watcher is included, which will take care of creating the FuMmDevice that is not associated to any modem currently exposed by MM, but that shares all the details of the original device. This new logic assumes that the devices don't change their USB layout during a firmware upgrade, which is not a very good assumption, but it works for the case at hand. If this is not the case, we may need to end up doing some custom AT port probing instead of relying on the original one reported by MM being still valid (note that we don't rely on the device name, as that may change if some other device is plugged in the system while we're doing the update, we rely on the USB interface number).
43 lines
1.3 KiB
Markdown
43 lines
1.3 KiB
Markdown
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.
|
|
|