From: Johannes Berg <johannes@sipsolutions.net>
To: Richard Farina <sidhayn@gmail.com>
Cc: Kalle Valo <kalle.valo@iki.fi>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: report operating frequency rather than current
Date: Tue, 05 May 2009 20:57:29 +0200 [thread overview]
Message-ID: <1241549849.4969.1.camel@johannes.local> (raw)
In-Reply-To: <1241549389.4969.0.camel@johannes.local>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
On Tue, 2009-05-05 at 20:49 +0200, Johannes Berg wrote:
> On Tue, 2009-05-05 at 14:32 -0400, Richard Farina wrote:
>
> > To be honest, I would be perfectly happy with this patch if something
> > like a scanning "flag" were to be show in the output if that is what is
> > happening. I don't so much need to see the current channel (when in sta
> > mode at least) as I need to know that the card is scanning if it is not
> > currently on the channel the AP is on. I'd be very happy to simply see
> > it say "scanning" next to the channel or some such when this occurs.
>
> Except that's totally not possible with wext.
Also, again, it is impossible in practise to do that for all cards since
fullmac cards might be bg scanning without telling the host.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-05-05 18:58 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 [this message]
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=1241549849.4969.1.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=kalle.valo@iki.fi \
--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