fwupd/plugins/system76-launch
Richard Hughes b3f9841924 Support more than one protocol for a given device
Devices may want to support more than one protocol, and for some devices
(e.g. Unifying peripherals stuck in bootloader mode) you might not even be able
to query for the correct protocol anyway.
2021-03-01 16:14:36 +00:00
..
fu-plugin-system76-launch.c system76-launch: Add a plugin for the System76 Launch Configurable Keyboard 2021-01-23 20:28:16 +00:00
fu-system76-launch-device.c Support more than one protocol for a given device 2021-03-01 16:14:36 +00:00
fu-system76-launch-device.h system76-launch: Add a plugin for the System76 Launch Configurable Keyboard 2021-01-23 20:28:16 +00:00
meson.build system76-launch: Prompt for unlock keypress if reset command is blocked 2021-02-25 12:37:24 -06:00
README.md Add a new internal flag to opt-in to GUID matching 2021-02-25 15:47:25 +00:00
system76-launch.quirk system76-launch: Add a plugin for the System76 Launch Configurable Keyboard 2021-01-23 20:28:16 +00:00

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.