[RFC 2/4] P2P: Handling single channel concurrency
Johannes Berg
johannes
Tue Mar 6 09:49:03 PST 2012
Please submit as text.
>
> diff --git a/wpa_supplicant/p2p_supplicant.c
> b/wpa_supplicant/p2p_supplicant.c
> index 486a551..b870c4e 100644
> --- a/wpa_supplicant/p2p_supplicant.c
> +++ b/wpa_supplicant/p2p_supplicant.c
> @@ -2609,6 +2609,7 @@ static void wpas_p2p_scan_res_join(struct
> wpa_supplicant *wpa_s,
> struct wpa_bss *bss;
> int freq;
> u8 iface_addr[ETH_ALEN];
> + int shared_freq = 0;
>
> eloop_cancel_timeout(wpas_p2p_join_scan, wpa_s, NULL);
>
> @@ -2644,6 +2645,14 @@ static void wpas_p2p_scan_res_join(struct
> wpa_supplicant *wpa_s,
> wpa_printf(MSG_DEBUG, "P2P: Target GO operating frequency "
> "from P2P peer table: %d MHz", freq);
> }
> +
> + if (!(wpa_s->drv_flags & WPA_DRIVER_FLAGS_MULTI_CHANNEL_CONCURRENT)
> &&
> + ((shared_freq = wpa_drv_shared_freq(wpa_s)) > 0) && (shared_freq !=
> freq)) {
> + wpa_msg(wpa_s->parent, MSG_INFO,
> + P2P_EVENT_GROUP_FORMATION_FAILURE "reason=FREQ_CONFLICT");
> + return;
> + }
How about DBus?
johannes
More information about the Hostap
mailing list