From: Fabio Rossi <rossi.f@inwind.it>
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: Mon, 4 May 2009 20:53:18 +0200 [thread overview]
Message-ID: <200905042053.19091.rossi.f@inwind.it> (raw)
In-Reply-To: <20090504181357.GA19022@tuxdriver.com>
On Monday 04 May 2009, John W. Linville wrote:
> On Mon, May 04, 2009 at 02:11:52PM -0400, Richard Farina wrote:
> > Johannes Berg wrote:
> >> Umm, if _you_ set channel 11 then you _will_ see channel 11. It's just
> >> that when it's scanning and happens to be on channel 132 instead of 11,
> >> while you previously set 11, you will _after_ this patch see 11, not
> >> 132.
> >
> > 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 want to report my experience. There was a bug in the ath5k driver with a
hanging result during scanning mode. I was able to discover the problem
thanks to the iwconfig output.
In alternative, is it possible to add a status flag so that iwconfig from user
space can report scanning mode is operative?
Fabio
next prev parent reply other threads:[~2009-05-04 18:54 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 [this message]
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
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=200905042053.19091.rossi.f@inwind.it \
--to=rossi.f@inwind.it \
--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