From: Hong Liu <hong.liu@intel.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: "John W. Linville" <linville@tuxdriver.com>,
Michael Wu <flamingice@sourmilk.net>,
linux-wireless@vger.kernel.org
Subject: Re: [patch]mac80211: add support for iwlist channel
Date: Wed, 20 Jun 2007 10:10:25 +0800 [thread overview]
Message-ID: <1182305425.19178.12.camel@napa-sdv1.sh.intel.com> (raw)
In-Reply-To: <20070619105024.3c6c68e3@griffin.suse.cz>
On Tue, 2007-06-19 at 10:50 +0200, Jiri Benc wrote:
> On Mon, 18 Jun 2007 16:47:05 +0800, Hong Liu wrote:
> > +static void ieee80211_get_supp_channels(struct ieee80211_local *local,
> > + struct iw_range *range)
> > +{
> > + struct ieee80211_hw_mode *mode = NULL;
> > + int c = 0, j;
> > +
> > + list_for_each_entry(mode, &local->modes_list, list) {
> > + for (j = 0;
> > + j < mode->num_channels && c < IW_MAX_FREQUENCIES; j++) {
> > + struct ieee80211_channel *chan = &mode->channels[j];
> > +
> > + if (is_duplicate_channel(chan, range->freq, c))
> > + continue;
> > + range->freq[c].i = chan->chan;
> > + range->freq[c].m = chan->freq * 100000;
> > + range->freq[c].e = 1;
> > + c++;
> > + }
>
> I don't know exactly what results are supposed to be returned by this
> ioctl, but given the fact SIOCSIWFREQ allows only channels with
> the IEEE80211_CHAN_W_SCAN flag set, shouldn't only channels with this
> flag be returned here?
> Thanks,
>
> Jiri
>
What is the meaning of IEEE80211_CHAN_W_SCAN flag? I can't find any
description of this flag.
Thanks,
Hong
next prev parent reply other threads:[~2007-06-20 2:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 8:47 [patch]mac80211: add support for iwlist channel Hong Liu
2007-06-19 5:12 ` Michael Wu
2007-06-20 3:03 ` Hong Liu
2007-06-20 3:24 ` Larry Finger
2007-06-20 7:08 ` Michael Wu
2007-06-21 1:43 ` Hong Liu
2007-06-19 8:50 ` Jiri Benc
2007-06-20 2:10 ` Hong Liu [this message]
2007-06-20 9:55 ` Jiri Benc
2007-06-20 17:43 ` James Ketrenos
2007-06-20 16:25 ` Jiri Benc
2007-06-20 18:19 ` James Ketrenos
2007-06-20 17:05 ` Jiri Benc
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=1182305425.19178.12.camel@napa-sdv1.sh.intel.com \
--to=hong.liu@intel.com \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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