Lines Matching refs:in
4 All hardware and driver dependent functionality is in separate C files
9 Driver wrappers need to implement whatever calls are used in the
11 devices. As an example, in case of Linux, these are mostly some glue
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.
21 defined in \ref driver.h. These functions are registered by filling struct
26 documented in \ref driver.h. In addition, a pointer to the 'struct
27 \ref wpa_driver_ops' needs to be registered in \ref drivers.c file.
36 without very good reasons in order to limit the number of changes
39 make them in backwards compatible way that allows existing driver
42 Generic Linux Wireless Extensions functions are implemented in
45 specific functions are implemented in separate C files, e.g.,
47 entry that will be used in \ref wpa_supplicant.c when calling driver
48 functions. struct \ref wpa_driver_ops entries are registered in \ref drivers.c.
63 of these need to be implemented in order to provide enough support for
76 implementation of both encryption protocols is also available in Host
79 be used in Linux drivers.
91 (ap_scan=1 mode in configuration). This means that the driver should
98 this was added in WE-18. With older versions, a custom event can be used
100 string that is included in the scan results.
118 provided to the driver interface in the associate call. This does not
123 selected cipher and key management suites in the associate call. If
126 about the used WPA IE (i.e., the one it used in (Re)Associate
136 details are defined in \ref driver.h (\ref wpa_supplicant_event() function
144 Michael MIC failure event was added in WE-18. Older versions of Wireless