proxmox-mirrors/fwupd
1
0
Fork 0
mirror of https://git.proxmox.com/git/fwupd synced 2025-06-05 20:37:17 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
2883b577dc
fwupd/plugins/cros-ec
History
Richard Hughes 5f4e962d02 cros-ec: Mark as signed payload
2022-03-04 19:21:42 +00:00
..
data cros-ec: Initial skeleton 2020-05-29 06:55:40 +01:00
tests Move the fuzzing files into the plugin directories 2021-10-22 15:24:05 +01:00
cros-ec.quirk add new device Belkin docking station : VID050D/PID003F 2021-12-16 11:57:19 +00:00
fu-cros-ec-common.c trivial: reformat the whole tree to match new format 2021-08-24 11:18:40 -05:00
fu-cros-ec-common.h trivial: reformat the whole tree to match new format 2021-08-24 11:18:40 -05:00
fu-cros-ec-firmware.c cros-ec: Add progress completion when writing blocks 2022-01-07 07:24:08 +00:00
fu-cros-ec-firmware.h cros-ec: Add progress completion when writing blocks 2022-01-07 07:24:08 +00:00
fu-cros-ec-usb-device.c cros-ec: Mark as signed payload 2022-03-04 19:21:42 +00:00
fu-cros-ec-usb-device.h trivial: reformat the whole tree to match new format 2021-08-24 11:18:40 -05:00
fu-plugin-cros-ec.c Speed up the daemon startup by ~2% by doing dlsym much less 2021-11-09 12:02:07 +00:00
meson.build Convert build system to use meson tristate features 2022-02-28 08:34:48 -06:00
README.md trivial: update markdown for pre-commit style 2021-07-18 14:42:47 -05:00

README.md

Chrome OS EC

Introduction

This plugin provides support for the firmware updates for Chrome OS EC project based devices.

Initially, it supports the USB endpoint updater, but lays the groundwork for future updaters which use other update methods other than the USB endpoint.

This is based on the chromeos ec project's usb_updater2 application.

Information about the USB update protocol is available here.

Firmware Format

The daemon will decompress the cabinet archive and extract a firmware blob in the Google fmap file format.

This plugin supports the following protocol ID:

  • com.google.usb.crosec

GUID Generation

These devices use the standard USB DeviceInstanceId values, e.g.

  • USB\VID_18D1&PID_501A

Update Behavior

The device usually presents in runtime mode, but on detach re-enumerates with the same USB PID in an unlocked mode. On attach the device again re-enumerates back to the runtime locked mode.

For this reason the REPLUG_MATCH_GUID internal device flag is used so that the bootloader and runtime modes are treated as the same device.

Vendor ID Security

The vendor ID is set from the USB vendor, which is set to various different values depending on the model and device mode. The list of USB VIDs used is:

  • USB:0x18D1

External Interface Access

This plugin requires read/write access to /dev/bus/usb.