mirror of
https://git.proxmox.com/git/fwupd
synced 2025-06-28 12:22:05 +00:00
![]() This allows us to 'nest' firmware formats, and removes a ton of duplication. The aim here is to deprecate FuFirmwareImage -- it's almost always acting as a 'child' FuFirmware instance, and even copies most of the vfuncs to allow custom types. If I'm struggling to work out what should be a FuFirmware and what should be a FuFirmwareImage then a plugin author has no hope. For simple payloads we were adding bytes into an image and then the image into a firmware. This gets really messy when most plugins are treating the FuFirmware *as* the binary firmware file. The GBytes saved in the FuFirmware would be considered the payload with the aim of not using FuFirmwareImage in the single-image case. |
||
---|---|---|
.. | ||
emmc.quirk | ||
fu-emmc-device.c | ||
fu-emmc-device.h | ||
fu-plugin-emmc.c | ||
meson.build | ||
README.md |
eMMC Support
Introduction
This plugin reads the sysfs attributes corresponding to eMMC devices. It uses the kernel MMC API for flashing devices.
Protocol
eMMC devices support the org.jedec.mmc
protocol.
GUID Generation
These devices use the following instance values:
EMMC\%NAME%
EMMC\%MANFID%&%OEMID%
EMMC\%MANFID%&%OEMID%&%NAME%
Update Behavior
The firmware is deployed when the device is in normal runtime mode, but it is only activated when the device is rebooted.
Vendor ID Security
The vendor ID is set from the EMMC vendor, for example set to EMMC:{$manfid}
External interface access
This plugin requires ioctl MMC_IOC_CMD
and MMC_IOC_MULTI_CMD
access.