Lenovo systems that offer a BIOS setting for ThunderboltAccess will
use this option to control whether the IOMMU is enabled by default
or not.
It may be counter-intuitive; but as there are other more physically
difficult to attack PCIe devices it's better to have the IOMMU
enabled pre-boot even if it enables access to Thunderbolt/USB4.
Fixes: #5314
The fu_context_load_quirks(FU_QUIRKS_LOAD_FLAG_NO_CACHE) has to be done first,
otherwise fu_context_load_hwinfo() auto-loads the quirk db with the defaults.
Fixes a build failure in Fedora QA.
Explicitly load_hwinfo at start of mtd self test
```
.# Start of mtd tests
.# GLib-GIO-DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
.# XbSilo-DEBUG: attempting to load /tmp/.E94WW1
.# XbSilo-DEBUG: failed to load silo: blob too small
Bail out! FuContext-FATAL-CRITICAL: cannot use HWIDs before calling ->load_hwinfo()
(/usr/libexec/installed-tests/fwupd/mtd-self-test:1758): FuContext-CRITICAL **: 23:27:43.095: cannot use HWIDs before calling ->load_hwinfo()
```
* 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.
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.
* plugins/{flashrom,superio]: Add GUIDs for StarBook Mk VI - Intel
Signed-off-by: Sean Rhodes <sean@starlabs.systems>
* plugins/{flashrom,superio]: Add GUIDs for StarBook Mk VI - AMD
Signed-off-by: Sean Rhodes <sean@starlabs.systems>
* plugins/{flashrom,superio]: Add GUIDs for Byte Mk I - AMD
Signed-off-by: Sean Rhodes <sean@starlabs.systems>
Signed-off-by: Sean Rhodes <sean@starlabs.systems>
