On 6/10/19 11:47 AM, Jakub Kicinski wrote: > It's the kernel that does this, the request_firmware() API. It's > documented in both devlink's and ethtool's API. I was initially > intending to use the file request API directly in devlink, but because > of the requirement to keep compatibility with ethtool that was a no go. > > FWIW you can load from any directory, just prefix the file name > with ../../ to get out of /lib/firmware. > > I guess we could add some logic into devlink user space to detect that > user does not know about this quirk and fix up the path for them.. 🤔
If the user can not load a file based on an arbitrary path, what is the point of the option in the devlink command? You might as well just have the driver use the firmware interface.
