From: Kalle Valo <kalle.valo@iki.fi>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Richard Farina <sidhayn@gmail.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: report operating frequency rather than current
Date: Tue, 05 May 2009 08:45:51 +0300 [thread overview]
Message-ID: <87eiv49k6o.fsf@litku.valot.fi> (raw)
In-Reply-To: <20090504181357.GA19022@tuxdriver.com> (John W. Linville's message of "Mon\, 4 May 2009 14\:13\:57 -0400")
"John W. Linville" <linville@tuxdriver.com> writes:
>> 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.
>
> I can see what you mean, but I think showing seemingly random
> fluctuations in channel assignments is at best distracting. Don't you
> agree that most people are more interested in seeing the configuration
> state than the transient state of the hardware?
I agree, it's very distracting. And while doing mac80211 software scan
the device is on a channel approximately 30 ms with queues stopped, so
no data is transfered at that time. I don't see any benefit from
reporting this value to user space: "Hey, I'm on channel 5 now but by
the time to you read this I will be on channel 6 already."
If people want to follow how mac80211 changes the frequency during scan,
the proper way is to add debug messages for op_config() calls. I saw
that Johannes was already working on that.
--
Kalle Valo
next prev parent reply other threads:[~2009-05-05 5:45 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 [this message]
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
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=87eiv49k6o.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=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