Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Sandesh Goel" <sgoel@marvell.com>,
	"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 15:25:10 +0300	[thread overview]
Message-ID: <1ba2fa240706180525i561b0abex6c39d18e7b7b461e@mail.gmail.com> (raw)
In-Reply-To: <1182164508.5924.19.camel@johannes.berg>

On 6/18/07, Johannes Berg <johannes@sipsolutions.net> wrote:
> 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.
>
I have to agree that the phymode lost is relevance. and band channel
couple has more meaning

In this context, what atheros turbo phy mode is? What channel, band
does it operate?

Thanks
Tomas

> johannes
>
>

  reply	other threads:[~2007-06-18 12:25 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 [this message]
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=1ba2fa240706180525i561b0abex6c39d18e7b7b461e@mail.gmail.com \
    --to=tomasw@gmail.com \
    --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