On Wed, 23 Nov 2016 10:49:33 +0300 Andrew Rybchenko <arybchenko at solarflare.com> wrote:
> I've tried to explain it above in item (2): > > >>> > > 2. Another Solarflare PMD with in-kernel part (for control operations) > is considered and could be added in the future. Code for data path > should be shared by these two drivers. libefx-based PMD is put into > 'efx' subdirectory to have a space for another PMD and shared code. > > <<< > > So, main reason is to have location for the code shared by two Solarflare > network PMDs. May be it better to relocate when we really have it. > I'm open for other ideas/suggestions. So is this driver dependent on another non-upstream kernel driver to work? Is this documented in docs directory. If it does depend on other non-upstream components, then the default config should disable the driver.
