Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / third_party / fwupd / refs/heads/stabilize-13482.B
commit38d8fb5d4535903c3166618a52ef852060fb5726[log] [tgz]
authorMario Limonciello <mario.limonciello@dell.com>Sat Sep 12 15:18:24 2020 -0500
committerCommit Bot <commit-bot@chromium.org>Tue Sep 15 16:19:26 2020 +0000
tree3a5b857fd3b1a712c972feb547ac7d519688be89
parent7913e1d77e80d90070825ad841d8bdf33f87299b [diff]
UPSTREAM: thunderbolt: set install parent first flag for WD19TB

This is only applicable for kernel 5.9 or kernels that backported
the authenticate on disconnect patches.

For installation time this isn't very important since no device will
restart.  This also isn't relevant for the authenticate on disconnect
scenario.
However the manual activation scenario, it's important to activate the
WD19TB device first, followed by Thunderbolt.

(cherry picked from commit 7fc7da3999a3bb0d7e75b4e72993783d82836329)

BUG=b:168152036
TEST=emerge-volteer fwupd; fwupdtool update; fwupdtool activate

Change-Id: I7344cb21a51c96ccdfb90e1cf0f8836cb32bc05e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/fwupd/+/2407168
Reviewed-by: Benson Leung <bleung@google.com>
Reviewed-by: Sean Paul <seanpaul@chromium.org>
Commit-Queue: Daniel Campello <campello@chromium.org>
Tested-by: Daniel Campello <campello@chromium.org>
1 file changed
tree: 3a5b857fd3b1a712c972feb547ac7d519688be89
  1. .circleci/
  2. .github/
  3. .tx/
  4. contrib/
  5. data/
  6. docs/
  7. libfwupd/
  8. libfwupdplugin/
  9. plugins/
  10. po/
  11. policy/
  12. snap/
  13. src/
  14. subprojects/
  15. .gitignore
  16. .gitmodules
  17. .lgtm.yml
  18. .travis.yml
  19. AUTHORS
  20. CODE_OF_CONDUCT.md
  21. COMMITMENT
  22. CONTRIBUTING.md
  23. COPYING
  24. MAINTAINERS
  25. meson.build
  26. meson_options.txt
  27. meson_post_install.sh
  28. OWNERS
  29. README.chromium
  30. README.md
  31. RELEASE
  32. SECURITY.md
README.md

fwupd

Build Status Coverity Scan Build Status

Get it from the Snap Store

This project aims to make updating firmware on Linux automatic, safe and reliable.

Additional information is available at the website: https://fwupd.org/

Compiling

The most up to date compilation instructions are available in the Wiki.

LVFS

This project is configured by default to download firmware from the Linux Vendor Firmware Service (LVFS).

This service is available to all OEMs and firmware creators who would like to make their firmware available to Linux users.

You can find more information about the technical details of creating a firmware capsule in the hardware vendors section of the fwupd website.

Basic usage flow (command line)

If you have a device with firmware supported by fwupd, this is how you will check for updates and apply them using fwupd's command line tools.

# fwupdmgr get-devices

This will display all devices detected by fwupd.

# fwupdmgr refresh

This will download the latest metadata from LVFS.

# fwupdmgr get-updates

If updates are available for any devices on the system, they'll be displayed.

# fwupdmgr update

This will download and apply all updates for your system.

  • Updates that can be applied live will be done immediately.
  • Updates that run at bootup will be staged for the next reboot.

You can find more information about the update workflow in the end users section of the fwupd website.

Reporting status

fwupd will encourage users to report both successful and failed updates back to LVFS. This is an optional feature, but encouraged as it provides valuable feedback to LVFS administrators and OEM developers regarding firmware update process efficacy.

The privacy policy regarding this data can be viewed on the fwupd website.

To report the status of an update run:

# fwupdmgr report-history

To clear the local history of updates:

# fwupdmgr clear-history

Only updates that were distributed from the LVFS will be reported to the LVFS.

Enterprise use

The flow of updates can be controlled in the enterprise using the "approved updates" feature. This allows the domain administrator to filter the possible updates from a central server (e.g. the LVFS, or a mirror) to only firmware that have been tested specifically in your organisation.

The list of approved updates can be enabled by adding ApprovalRequired=true to the remote configuration file, e.g. lvfs.conf. Once enabled, the list of approved updates can be set in daemon.conf using a comma delimited list.

For example:

ApprovedFirmware=foo,bar

Where foo,bar refers to the container checksums that would correspond to two updates in the metadata file.

Additionally, the list of approved firmware can be supplemented using fwupdmgr set-approved-firmware baz or using the D-Bus interface.

Other frontends

  1. GNOME Software is the graphical frontend available. When compiled with firmware support, it will check for updates periodically and automatically download firmware in the background. After the firmware has been downloaded a popup will be displayed in GNOME Software to perform the update.

  2. KDE Discover is the software centre, generally bundled with KDE Plasma. With the release of KDE Plasma 5.14, a new fwupd backend has been implemented in KDE Discover for firmware updates. These firmware updates are shown with other system updates.

  3. Wyse Management Suite A software suite available on Dell IoT gateways and Wyse thin clients with built-in fwupd support. The remote administration interface can be used to download and deploy firmware updates.

Fuzzing

There are several automated fuzzing tests in fwupd. These take some time to run:

CC=afl-gcc meson --default-library=static ../
AFL_HARDEN=1 ninja
ninja fuzz-synaptics-rmi
ninja fuzz-firmware
ninja fuzz-smbios