Steps/Question about moving FW update to fwupd #7212
Replies: 1 comment
-
If you haven't already, you should read over the plugin tutorial:
Sounds reasonable. You can add a dummy sysfs to your driver to POC how it would work and allow you to do the fwupd plugin in parallel.
As I mentioned in the other thread I think this could mostly model off of how the "amd-gpu" plugin works. We have a quirk file in the plugin that will make sure that it runs anytime a device is bound with the The constructed callback for the plugin will make sure that matching udev events come to the plugin.
The instance ID is built off of whatever you use to identify the hardware. If you have unique PCI IDs for each stream of CV firmware you can use those. For example on my system I have some devices that make the instance IDs and GUIDs this way:
If you need to add another attribute into the instance ID you can based of whatever you want. The plugin I linked showed using libdrm to get it:
It can just as well be a string from a sysfs attribute or any other API.
This is putting the cart before the horse, you should work out how the plugin should work, and then you can use |
Beta Was this translation helpful? Give feedback.
-
This is a continuous discussion from https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/207
I'm looking into a way to build a simple bare-minimal prototype (seleton) for Intel CV FW device update solution to show case the solution.
To start with, I'll
To build and test a bare-minimal environment, I'd like to do it without LFVS, by running
"fwupdtool --verbose --plugins intel-cvs install-blob /tmp/cvs-firmware.bin $CVS_DEVICE_ID", is this correct?
Also, two other questions,
Beta Was this translation helpful? Give feedback.
All reactions