public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Richard Farina <sidhayn@gmail.com>
Cc: John Linville <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: report operating frequency rather than current
Date: Mon, 04 May 2009 20:15:44 +0200	[thread overview]
Message-ID: <1241460944.8683.92.camel@johannes.local> (raw)
In-Reply-To: <49FF2FE8.8010004@gmail.com>

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

On Mon, 2009-05-04 at 14:11 -0400, Richard Farina wrote:

> Yes, and at what point does it seem like a good idea to hide the channel 
> the wifi card is on?  If I set channel 11 and it is scanning instead of 
> locked on channel 11 then I should see the current channel the hardware 
> is on.  This seems like an aweful idea to me, granted, it may help a few 
> people that don't understand how scanning works, but hiding the truth is 
> never a good idea. NACK.

It's not really about hiding the truth. Besides, many many devices are
_already_ "hiding the truth" (to use your words) because they do
scanning in firmware and you never know what channel they're on (e.g.
all Intel wireless hardware).

I think it's completely pointless for us to reply to the question "what
channel am I on" with the answer "currently the receiver is tuned to
132", when we can say "you're associated to a network on channel 11".

After all, we don't unset the SSID/BSSID when scanning either, even
though we're currently not talking to the AP.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2009-05-04 18:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 15:52 [PATCH] mac80211: report operating frequency rather than current Johannes Berg
2009-05-04 17:50 ` Richard Farina
2009-05-04 18:02   ` Johannes Berg
2009-05-04 18:11     ` Richard Farina
2009-05-04 18:13       ` John W. Linville
2009-05-04 18:53         ` Fabio Rossi
2009-05-04 19:23           ` Luis R. Rodriguez
2009-05-05  5:45         ` Kalle Valo
2009-05-05 18:32           ` Richard Farina
2009-05-05 18:49             ` Johannes Berg
2009-05-05 18:57               ` Johannes Berg
2009-05-04 18:15       ` Johannes Berg [this message]
2009-05-04 18:30         ` Richard Farina
2009-05-04 18:33           ` Luis R. Rodriguez
2009-05-04 18:36             ` Johannes Berg
2009-05-04 18:34           ` Johannes Berg

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=1241460944.8683.92.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sidhayn@gmail.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