Replies: 2 comments 3 replies
-
|
Heu @jyu99. We already have this scenario now, e.g. with VIA chips. The LVFS account for each vendor has a list of vendor-ids it can update (e.g. USB:0x1234) and these can be the same if required.
This is exactly what you need to do, and is completely fine to mix customers in the same quirk fiel. |
Beta Was this translation helpful? Give feedback.
-
|
Since it takes a while to get new quirks into distributions, my suggestion would be to populate the quirk with all the VID/PID that your plugin can support whether or not vendor has LVFS account. That way vendor can create LVFS account and process for CAB asynchronously from fwupd release cadence. Or if we have a way that we can safely probe to determine it's a supportable device we can explore that instead of quirk. Such as other USB descriptor information. |
Beta Was this translation helpful? Give feedback.
-
|
But how to determine the instance id ,if I want to polling all the HID peripheral? use the loosely condition ,e.g. |
Beta Was this translation helpful? Give feedback.
-
|
You're probably right, there isn't a safe way to know unless it was all from Pixart VID. If it uses OEM or ODM VID then you need allow list. |
Beta Was this translation helpful? Give feedback.
-
|
Or if there is anything in USB descriptor even in OEM VID that is pixart specific as a hint? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Our plugin need to support different pid,vid. Scenario as below
We have ODM/OEM customer A, customer B ,etc.. Each ODM/OEM customer pid & vid and could apply unique LVFS account.
How to solve this problem ? Add customer pid and vid to our plugin quirks when we have new customer. or is any better way?
Beta Was this translation helpful? Give feedback.
All reactions