Hi, Javier,
Before applying the patch, the beacon is based on
adhoc ath_beacon_config_adhoc. But to ensure mesh and ap support in one
single radio, Steve Brown has modified the mesh beaconing using
ath_beacon_config_ap.
Any issues on this?
Regards,
Chun-Yeow
switch (sc->sc_ah->opmode) {
case NL80211_IFTYPE_AP:
+ case NL80211_IFTYPE_MESH_POINT:
if (ath_has_valid_bslot(sc))
ath_beacon_config_ap(sc, cur_conf);
break;
case NL80211_IFTYPE_ADHOC:
- case NL80211_IFTYPE_MESH_POINT:
ath_beacon_config_adhoc(sc, cur_conf);
break;
case NL80211_IFTYPE_STATION:
On Fri, Aug 5, 2011 at 12:06 AM, Javier Cardona <jav...@cozybit.com> wrote:
> On Thu, Aug 4, 2011 at 12:53 AM, Yeoh Chun-Yeow <yeohchuny...@gmail.com>
> wrote:
> > Hi, all,
> > I have tested the OpenWRT platform with compat-wireless-2011-6-22 by
> > creating 1 AP and 1 Mesh in one single radio.
> > It works for ath9k by applying the patches mentioned in:
> > http://www.mail-archive.com/ath9k-devel@lists.ath9k.org/msg06230.html
> > Currently, I manage to setup the 3 nodes with AP+Mesh and all of them can
> > become AP and mesh node at the same time.
>
> Thanks for sharing that info.
>
> > Previously, the ath9k chooses the adhoc beaconing instead of AP
> beaconing,
> > anyone can comment on this?
>
> I'm not sure I understand the question. By "previously" you mean
> before applying the patch? And is this for mesh beacons?
>
> Javier
>
>
> --
> Javier Cardona
> cozybit Inc.
> http://www.cozybit.com
>
_______________________________________________
Devel mailing list
Devel@lists.open80211s.org
http://open80211s.com/mailman/listinfo/devel
