Linux wireless drivers development
 help / color / mirror / Atom feed
From: Jiri Benc <jbenc@suse.cz>
To: "Sandesh Goel" <sgoel@marvell.com>
Cc: "David Lamparter" <lists@diac24.net>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	"linux-wireless" <linux-wireless@vger.kernel.org>
Subject: Re: phy mode, channel -> freq mapping (was RE: more nl80211/iw tool  code comments)
Date: Tue, 19 Jun 2007 10:59:20 +0200	[thread overview]
Message-ID: <20070619105920.44f170f9@griffin.suse.cz> (raw)
In-Reply-To: <285925A4DF50FC408669C6302216838D024899@sc-exch02.marvell.com>

On Mon, 18 Jun 2007 02:42:01 -0700, Sandesh Goel wrote:
> I have a high level comment on the whole phy mode, channel and frequency
> mapping business.
> 
> I think it is cleaner to define a parameter called BAND which can take
> values 2.4 GHz, 5 GHz and so on. Then, the combination of BAND and
> CHANNEL will uniquely define the operating frequency.

I completely agree. Actually, I thought about this in the past (see my
old patches for ieee80211) but it was not worth the effort to rewrite
mac80211 (as the changes would need to be quite invasive). But now,
with 802.11n, it's probably worth reconsidering.

Thanks,

 Jiri

-- 
Jiri Benc
SUSE Labs

      parent reply	other threads:[~2007-06-19  8:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-13 18:23 more nl80211/iw tool code comments Johannes Berg
2007-06-14 14:29 ` David Lamparter
2007-06-16 12:17   ` Johannes Berg
2007-06-18  9:42   ` phy mode, channel -> freq mapping (was RE: more nl80211/iw tool code comments) Sandesh Goel
2007-06-18 11:01     ` Johannes Berg
2007-06-18 12:25       ` Tomas Winkler
2007-06-19  4:50         ` Sandesh Goel
2007-06-19  8:59     ` Jiri Benc [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=20070619105920.44f170f9@griffin.suse.cz \
    --to=jbenc@suse.cz \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lists@diac24.net \
    --cc=sgoel@marvell.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