On 4/8/21 10:01 AM, Jaroslav Kysela wrote:
When we have a common standard layer for the plug-and-play handling (udev), we
should concentrate to allow changing / refining of this information there.
Those strings are not used for anything else than the user space. So from my
view, there's no reason to create another mechanism to handle the overrides.
It should be a safe, fast, flexible and_optional_ solution. The udev can
alter the sysfs attributes directly without any hassle with the file
modifications or looking for another way to pass / store this information
somewhere.
There's one part where I am lost.
The initial idea of udev what to modify kernel parameters to pick a
different path for firmware/topology before probing the PCI driver. At
that point there is no card and no sysfs attributes just yet, they will
be added at a later point during the probe itself.
So are we talking about a second set of rules that would be applied when
the card is created?
