Go to file
Richard Hughes b6f79556f1 Use a SHA1 hash for the internal DeviceID
It's actually less scary to see a SHA1 hash than it is to see a path like
/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.2. It's also way easier to
copy and paste into the various fwupdmgr command that require a device ID and
also means we can match a partial prefix much like git allows.

If we also move to a model where plugins can be changed during different stages
of the update (e.g. during detach) then the device might change connection type
and then the sysfs path not only becomes difficult to paste, but incorrect.

Session software doesn't care about the format of the device ID (it is supposed
to be an implementation detail) and so there's no API or ABI break here. A few
plugins also needed to be ported, but nothing too worrying.
2017-11-16 07:18:36 +00:00
.github .github: Add note how to find version before fwupd 0.9.6 2017-11-06 14:17:11 +00:00
.tx trivial: Add some files ready for a first release 2015-03-16 12:51:04 +00:00
contrib Add a nitrokey plugin 2017-11-13 16:25:46 +00:00
data trivial: Use the runtime GUID for the SFC30 gamepad in the hardware tests 2017-11-14 16:01:12 +00:00
docs Set environment variables to allow easy per-plugin debugging 2017-11-14 14:22:02 +00:00
libfwupd trivial: Clarify two gtk-doc comments to explain the flags better 2017-11-11 21:06:14 +00:00
plugins Use a SHA1 hash for the internal DeviceID 2017-11-16 07:18:36 +00:00
po Release fwupd 1.0.1 2017-11-09 15:19:58 +00:00
policy trivial: Ensure the polkit rules always get installed into datadir 2017-11-10 14:31:22 +00:00
src Use a SHA1 hash for the internal DeviceID 2017-11-16 07:18:36 +00:00
.gitignore Add gitignore 2017-10-12 07:02:43 +01:00
.travis.yml contrib/debian: dynamically generate control file 2017-11-07 16:39:28 -06:00
AUTHORS Add initial build files and enough code to launch a simple D-Bus daemon 2015-02-26 18:16:40 +00:00
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md 2017-09-12 15:26:14 +01:00
CONTRIBUTING.md Create CONTRIBUTING.md 2017-09-12 19:37:35 +01:00
COPYING Add initial project files 2015-02-26 13:07:00 +00:00
MAINTAINERS Add initial build files and enough code to launch a simple D-Bus daemon 2015-02-26 18:16:40 +00:00
meson_options.txt Don't run -enable-werror on anything but CI. 2017-10-18 08:20:40 -05:00
meson_post_install.sh Create /var/lib/fwupd by meson post install 2017-04-21 08:07:58 -05:00
meson.build trivial: post release version bump 2017-11-09 15:23:12 +00:00
NEWS Release fwupd 1.0.1 2017-11-09 15:19:58 +00:00
README.md README: Use more secure HTTPS URL for fwupd Web site 2017-11-06 12:29:45 +00:00
RELEASE trivial: post release version bump 2017-11-09 15:23:12 +00:00

fwupd

Build Status Coverity Scan Build Status

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

Additional information is available at the website: http://www.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 (Online updates) will be done immediately.
  • Updates that require a reboot (Offline updates) 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.

Other frontends

Currently GNOME Software is the only 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.

On Dell IoT gateways, Wyse Cloud Client Manager (CCM) has been built with fwupd support. The remote administration interface can be used to download and deploy firmware updates.