fwupd/docs
Richard Hughes 9c028f06b5 Move the database of supported devices out into runtime loaded files
When fwupd is installed in long-term support distros it's very hard to backport
new versions as new hardware is released.

There are several reasons why we can't just include the mapping and quirk
information in the AppStream metadata:

 * The extra data is hugely specific to the installed fwupd plugin versions
 * The device-id is per-device, and the mapping is usually per-plugin
 * Often the information is needed before the FuDevice is created
 * There are security implications in allowing plugins to handle new devices

The idea with quirks is that the end user can drop an additional (or replace
an existing) file in a .d director with a simple format and the hardware will
magically start working. This assumes no new quirks are required, as this would
obviously need code changes, but allows us to get most existing devices working
in an easy way without the user compiling anything.

This allows us to fix issues like https://github.com/hughsie/fwupd/issues/265
2017-11-02 19:08:51 +00:00
..
libfwupd Move the database of supported devices out into runtime loaded files 2017-11-02 19:08:51 +00:00
architecture-plan.svg Automatically download metadata using fwupdmgr if required 2015-07-20 16:19:20 +01:00
dfu-metadata-store.md trivial: Add actual example in the DFU metadata spec document 2015-12-08 08:59:29 +00:00
meson.build trivial: Move the man pages to the source locations 2017-10-09 09:59:52 +01:00