fwupd/plugins/dfu-csr
Richard Hughes 2e1245728f Call the superclass directly from subclassed devices
This allows a device subclass to call the parent method after doing an initial
action, or even deliberately not call the *generic* parent method at all.

It also simplifies the plugins; you no longer have to remember what the plugin
is deriving from and accidentally clobber the wrong superclass method.
2021-02-18 16:18:34 +00:00
..
data csr: Rename plugin to dfu-csr as it depends on the prefixed plugin 2021-02-18 14:46:20 +00:00
dfu-csr.quirk csr: Rename plugin to dfu-csr as it depends on the prefixed plugin 2021-02-18 14:46:20 +00:00
fu-dfu-csr-device.c Call the superclass directly from subclassed devices 2021-02-18 16:18:34 +00:00
fu-dfu-csr-device.h csr: Rename plugin to dfu-csr as it depends on the prefixed plugin 2021-02-18 14:46:20 +00:00
fu-plugin-dfu-csr.c csr: Rename plugin to dfu-csr as it depends on the prefixed plugin 2021-02-18 14:46:20 +00:00
meson.build Move the plugin build logic to the plugins themselves 2021-02-18 14:46:20 +00:00
README.md csr: Rename plugin to dfu-csr as it depends on the prefixed plugin 2021-02-18 14:46:20 +00:00

DFU CSR Support

Introduction

CSR is often called “driverless DFU” and is used only by BlueCore chips from Cambridge Silicon Radio (now owned by Qualcomm). The driverless just means that it's DFU like, and is routed over HID.

CSR is a ODM that makes most of the Bluetooth audio chips in vendor hardware. The hardware vendor can enable or disable features on the CSR microcontroller depending on licensing options (for instance echo cancellation), and theres even a little virtual machine to do simple vendor-specific things.

All the CSR chips are updatable in-field, and most vendors issue updates to fix sound quality issues or to add support for new protocols or devices.

Firmware Format

The daemon will decompress the cabinet archive and extract a firmware blob in DFU file format.

This plugin supports the following protocol ID:

  • com.qualcomm.dfu

GUID Generation

These devices use the standard USB DeviceInstanceId values, e.g.

  • USB\VID_0A12&PID_1337&REV_2520
  • USB\VID_0A12&PID_1337
  • USB\VID_0A12

Vendor ID Security

The vendor ID is set from the USB vendor, in this instance set to USB:0x0A12

External interface access

This plugin requires read/write access to /dev/bus/usb.