On Wed, 2013-02-27 at 09:06 +0100, Marco Porsch wrote:
> >> struct ieee802_11_elems;
> >> struct ieee80211_mesh_sync_ops {
> >> - void (*rx_bcn_presp)(struct ieee80211_sub_if_data *sdata,
> >> - u16 stype,
> >> - struct ieee80211_mgmt *mgmt,
> >> - struct ieee802_11_elems *elems,
> >> - struct ieee80211_rx_status *rx_status);
> >> + void (*rx_bcn)(struct sta_info *sta,
> >> + struct ieee80211_mgmt *mgmt,
> >> + struct ieee802_11_elems *elems,
> >> + u64 t_r);
> >
> > Why not continue to sync against probe responses?
> > mesh_neighbour_update() gets these as well.
>
> Because there was a comment about the standard mentioning only beacon
> frames. Fooled me here =/
> Now I see that the standard explicitly mentions probe responses as well.
> Is the sync code currently ready to handle probe responses? I am not
> perfectly sure about the sta->t_offset_setpoint stuff.
I'm going to drop these patches until you figure this out and tell me
otherwise.
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
