Lines Matching refs:driver

2 \page driver_wrapper Driver wrapper implementation (driver.h, drivers.c)
4 All hardware and driver dependent functionality is in separate C files
6 of the wpa_supplicant are designed to be hardware, driver, and operating
10 target operating system/driver for controlling wireless LAN
14 Linux Wireless Extensions (in version 18), some driver specific code is used
15 in number of driver interface implementations. These driver dependent parts
16 can be replaced with generic code in \ref driver_wext.c once the target driver
18 least in theory, could use the same driver wrapper code.
20 A driver wrapper needs to implement some or all of the functions
21 defined in \ref driver.h. These functions are registered by filling struct
23 wpa_supplicant will call these functions to control the driver/wlan
24 card. In addition, support for driver events is required. The event
26 documented in \ref driver.h. In addition, a pointer to the 'struct
29 When porting to other operating systems, the driver wrapper should be
31 that some extra requirements for the interface between the driver
34 basis by modifying the interface and updating the other driver
39 make them in backwards compatible way that allows existing driver
43 \ref driver_wext.c. All Linux driver wrappers can use these when the kernel
44 driver supports the generic ioctl()s and wireless events. Driver
47 entry that will be used in \ref wpa_supplicant.c when calling driver
51 of driver interface examples before starting on implementing a new
62 WPA introduces new requirements for the device driver. At least some
70 protocols and thus, the driver will need to be modified to support
77 AP driver (driver/modules/hostap_{tkip,ccmp}.c). In addition, Linux 2.6
81 The driver will also need to provide configuration mechanism to allow
91 (ap_scan=1 mode in configuration). This means that the driver should
94 recommended. The current driver wrapper (\ref driver_wext.c) uses this for
102 wpa_supplicant needs to also be able to request the driver to
103 associate with a specific BSS. Current Host AP driver and matching
112   (this last ioctl will trigger the driver to request association)
118 provided to the driver interface in the associate call. This does not
124 the driver generates its own WPA IE and that differs from the one
125 generated by wpa_supplicant, the driver has to inform wpa_supplicant
128 \ref driver.h). wpa_supplicant is normally configured to use
136 details are defined in \ref driver.h (\ref wpa_supplicant_event() function
145 Extensions will need to use a custom event. Host AP driver used a custom
148 the driver can be moved to use WE-18 mechanism.
157 - driver reports scan complete with wireless event SIOCGIWSCAN
161 - wpa_supplicant configures driver to associate with the selected BSS
167 - wpa_supplicant configures driver to associate with an SSID
174   (Re)AssocReq), driver reports association parameters (AssocReq IEs)
176 - driver reports association with wireless event SIOCGIWAP