mirror of
https://git.proxmox.com/git/fwupd
synced 2025-05-25 18:44:54 +00:00
![]() It's actually quite hard to build a front-end for fwupd at the moment as you're never sure when the progress bar is going to zip back to 0% and start all over again. Some plugins go 0..100% for write, others go 0..100% for erase, then again for write, then *again* for verify. By creating a helper object we can easily split up the progress of the specific task, e.g. write_firmware(). We can encode at the plugin level "the erase takes 50% of the time, the write takes 40% and the read takes 10%". This means we can have a progressbar which goes up just once at a consistent speed. |
||
---|---|---|
.. | ||
fu-plugin-system76-launch.c | ||
fu-system76-launch-device.c | ||
fu-system76-launch-device.h | ||
meson.build | ||
README.md | ||
system76-launch.quirk |
System76 Launch
Introduction
This plugin is used to detach the System76 Launch device to DFU mode.
To switch to bootloader mode a USB packet must be written, as specified by the System76 EC protocol.
GUID Generation
These devices use the standard USB DeviceInstanceId values, e.g.
USB\VID_3384&PID_0001&REV_0001
Update Behavior
The device usually presents in runtime mode, but on detach re-enumerates with a
different USB VID and PID in DFU mode. The device is then handled by the dfu
plugin.
On DFU attach the device again re-enumerates back to the runtime mode.
For this reason the REPLUG_MATCH_GUID
internal device flag is used so that
the bootloader and runtime modes are treated as the same device.
Vendor ID Security
The vendor ID is set from the USB vendor, in this instance set to USB:0x3384
External Interface Access
This plugin requires read/write access to /dev/bus/usb
.