![]() This allows us to 'nest' firmware formats, and removes a ton of duplication. The aim here is to deprecate FuFirmwareImage -- it's almost always acting as a 'child' FuFirmware instance, and even copies most of the vfuncs to allow custom types. If I'm struggling to work out what should be a FuFirmware and what should be a FuFirmwareImage then a plugin author has no hope. For simple payloads we were adding bytes into an image and then the image into a firmware. This gets really messy when most plugins are treating the FuFirmware *as* the binary firmware file. The GBytes saved in the FuFirmware would be considered the payload with the aim of not using FuFirmwareImage in the single-image case. |
||
---|---|---|
.. | ||
data | ||
fu-plugin-rts54hub.c | ||
fu-rts54hub-device.c | ||
fu-rts54hub-device.h | ||
fu-rts54hub-rtd21xx-device.c | ||
fu-rts54hub-rtd21xx-device.h | ||
meson.build | ||
README.md | ||
rts54hub.quirk |
Realtek RTS54 HUB Support
Introduction
This plugin allows the user to update any supported hub and attached downstream ICs using a custom HUB-based flashing protocol. It does not support any RTS54xx device using the HID update protocol.
Other devices connected to the RTS54xx using I2C will be supported soon.
Firmware Format
The daemon will decompress the cabinet archive and extract a firmware blob in an unspecified binary file format.
This plugin supports the following protocol IDs:
- com.realtek.rts54
- com.realtek.rts54.i2c
GUID Generation
These devices use the standard USB DeviceInstanceId values, e.g.
USB\VID_0BDA&PID_5423&REV_0001
USB\VID_0BDA&PID_5423
USB\VID_0BDA
Update Behavior
The firmware is deployed when the device is in normal runtime mode, and the device will reset when the new firmware has been written.
Vendor ID Security
The vendor ID is set from the USB vendor, in this instance set to USB:0x0BDA
External interface access
This plugin requires read/write access to /dev/bus/usb
.