Home | History | Annotate | Download | only in wpa_supplicant

Lines Matching full:wpa_supplicant

101 	 * the driver has to notify wpa_supplicant about the used WPA
103 * convert into EVENT_ASSOCINFO data (see wpa_supplicant.h).
236 * for core wpa_supplicant code. All driver specific functionality is captured
293 * allow wpa_supplicant to control roaming if ap_scan=1 is used;
335 * some drivers may expect them in different order than wpa_supplicant
348 * @ctx: context to be used when calling wpa_supplicant functions,
363 * The main event loop (eloop.c) of wpa_supplicant can be used to
366 * See wpa_supplicant.h for more information about events and
428 * results event for wpa_supplicant which will eventually request the
516 * in the driver. If the driver uses wpa_ie from wpa_supplicant, this
535 * between the driver and wpa_supplicant. If the driver uses wpa_ie
536 * from wpa_supplicant, this driver_ops function does not need to be
553 * between the driver and wpa_supplicant. If the driver uses wpa_ie
554 * from wpa_supplicant, this driver_ops function does not need to be
672 * (management frame processing) to wpa_supplicant.
687 * (management frame processing) to wpa_supplicant.
700 * (management frame processing) to wpa_supplicant.
711 * (management frame processing) to wpa_supplicant.
723 * (management frame processing) to wpa_supplicant.
737 * (management frame processing) to wpa_supplicant. When the MLME code
752 * (management frame processing) to wpa_supplicant.