This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

WL18xx driver build with TI build process fails

Specifically, I'm following the build process for the WL18xx (http://processors.wiki.ti.com/index.php/WL18xx_WiFi_Build_Process), down to having set up a workstation with Ubuntu, etc so everything is as step-for-step the same as the directions.

The compat-wireless build fails because the version of compat-wireless which TI is using for the WL18xx is based on a pre 3.10.x kernel - a kernel function prototype changed calling parameters, and so the driver build breaks when using the Kernel (3.12.10 - LINUXEZSDK-AM335X from http://www.ti.com/lsds/ti/tools-software/linux.page which claims to support the WL18xx devices) and compat-wireless, both from links from TI.  I get the distinct impression that the WL18xx driver build process was based on an older kernel release, and then the kernel links were updated and the build not actually re-checked, as the WL18xx build page itself is based on a number of older components.

I'm looking to merge from the kernel.org compat-drivers repo, but expect there may be some issues doing that.

Our project intends to use a recent kernel, so we really do need the build to work with that, and not something much older.

Further, the OpenSSL library used by the build process is 1.0.0d, and should be updated to 1.0.0g (ref: CVE-2014-0160), so that nobody inadvertently deploys with the vulnerable library files, even if Wi-Fi use of the library doesn't expose the vulnerable interface.

It would be beneficial if the drivers and other necessary alterations were contributed directly to the kernel.org repos instead of being based on a copy of the repo from some (seemingly) arbitrary point in time, since they'd then be in lock-step with future kernel releases.  I've had experience with some prior gen ARM processors which were stuck with 2.6.x kernel for a long time because the TI patches were not updated for newer kernels.