proxmox-mirrors/fwupd
1
0
Fork 0
mirror of https://git.proxmox.com/git/fwupd synced 2025-07-27 04:04:05 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
81482c3ba7
fwupd/plugins/cros-ec
History
Richard Hughes bf72d393fd Split up FuUsbDevice into ->open() and ->setup() 
Before this change calling FuUsbDevice->open() opened the device, and
also unconditionally added various GUIDs and InstanceIDs which we
normally do in setup.
Then fu_device_setup() would call the FuSubclass->setup() vfunc which
would have no way of either opting out of the FuUsbDevice->setup()-like
behaviour, or controlling if the parent class ->setup is run before or
after the subclass setup.

Split up FuUsbDevice->open() into clear ->open() and ->setup() phases
and add the parent class calls where appropriate.

This means that ->setup() now behaves the same as all the other vfuncs.
2021-06-17 16:21:41 +01:00
..
data cros-ec: Initial skeleton 2020-05-29 06:55:40 +01:00
cros-ec.quirk cros-ec: Add D501 Baklava device support 2021-03-18 14:29:42 -07:00
fu-cros-ec-common.c cros-ec: Parse version number into triplet 2020-05-29 06:55:40 +01:00
fu-cros-ec-common.h trivial: fixup includes for a variety of plugins 2021-06-14 10:12:45 +01:00
fu-cros-ec-firmware.c trivial: fixup includes for a variety of plugins 2021-06-14 10:12:45 +01:00
fu-cros-ec-firmware.h trivial: fixup includes for a variety of plugins 2021-06-14 10:12:45 +01:00
fu-cros-ec-usb-device.c Split up FuUsbDevice into ->open() and ->setup() 2021-06-17 16:21:41 +01:00
fu-cros-ec-usb-device.h trivial: fixup includes for a variety of plugins 2021-06-14 10:12:45 +01:00
fu-plugin-cros-ec.c trivial: fixup includes for a variety of plugins 2021-06-14 10:12:45 +01:00
meson.build Move the plugin build logic to the plugins themselves 2021-02-18 14:46:20 +00:00
README.md Add a new internal flag to opt-in to GUID matching 2021-02-25 15:47:25 +00:00

README.md

Chrome OS EC Support

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 [1].

Information about the USB update protocol is available at [2].

Firmware Format

The daemon will decompress the cabinet archive and extract a firmware blob in the Google fmap [3] 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.

[1] https://chromium.googlesource.com/chromiumos/platform/ec/+/master/extra/usb_updater/usb_updater2.c [2] https://chromium.googlesource.com/chromiumos/platform/ec/+/master/docs/usb_updater.md [3] https://www.chromium.org/chromium-os/firmware-porting-guide/fmap