Jakub Kicinski <kuba@xxxxxxxxxx> writes: >> In order to address scenario#1, a fallback method that loads the FW from >> the older path(/atmel) can be added in the driver. I think that change >> will make it compatible for scenario#1. >> Please suggest, if there is a generic/recommended approach to handle >> backward compatibility for FW path change. > > I'm afraid you need to request from both new and old patch for some > time. Push the change to linux-firmware, but make driver be compatible > with both for maybe three full releases? Then the risk of someone still > having stale linux-firmware goes down quite a bit. I would say at least minimum of two years, preferably more to make it possible to upgrade kernel on LTS distro releases. > TBH renaming FW paths, much like renaming drivers is usually more risk > than reward. I agree, it's just extra work without no actually benefit. Maybe an exception here is iwlwifi, that should be fixed as that clutters the top level firmware directory with dozens of files: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/ -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
