fwupd/plugins/superio
Richard Hughes b333e0045c Split out a shared system context
There is a lot of code in fwupd that just assigns a shared object type to
a FuPlugin, and then for each device on that plugin assigns that same shared
object to each FuDevice.

Rather than proxy several kinds of information stores over two different levels
of abstraction create a 'context' which contains the shared *system* state
between the daemon, the plugins and the daemon.

This will allow us to hold other per-machine state in the future, for instance
the system battery level or AC state.
2021-04-01 21:11:29 +01:00
..
fu-plugin-superio.c Split out a shared system context 2021-04-01 21:11:29 +01:00
fu-superio-common.c Move the file descriptor lifecycle into FuUdevDevice 2019-10-31 09:21:35 -05:00
fu-superio-common.h Only include the start year in the copyright header 2021-01-07 14:48:16 +00:00
fu-superio-device.c superio: Use DeviceInstanceIDs to merge chip quirk metadata 2021-03-03 08:30:34 +00:00
fu-superio-device.h superio: Simplify device setup using the parent_class 2021-02-26 18:46:51 +00:00
fu-superio-it85-device.c superio: Simplify device setup using the parent_class 2021-02-26 18:46:51 +00:00
fu-superio-it85-device.h Only include the start year in the copyright header 2021-01-07 14:48:16 +00:00
fu-superio-it89-device.c trivial: Add fu_device_remove_flag() as a proper symbol 2021-03-31 19:19:46 +01:00
fu-superio-it89-device.h Only include the start year in the copyright header 2021-01-07 14:48:16 +00:00
meson.build Move the plugin build logic to the plugins themselves 2021-02-18 14:46:20 +00:00
README.md trivial: Codespell fixes 2021-03-19 16:42:33 +00:00
superio.quirk Updated StarLabs guids 2021-03-04 17:56:43 +00:00

SuperIO

This plugin enumerates the various ITE85* SuperIO embedded controller ICs found in many laptops. Vendors wanting to expose the SuperIO functionality will need to add a HwId quirk entry to superio.quirk.

See https://en.wikipedia.org/wiki/Super_I/O for more details about SuperIO and what the EC actually does.

Other useful links:

GUID Generation

These devices use a custom GUID generated using the SuperIO chipset name:

  • SuperIO-$(chipset), for example SuperIO-IT8512

Update Behavior

The firmware is deployed when the device is in normal runtime mode, but it is only activated on machine reboot. The firmware write is normally scheduled to be done very early in the boot process to minimize the chance the EC chip locking up if the user is actually using the kerboard controller.

Vendor ID Security

The vendor ID is set from the baseboard vendor, for example DMI:Star Labs

External interface access

This plugin requires access to raw system memory via inb/outb.