Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / third_party / fwupd / refs/heads/firmware-servo-12768.B
commit9ef051f84b4ad6f9c9d55b743614d8556b182011[log] [tgz]
authorMario Limonciello <mario.limonciello@dell.com>Tue Nov 19 16:30:32 2019 -0600
committerCommit Bot <commit-bot@chromium.org>Mon Dec 16 03:53:29 2019 +0000
tree122f518c2b7b2a5a5bf168af3e234eac5438f6df
parentb4c6a12a3755d1b9fe7b27a1b8e5ff0972dbab60 [diff]
UPSTREAM: wacom-raw: Correct HWID support

This support was using the wrong commands to add a HWID and thus
never actually functioned.  Furthermore it's purpose is to pull
the PID out of the bootloader to be able to properly identify
the device when in bootloader mode (as in recovery mode).

When in this state, generate the correct instance IDs for both
possible Wacom VID.  We can't tell which Wacom VID we are in
bootloader mode.

(cherry picked from commit 59970600adc171a183dddb90908e88b73727b832)
Signed-off-by: Crag Wang <crag_wang@dell.com>

Change-Id: I3627b8a32811177af42cc59cc2363a455f9a5f73
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/fwupd/+/1955347
Reviewed-by: Daniel Campello <campello@chromium.org>
Tested-by: Crag Wang <crag_wang@dell.com>
Commit-Queue: Daniel Campello <campello@chromium.org>
3 files changed
tree: 122f518c2b7b2a5a5bf168af3e234eac5438f6df
  1. .circleci/
  2. .github/
  3. .tx/
  4. contrib/
  5. data/
  6. docs/
  7. libfwupd/
  8. plugins/
  9. po/
  10. policy/
  11. snap/
  12. src/
  13. subprojects/
  14. .gitignore
  15. .gitmodules
  16. .lgtm.yml
  17. .travis.yml
  18. AUTHORS
  19. CODE_OF_CONDUCT.md
  20. COMMITMENT
  21. CONTRIBUTING.md
  22. COPYING
  23. MAINTAINERS
  24. meson.build
  25. meson_options.txt
  26. meson_post_install.sh
  27. OWNERS
  28. README.chromium
  29. README.md
  30. RELEASE
  31. 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.