linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger@lwfinger.net>
To: Dan Williams <dcbw@redhat.com>
Cc: Pavel Roskin <proski@gnu.org>,
	John Linville <linville@tuxdriver.com>,
	Bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] ieee80211: Output frequency rather than channel in scan  results
Date: Sun, 22 Apr 2007 17:24:05 -0500	[thread overview]
Message-ID: <462BE085.1050906@lwfinger.net> (raw)
In-Reply-To: <1177279412.21205.23.camel@localhost.localdomain>

Dan Williams wrote:
> 
> Haha.  Ok.  NM should be smarter about this and convert channels
> returned by the driver into frequencies.  In the end, I prefer
> frequencies where at all possible, because channel numbers are _not_
> unique (unless you use the the tuple of [standard, band, channel] where
> standard is something like "802.11" or "802.16", band is "a" or "bg").

My current (but not yet accepted) patch for ieee80211 outputs both channel and frequency as does the 
"soon to be submitted" one for mac80211. I agree that frequency is unique; however, I find it easier 
to think in terms of channels. In addition, I only use the bg band and have no confusion. If both 
are listed, everyone should be happy.

Larry

      reply	other threads:[~2007-04-22 22:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-21  4:07 [PATCH] ieee80211: Output frequency rather than channel in scan results Larry Finger
2007-04-21  4:12 ` Pavel Roskin
2007-04-21 22:19   ` Dan Williams
2007-04-21 22:55     ` Larry Finger
2007-04-22 22:03       ` Dan Williams
2007-04-22 22:24         ` Larry Finger [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=462BE085.1050906@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=Bcm43xx-dev@lists.berlios.de \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=proski@gnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).