mirror of
https://git.proxmox.com/git/fwupd
synced 2025-05-16 15:51:29 +00:00
![]() Before this change calling FuUsbDevice->open() opened the device, and also unconditionally added various GUIDs and InstanceIDs which we normally do in setup. Then fu_device_setup() would call the FuSubclass->setup() vfunc which would have no way of either opting out of the FuUsbDevice->setup()-like behaviour, or controlling if the parent class ->setup is run before or after the subclass setup. Split up FuUsbDevice->open() into clear ->open() and ->setup() phases and add the parent class calls where appropriate. This means that ->setup() now behaves the same as all the other vfuncs. |
||
---|---|---|
.. | ||
fu-plugin-system76-launch.c | ||
fu-system76-launch-device.c | ||
fu-system76-launch-device.h | ||
meson.build | ||
README.md | ||
system76-launch.quirk |
System76 Launch Support
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
.