Home
last modified time | relevance | path

Searched refs:wrapper (Results 1 – 15 of 15) sorted by relevance

/hostap-latest/tests/hwsim/
Dutils.py321 def cloned_wrapper(wrapper, fn): argument
323 wrapper.__name__ = fn.__name__
324 wrapper.__doc__ = fn.__doc__
326 wrapper.__module__ = fn.__module__
327 return wrapper
330 def wrapper(dev, apdev, params): function
339 return cloned_wrapper(wrapper, fn)
/hostap-latest/doc/
Ddriver_wrapper.doxygen2 \page driver_wrapper Driver wrapper implementation (driver.h, drivers.c)
5 that implement defined wrapper functions. Other parts
18 least in theory, could use the same driver wrapper code.
20 A driver wrapper needs to implement some or all of the functions
29 When porting to other operating systems, the driver wrapper should be
32 wrapper and generic wpa_supplicant code are discovered during porting
94 recommended. The current driver wrapper (\ref driver_wext.c) uses this for
104 \ref driver_hostap.c wrapper uses following sequence for this
Dcode_structure.doxygen65 Layer 2 (link) access wrapper (includes Linux packet socket
115 Definition of crypto library wrapper
130 Definition of TLS library wrapper
133 Stub implementation of TLS library wrapper for cases where TLS
137 TLS library wrapper for openssl
143 TLS library wrapper for GnuTLS
Dporting.doxygen26 Many of the common ANSI C functions are used through a wrapper
40 OS_NO_C_LIB_DEFINES may be defined for the build and the wrapper
41 functions can then be implemented in a new os_*.c wrapper file.
67 projects have to implement a driver wrapper. This may be done by
70 driver_wrapper "Driver wrapper implementation" describes the details
Dp2p.doxygen160 The following driver wrapper functions are needed for P2P in addition
170 The following driver wrapper events are needed for P2P in addition to
/hostap-latest/radius_example/
DREADME29 implementation or alternatively, implement eloop_* wrapper functions
/hostap-latest/wpa_supplicant/
Dtodo.txt69 requiring every TLS wrapper to implement all functions
DREADME463 If the specific driver wrapper is not known beforehand, it is possible
465 line. wpa_supplicant will use the first driver wrapper that is able to
931 enabled, the privileged operations (driver wrapper and l2_packet) are
DChangeLog728 available only with the macsec_qca driver wrapper)
1265 * bsd: Cleaned up driver wrapper and added various low-level
1301 * cleaned up driver wrapper API (struct wpa_driver_ops); the new API
1317 wrapper
1351 * use shared driver wrapper files with hostapd
1362 (this can also be used with a new 'none' driver wrapper if no
1842 wrapper functions defined in os.h and implemented in os_*.c to make
Dandroid.config241 # Select wrapper for operating system and C library specific functions
Ddefconfig290 # Select wrapper for operating system and C library specific functions
/hostap-latest/hostapd/
Dandroid.config156 # Select wrapper for operatins system and C library specific functions
DChangeLog717 * bsd: Cleaned up driver wrapper and added various low-level
723 * cleaned up driver wrapper API for multi-BSS operations
742 * cleaned up driver wrapper API (struct wpa_driver_ops); the new API
751 * remove obsolete Prism54.org driver wrapper
790 * use shared driver wrapper files with wpa_supplicant
858 * added new "driver wrapper" for RADIUS-only configuration
/hostap-latest/wpa_supplicant/doc/docbook/
Dwpa_supplicant.sgml547 <para>If the specific driver wrapper is not known beforehand, it is
550 wrapper that is able to initialize the interface.</para>
/hostap-latest/tests/hwsim/vm/
Dparallel-vm.py545 curses.wrapper(show_progress)