mirror of https://git.proxmox.com/git/fwupd synced 2025-06-27 08:11:55 +00:00

History

Mario Limonciello d5585728a2 trivial: don't refer to plugindir in the build system anymore		2022-09-28 15:12:10 -05: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: try harder to make sure mtdram is set up	2022-09-07 08:24:10 -05:00
meson.build	trivial: don't refer to plugindir in the build system anymore	2022-09-28 15:12:10 -05:00
mtd.quirk	mtd: expose Pine64 PinePhone Pro MTD as Tow-Boot	2022-09-12 14:51:14 +01:00
README.md	mtd: Use the correct uSWID child for multiple coSWID children	2022-04-18 17:48:52 +01:00

README.md

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.