From: Johannes Berg <johannes@sipsolutions.net>
To: Luis Carlos Cobo <luisca@cozybit.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 04/13] o11s: various definitions and support functions for mesh interfaces
Date: Thu, 07 Feb 2008 01:21:57 +0100 [thread overview]
Message-ID: <1202343717.9965.52.camel@johannes.berg> (raw)
In-Reply-To: <47a7826d.08102c0a.1d2c.ffff96d2@mx.google.com> (sfid-20080204_212413_136777_9A62E0BA)
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
> key.o \
> util.o \
> - event.o
> + event.o \
> + mesh.o \
> + mesh_pathtbl.o \
> + mesh_plinktbl.o \
> + mesh_plinkfsm.o \
> + mesh_hwmp.o
Since this is a lot of code, any opinion on making it build-time
conditional? I can imagine that you don't want mesh when building an
embedded AP device.
> @@ -358,6 +366,10 @@ static int ieee80211_stop(struct net_device *dev)
> + case IEEE80211_IF_TYPE_MESH_POINT:
> + sdata->u.sta.state = IEEE80211_DISABLED;
> + flush_mesh_interface(dev);
> + /* fall through */
> case IEEE80211_IF_TYPE_STA:
> case IEEE80211_IF_TYPE_IBSS:
> sdata->u.sta.state = IEEE80211_DISABLED;
Setting the state twice seems a bit odd.
> + } else if (sdata->vif.type == IEEE80211_IF_TYPE_MESH_POINT) {
> + /* SSID is wildcard (all 0s) */
> + ieee80211_set_mesh_beacon_template(dev, &conf);
> + local->hw.flags |= IEEE80211_HW_HOST_GEN_BEACON_TEMPLATE;
> + local->hw.conf.beacon_int = 100;
> + ieee80211_start_mesh(dev);
I already mentioned how that is wrong. Let me know if you need any more
info/help.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2008-02-07 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 18:55 [PATCH 04/13] o11s: various definitions and support functions for mesh interfaces Luis Carlos Cobo
2008-02-07 0:21 ` Johannes Berg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1202343717.9965.52.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luisca@cozybit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox