Linux wireless drivers development
 help / color / mirror / Atom feed
From: Michael Wu <flamingice@sourmilk.net>
To: Hong Liu <hong.liu@intel.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	Jiri Benc <jbenc@suse.cz>,
	linux-wireless@vger.kernel.org
Subject: Re: [patch]mac80211: add support for iwlist channel
Date: Mon, 18 Jun 2007 22:12:51 -0700	[thread overview]
Message-ID: <200706182212.55862.flamingice@sourmilk.net> (raw)
In-Reply-To: <1182156425.15928.7.camel@napa-sdv1.sh.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]

On Monday 18 June 2007 01:47, Hong Liu wrote:
> +static int is_duplicate_channel(struct ieee80211_channel *chan,
> +				struct iw_freq *freq, int count)
> +{
> +	int i;
> +
> +	for (i = 0; i < count; i++, freq++)
> +		if (chan->chan == freq->i)
> +			return 1;
> +
> +	return 0;
> +}
> +
Currently, the only situation in which channels are duplicated is when there's 
an 11g mode registered. The scanning code in ieee80211_sta.c 
(ieee80211_sta_scan_work) checks for this specifically:

(local->hw_modes & local->enabled_modes & (1 << MODE_IEEE80211G) &&
 mode->mode == MODE_IEEE80211B)

MODE_IEEE80211B is skipped if MODE_IEEE80211G is enabled. Modes should be 
skipped instead of channels.

> +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++) {
This looks somewhat awkward. How about something like:

int j = 0;
(check if this mode is disabled or duplicates channels here)
while (j++ < mode->num_channels && c++ < IW_MAX_FREQUENCIES) {

> +			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++;
> +		}
> +	}
> +	range->num_channels = c;
> +	range->num_frequency = c;
> +}
>
>  static int ieee80211_ioctl_giwrange(struct net_device *dev,
>  				 struct iw_request_info *info,
> @@ -1533,6 +1567,8 @@ static int ieee80211_ioctl_giwrange(struct net_device
> *dev, range->enc_capa = IW_ENC_CAPA_WPA | IW_ENC_CAPA_WPA2 |
>  			  IW_ENC_CAPA_CIPHER_TKIP | IW_ENC_CAPA_CIPHER_CCMP;
>
> +	ieee80211_get_supp_channels(local, range);
> +
Should be fine to just put all the logic here. No other code will use that 
function.

-Michael Wu

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-06-19  5:14 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 [this message]
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
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=200706182212.55862.flamingice@sourmilk.net \
    --to=flamingice@sourmilk.net \
    --cc=hong.liu@intel.com \
    --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