proxmox-mirrors/fwupd
1
0
Fork 0
mirror of https://git.proxmox.com/git/fwupd synced 2025-05-09 13:42:49 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
0cc06f032c
fwupd/plugins/ebitdo
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 Updated: Add support for 8BitDo M30. 2019-04-09 12:38:24 -04:00
ebitdo.quirk Add N30 Pro 2 gamepad 2021-06-04 06:44:32 -05:00
fu-ebitdo-common.c ebitdo: Modernize the plugin to use FuFirmware 2019-10-31 09:21:35 -05:00
fu-ebitdo-common.h ebitdo: Modernize the plugin to use FuFirmware 2019-10-31 09:21:35 -05:00
fu-ebitdo-device.c Split up FuUsbDevice into ->open() and ->setup() 2021-06-17 16:21:41 +01:00
fu-ebitdo-device.h trivial: fixup includes for a variety of plugins 2021-06-14 10:12:45 +01:00
fu-ebitdo-firmware.c trivial: fixup includes for a variety of plugins 2021-06-14 10:12:45 +01:00
fu-ebitdo-firmware.h trivial: fixup includes for a variety of plugins 2021-06-14 10:12:45 +01:00
fu-plugin-ebitdo.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 trivial: Use new 8BitDo name 2021-05-24 08:59:54 +01:00

README.md

8BitDo Support

Introduction

This plugin can flash the firmware on the 8BitDo game pads.

Ebitdo support is supported directly by this project with the embedded libebitdo library and is possible thanks to the vendor open sourcing the flashing tool.

The 8BitDo devices share legacy USB VID/PIDs with other projects and so we have to be a bit careful to not claim other devices as our own.

Firmware Format

The daemon will decompress the cabinet archive and extract a firmware blob in an unspecified binary file format. The binary file has a vendor-specific header that is used when flashing the image.

This plugin supports the following protocol ID:

  • com.8bitdo

GUID Generation

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

  • USB\VID_2DC8&PID_AB11&REV_0001
  • USB\VID_2DC8&PID_AB11
  • USB\VID_2DC8

Update Behavior

The device usually presents in runtime mode, but on detach re-enumerates with a different USB VID and PID in a bootloader mode. On attach the device again re-enumerates back to the runtime 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:0x2DC8
  • USB:0x0483
  • USB:0x1002
  • USB:0x1235
  • USB:0x2002
  • USB:0x8000

External interface access

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