This was causing the SystemIntegrityOld metadata key to be overwritten and not
included in the upload. It is much better to be explicit rather than using the
default release, which may not be what the user actually upgraded to.
In various places the code was checking if a release was set, but this would
always be false as the release was being auto-created. This was masking valid
bugs, and was confusing to have the superclass have different semantics to the
baseclass.
* elantp: Include 04F3:0400 (bootloader) as a valid i2c-hid touchpad
ELAN Touchpads with product ids between 0x3000 and 0x4000 can sometimes
end up in bootloader mode (due to not having a valid firmware, for
example)
The bootloader has a product id outside of the range checked by
fu_elantp_hid_device_probe, resulting in the device disappearing from
get-devices when it's in that mode, which makes it seem dead.
This expands the range of that check to include 0x400 so that it is
possible to upload a valid firmware to it.
There is no guarantee that Python environment used for the build contains
the same `markdown` version as the one used for running `gi-docgen`.
For example, Nixpkgs uses a self-contained Python environment for the latter,
so `markdown` package is not even available in fwupd build environment.
Fortunately, gi-docgen 2022.2 already checks for `markdown` version
so we can omit our own check for newer gi-docgen versions.
Intel Arc products do not require the host CSME to update Arc firmware.
Firmware updates will work on both AMD and Intel platforms.
Arc products have their own Graphics Security Control for firmware updates and
leverage existing Intel technology like the MEI interface protocol to implement
the firmware update flow.
Signed-off-by: Vitaly Lubart <vitaly.lubart@intel.com>
The use-runtime-version flag was initially used with the Intuos
Pro Small (2nd-gen USB v2) to force the use of the legacy code
path. The legacy code path was required because of a bug in the
identification of the Bluetooth (I6) firmware.
It has been decided that the bug will be fixed before any fimware
changes are released, removing the need to use the legacy code path.
Recently we had an update that changed the system-defined Platform Key, and
we've certainly had updates in the past that changed the Boot#### variables.
Store some core ACPI and UEFI system integrity state from before and after the
update which can be used to mark (waivable) test failures on the LVFS.
