From: Johannes Berg <johannes@sipsolutions.net>
To: Sandesh Goel <sgoel@marvell.com>
Cc: David Lamparter <lists@diac24.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: phy mode, channel -> freq mapping (was RE: more nl80211/iw tool code comments)
Date: Mon, 18 Jun 2007 13:01:48 +0200 [thread overview]
Message-ID: <1182164508.5924.19.camel@johannes.berg> (raw)
In-Reply-To: <285925A4DF50FC408669C6302216838D024899@sc-exch02.marvell.com>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
Hi,
> 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.
<phymode stuff snipped>
> I wasn't sure if this has already been thought about. I look forward to
> being educated if I am missing something.
Good point. I hadn't really considered this but a/g or n cards really
make it necessary to distinguish here, and regulatory stuff would also
benefit from defining it that way.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2007-06-18 11:01 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 [this message]
2007-06-18 12:25 ` Tomas Winkler
2007-06-19 4:50 ` Sandesh Goel
2007-06-19 8:59 ` 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=1182164508.5924.19.camel@johannes.berg \
--to=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