![]() 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. |
||
---|---|---|
.. | ||
bcm57xx.quirk | ||
fu-bcm57xx-common.c | ||
fu-bcm57xx-common.h | ||
fu-bcm57xx-device.c | ||
fu-bcm57xx-device.h | ||
fu-bcm57xx-dict-image.c | ||
fu-bcm57xx-dict-image.h | ||
fu-bcm57xx-firmware.c | ||
fu-bcm57xx-firmware.h | ||
fu-bcm57xx-recovery-device.c | ||
fu-bcm57xx-recovery-device.h | ||
fu-bcm57xx-stage1-image.c | ||
fu-bcm57xx-stage1-image.h | ||
fu-bcm57xx-stage2-image.c | ||
fu-bcm57xx-stage2-image.h | ||
fu-plugin-bcm57xx.c | ||
fu-self-test.c | ||
meson.build | ||
README.md |
BCM57xx
Introduction
This plugin updates BCM57xx wired network adaptors from Broadcom using a reverse-engineered flashing protocol. It is designed to be used with the clean-room reimplementation of the BCM5719 firmware found here: https://github.com/meklort/bcm5719-fw
Protocol
BCM57xx devices support a custom com.broadcom.bcm57xx
protocol which is
implemented as ioctls like ethtool does.
GUID Generation
These devices use the standard PCI instance IDs, for example:
PCI\VEN_14E4&DEV_1657
PCI\VEN_14E4&DEV_1657&SUBSYS_17AA222E
Update Behavior
The device usually presents in runtime mode, and the firmware is written to the device without disconnecting the working kernel driver. Once complete the APE is reset which may cause a brief link reconnection.
On flash failure the device is nonfunctional, but is recoverable using direct BAR writes, which is typically much slower than updating the device using the kernel driver and the ethtool API.
Vendor ID Security
The vendor ID is set from the PCI vendor, in this instance set to PCI:0x14E4
External Interface Access
This plugin requires the SIOCETHTOOL
ioctl interface.