Re: Using compat-drivers conflicts with kernel mac80211 and cfg80211

[JoSH Lehan <krellan@gmail.com>]

On 05/11/2013 12:35 AM, Arend van Spriel wrote:
> On 05/11/2013 02:52 AM, JoSH Lehan wrote:
> Luis may correct me, but I think you are correct. compat-drivers
> provides a compat.ko which is the glue between new drivers and your
> kernel. With the new drivers you get new features provided you have new
> mac80211/cfg80211 as well. Hence the glue is between wireless modules
> (including mac80211/cfg80211) and rest of your kernel. On a non-embedded
> system the compat-driver modules are installed in a separate folder
> /lib/modules/<your_kernel_version/updates. depmod is run during the
> install in which this folder takes precedence.

Thanks!  So, I'll need to maintain two sets of mac80211/cfg80211
modules: one for drivers that were compiled along with the kernel, and
another for drivers that were compiled as part of the compat-drivers
package.

> Not sure what your use-case is. You have a system in which different
> wireless devices may be plugged in or ...?

Yes.  It's an embedded system, however, it has an exposed USB port and
the user is free (within reason) to plug in a USB device.  I'm trying to
add support for as many USB wireless adapters that I can find.  For some
adapters (such as vt6656 and rtl8712), I use the vendor's tarball (which
compiles directly against the kernel).  So, this is why I need to mix
and match drivers compiled against the kernel's mac80211/cfg80211 with
drivers compiled against the mac80211/cfg80211 from compat.

> Probably not, provided you build it for your kernel version.

Thanks.  Everything's being built for the same version, which is good.
It all compiles and loads OK.  The problem is when the drivers are
actually used, then they oops.

> Depends what you call an embedded system. We used it to run our driver
> on Android. Just cross-compiling it and install it on the system is what
> we did. Recently, there have been a number of people walking that path
> and contacting us. It may be an idea to have a compat-drivers feature to
> generate Android tarballs as it is always running a few kernel versions
> behind mainline.

I'm just running the upstream Linux from kernel.org, not Android.  Good
to see you supporting Android, though.  Thanks for your help!

Josh Lehan