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
125
26 Appendix A: Configuration of Kernels from 3.13 and above
To ensure that the OneBox-Mobile software works on kernel versions from 3.13 and above, some configuration
changes might be needed. These are explained in this section. Super user permissions are needed to make these
changes.
For SDIO mode, ensure that the SDIO stack related modules are already inserted in the kernel.
This can be verified by using the commands below :
cd release
sh load_stack.sh
lsmod
Verify that the output of the "lsmod" command should describe sdhci.ko, sdhci_pci.ko (Specific for x86/PC,
others should use their controller specific ko ), mmc_block.ko as well as mmc_core.ko modules. This is a one-time
process and need not be repeated unless the modules are explicitly removed by the user.
26.1 SDIO Stack Options
If SDIO is the interface to the Host processor, it has to be ensured that the SDIO stack related modules are compiled
in the kernel. If the SDIO stack modules are not present, follow the steps below in order to enable SDIO support in
the kernel.
1. Navigate to the Linux kernel source folder. This is usually in /usr/src/kernels/Linux-<kernel-version>
2. Execute the 'make menuconfig' command in order to open the Kernel Configuration menu.
3. Scroll down to the "Device Drivers --->" option and hit Enter.
4. In the new menu, scroll down to the "MMC/SD/SDIO card support --->" option and press 'M' to modularize
the "MMC/SD/SDIO card support" feature and hit Enter.