fwupd/plugins/mtd
Richard Hughes 6e34a90a12 trivial: Add FuProgress to fu_context_load_hwinfo()
TIL: fu_bios_settings_setup() takes over 50ms (10%!) at startup.
2023-01-30 14:47:44 +00:00
..
tests mtd: Use dummy SMBIOS data to fix self test on s390x 2023-01-04 07:24:01 -06:00
fu-mtd-device.c Load coSWID metadata from a uSWID MTD block device 2022-09-07 16:02:27 +01:00
fu-mtd-device.h Add a new plugin to handle MTD devices 2021-11-05 20:01:51 +00:00
fu-mtd-plugin.c Build many more plugins as builtin 2022-09-28 17:01:23 +01:00
fu-mtd-plugin.h Build many more plugins as builtin 2022-09-28 17:01:23 +01:00
fu-self-test.c trivial: Add FuProgress to fu_context_load_hwinfo() 2023-01-30 14:47:44 +00:00
meson.build mtd: Use dummy SMBIOS data to fix self test on s390x 2023-01-04 07:24:01 -06:00
mtd.quirk igsc: Add a plugin to update some Intel discrete graphics cards 2022-11-03 13:43:54 +00:00
README.md Include the plugin README text in the generated docs 2023-01-10 14:58:30 +00:00

title: Plugin: MTD

Introduction

The Memory Technology Device (MTD) interface is a way of abstracting flash devices as if they were normal block devices.

See http://www.linux-mtd.infradead.org/doc/general.html for more details.

This plugin supports the following protocol ID:

  • org.infradead.mtd

GUID Generation

These devices use custom DeviceInstanceId values built from the device NAME and DMI data, e.g.

  • MTD\NAME_Factory
  • MTD\VENDOR_foo&NAME_baz
  • MTD\VENDOR_foo&PRODUCT_bar&NAME_baz

If the FirmwareGType quirk is set for the device then the firmware is read back from the device at daemon startup and parsed for the version number. In the event the firmware has multiple child images then the device GUIDs are used as firmware IDs.

Update Behavior

The MTD device is erased in chunks, written and then read back to verify.

Vendor ID Security

The vendor ID is set from the system vendor, for example DMI:LENOVO

External Interface Access

This plugin requires read/write access to /dev/mtd.