![]() It's actually quite hard to build a front-end for fwupd at the moment as you're never sure when the progress bar is going to zip back to 0% and start all over again. Some plugins go 0..100% for write, others go 0..100% for erase, then again for write, then *again* for verify. By creating a helper object we can easily split up the progress of the specific task, e.g. write_firmware(). We can encode at the plugin level "the erase takes 50% of the time, the write takes 40% and the read takes 10%". This means we can have a progressbar which goes up just once at a consistent speed. |
||
---|---|---|
.. | ||
data | ||
fu-plugin-rts54hub.c | ||
fu-rts54hub-device.c | ||
fu-rts54hub-device.h | ||
fu-rts54hub-rtd21xx-background.c | ||
fu-rts54hub-rtd21xx-background.h | ||
fu-rts54hub-rtd21xx-device.c | ||
fu-rts54hub-rtd21xx-device.h | ||
fu-rts54hub-rtd21xx-foreground.c | ||
fu-rts54hub-rtd21xx-foreground.h | ||
meson.build | ||
README.md | ||
rts54hub.quirk |
Realtek RTS54 HUB
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
.