From: Kalle Valo <kalle.valo@iki.fi>
To: Dan Williams <dcbw@redhat.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Bob Copeland <me@bobcopeland.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, mabbaswireless@gmail.com
Subject: Re: [PATCH v2 0/3] mac80211 suspend/resume
Date: Fri, 09 Jan 2009 18:44:19 +0200 [thread overview]
Message-ID: <878wpktonw.fsf@litku.valot.fi> (raw)
In-Reply-To: <1231518921.30057.14.camel@dhcp-18-190-61-35.dyn.mit.edu> (Dan Williams's message of "Fri\, 09 Jan 2009 11\:35\:21 -0500")
Dan Williams <dcbw@redhat.com> writes:
> On Fri, 2009-01-09 at 09:55 +0200, Kalle Valo wrote:
>> Dan Williams <dcbw@redhat.com> writes:
>>
>> > 1) A 'frequency' config item that works in infrastructure mode too,
>> > ignoring any AP not matching that frequency
>>
>> Just out of curiosity, why this feature is needed? I can understand
>> hard-coding bssid, but I don't understand the use for hard-coding the
>> frequency.
>
> If the user wishes to lock the connection to a specific frequency,
> irregardless of other values.
I guessed that part :) But I wanted to ask why would user want to do
this? I don't see any benefits from that.
> Maybe you're right and we don't really care about it, but one other
> thing that would be nice is a "band" argument for a network block to
> differentiate A vs. B/G APs that might have the same SSID and
> security settings, but where the user only wants to use the A-side
> for example.
This would be nice to have, most probably I would immediately disable
A band just to get faster scanning. I don't use 802.11a anywhere, for
me it's useless.
--
Kalle Valo
prev parent reply other threads:[~2009-01-09 16:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 3:50 [PATCH v2 0/3] mac80211 suspend/resume Bob Copeland
2008-12-15 10:14 ` Johannes Berg
2008-12-15 15:22 ` Dan Williams
2008-12-15 9:28 ` Luis R. Rodriguez
2008-12-17 18:21 ` Bob Copeland
2008-12-23 20:30 ` Johannes Berg
2008-12-24 5:49 ` Bob Copeland
2008-12-24 7:16 ` Marcel Holtmann
2009-01-06 16:45 ` Dan Williams
2009-01-06 17:07 ` Bob Copeland
2009-01-06 17:14 ` Johannes Berg
2009-01-06 17:35 ` Bob Copeland
2009-01-06 17:43 ` Johannes Berg
2009-01-06 18:01 ` Bob Copeland
2009-01-06 18:16 ` Johannes Berg
2009-01-06 17:12 ` Marcel Holtmann
2009-01-06 18:52 ` Dan Williams
2009-01-06 19:36 ` Marcel Holtmann
2009-01-06 20:05 ` Johannes Berg
2009-01-09 23:53 ` Tomas Winkler
2009-01-10 9:27 ` Johannes Berg
2009-01-11 11:11 ` Tomas Winkler
2009-01-11 14:40 ` Bob Copeland
2009-01-08 16:39 ` Dan Williams
2009-01-09 7:55 ` Kalle Valo
2009-01-09 16:35 ` Dan Williams
2009-01-09 16:44 ` Kalle Valo [this message]
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=878wpktonw.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mabbaswireless@gmail.com \
--cc=marcel@holtmann.org \
--cc=me@bobcopeland.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;
as well as URLs for NNTP newsgroup(s).