- 06 Jan, 2017 40 commits
-
-
Mario Limonciello authored
-
Mario Limonciello authored
-
This functionality is required so that AppStream metadata can check the fwupd version, the firmware version, bootloader version or a combination of all three.
-
This allows us to have new markup specified in the MetaInfo or AppStream XML: <requires> <id compare="ge" version="0.8.1">org.freedesktop.fwupd</id> <firmware compare="ge" version="0.1.2"/> </requires> This means that only updates that match these versions will be shown. -
We need to remove the device from the delayed hash table to ensure we don't accidently free the helper when it removed a *second* time.
-
-
-
Also, fix some method prefixes to match the plugin name.
-
-
There might be a better plugin to claim these than the generic fallback.
-
This allows us to reuse the logic in other plugins.
-
-
-
Mario Limonciello authored
-
Mario Limonciello authored
This method will be used in conjunction with other new plugins in the future that will perform online flashes.
-
-
-
-
-
-
-
-
Mario Limonciello authored
commit e34654e1 caused a regression that hotplugging devices no longer worked. Disabling systemd PrivateNetwork confinement resolves this.
-
Mario Limonciello authored
failed to open plugin /usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_dfu.so: failed to open plugin: /usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_dfu.so: undefined symbol: dfu_device_upload
-
Mario Limonciello authored
failed to open plugin /usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_udev.so: failed to open plugin: /usr/lib/x86_64-linux-gnu/fwupd-plugins-2/libfu_plugin_udev.so: undefined symbol: g_udev_device_get_property
-
Mario Limonciello authored
some code (such as libfwupd) still internally refers to provider, but this will need to be more carefully massaged
-
Mario Limonciello authored
-
-
-
-
-
The user will not be notified about firmware security updates all the time they are on battery power. It's better to handle this in the client prompting the user to connect the AC power source.
-
-
If you do not have Unifying hardware you can emulate writing firmware using: $ fu-unifying-tool write file.hex -v --emulate=bootloader-nordic
-
-
This is a large commit that removes all the providers and turns them into plugins. I think having both providers _and_ plugins was super confusing. Plugins are loaded at runtime so you could in theory develop a new plugin without putting it in the fwupd source tree, although there are no installed headers or PC files as I'm not sure it's a good idea at this stage. This commit moves all the per-provider docs, tests, notes, debug dumps and test data to plugin-specific directories -- these also allows the plugin author to "own" more of the source tree so we don't enforce fu- prefixes and the style guide everywhere. This allows us to run the same action on all the plugins in the future, so we could have a prepare(FuPlugin, FuDevice) and cleanup(FuPlugin, FuDevice) run on *all* plugins, so doing an update using one plugin would allow us to work around hardware quirks in other plugins. If I've broken your out-of-tree provider it's trivial to port to the new API with sed and a fixed up build file. If you need help please let me know.
-
-
This will allow us to add further documentation here in the future.
-
-