From: Dan Williams <dcbw@redhat.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
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: Sat, 21 Apr 2007 18:19:57 -0400 [thread overview]
Message-ID: <1177193997.19554.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20070421001253.q449myskosg0sg8k@webmail.spamcop.net>
On Sat, 2007-04-21 at 00:12 -0400, Pavel Roskin wrote:
> Quoting Larry Finger <Larry.Finger@lwfinger.net>:
>
> > In ieee80211, the output of scan results lists channels rather than
> > frequencies; however, NetworkManager needs frequency. This patch
> > changes the output from channel to frequency.
>
> The driver can report both, and I think it should. This would make the iwlist
> output a bit longer, but kernel drivers shouldn't be written to make userspace
> program generate pretty output.
I'm trying to remember why NM cares about frequency, and I think it's
for ad-hoc mode; but wpa_supplicant didn't historically support a
"channel" configuration parameter and so you can't create adhoc networks
with NM right now anyway... What's the failure mode?
Dan
> --
> Regards,
> Pavel Roskin
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-04-21 22:16 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 [this message]
2007-04-21 22:55 ` Larry Finger
2007-04-22 22:03 ` Dan Williams
2007-04-22 22:24 ` Larry Finger
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=1177193997.19554.1.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=Larry.Finger@lwfinger.net \
--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).