Reference Manual
Table Of Contents
- Introduction to RS9116
- Getting Started with RS9116
- Compiling the Driver
- Installing the Driver
- Installation of Modules
- Enabling a Protocol
- Disabling a Protocol
- OneBox-Mobile in Wi-Fi Only Mode
- Installation in Wi-Fi Client Mode (with BSD interface support)
- Installation in Access Point Mode (with BSD interface support)
- Installation in Wi-Fi Client Mode (with NL80211 support)
- Installation in Wi-Fi AP mode (with NL80211 support)
- Installation in Wi-Fi Direct Mode (With BSD Interface Support)
- Installation in Wi-Fi Direct Mode (With NL80211 Support only for Kernel v3.8 or higher)
- OneBox-Mobile in Wi-Fi + Bluetooth LE Coexistence Mode
- Driver Information
- Wi-Fi ioctl Usage Guide
- Configuration Using CFG80211
- Enterprise security using CFG80211
- HOSTAPD and Wi-Fi Protected Setup (WPS)
- ACS with Hostapd
- Antenna Diversity
- Sniffer Mode
- Monitor Mode
- Concurrent Mode
- Background Scan Parameters
- Power save Modes, Profiles and Parameters
- Compliance and Certification
- Wi-Fi Performance Test ioctl usage
- Wake-On-Wireless LAN
- PUF [ Physical Unclonable Functions ]
- GTK Offload
- Steps to connect 802.11R client to AP
- Steps to configure 802.11W
- Update WLAN region based maximum powers from driver
- Bluetooth hcitool and hciconfig Usage
- Android support for RS9116
- Appendix A: Configuration of Kernels from 3.13 and above
- Appendix B: Binary Files for Embedded Platforms
- Appendix C: Using the Bluetooth Manager
- Appendix D: Common Configuration Parameters
- Appendix E: Installation of Missing Generic Netlink Libraries
- Appendix F: Procedure to use latest supplicant with NL80211 interface
- Appendix G: Considerations need to be made during hostapd usage
- RS9116 n-Link Software TRM Revision History
RS9116 n-Link Linux and Android Technical Reference Manual
Version 2.0
August 2019
12
Figure 5: Save the changes before exiting
4. Now to compile the driver, enter the following command:
make
The code is compiled and the binaries are generated in thesource/host/release folder.For embedded
platforms, modify the path assigned to the "DEF_KERNEL_DIR" variable in the Makefile:
cd RS9116.NXX.NL.GEN.LNX.x.y.z/source/host
vim Makefile
The DEF_KERNEL_DIR variable has to be assigned along with the compiled kernel path. For an x86 based
Linux platform, the path is usually
"/lib/modules/<kernel_version>/build"
and this is the path assigned in
the Makefile provided in the package.
Example:
DEF_KERNEL_DIR:= /lib/modules/3.4.66/build
Next, use the "make" command to start compiling the driver. For embedded platforms, add the target
platform and toolchain path as cross compilation option to the "make" command.
For example, if the target platform is ARM and tool chain path is
"/opt/freescale/usr/local/gcc-4.4.4-
glibc-2.11.1-multilib-1.0/arm-fsl-linux-gnueabi/bin/arm-none-linux-gnueabi-"
, then the command is
issued as:
make ARCH=arm CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.4.4-glibc-2.11.1-multilib-1.0/arm-fsl-linux-
gnueabi/bin/arm-none-linux-gnueabi-