fwupd/plugins/system76-launch
Richard Hughes 99df74f0c2 Add API to wait for a device
This allows us to ignore all the delays when the device is emulated, with the
idea being to do dozens of device emulations in the CI tests.

Also, do not call fu_progress_sleep() when the device is emulated.
2023-02-01 09:42:08 +00:00
..
fu-system76-launch-device.c Add API to wait for a device 2023-02-01 09:42:08 +00:00
fu-system76-launch-device.h trivial: reformat the whole tree to match new format 2021-08-24 11:18:40 -05:00
fu-system76-launch-plugin.c Build many more plugins as builtin 2022-09-28 17:01:23 +01:00
fu-system76-launch-plugin.h Build many more plugins as builtin 2022-09-28 17:01:23 +01:00
meson.build Build many more plugins as builtin 2022-09-28 17:01:23 +01:00
README.md Add System76 launch_heavy_1 2023-01-12 09:09:12 +00:00
system76-launch.quirk Add System76 launch_heavy_1 2023-01-12 09:09:12 +00:00

title: Plugin: 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
  • USB\VID_3384&PID_0005&REV_0001
  • USB\VID_3384&PID_0006&REV_0001
  • USB\VID_3384&PID_0007&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.