From: Johannes Berg <johannes@sipsolutions.net>
To: Benoit Papillault <benoit.papillault@free.fr>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] cfg80211/mac80211: better channel handling
Date: Thu, 06 May 2010 07:35:59 +0200 [thread overview]
Message-ID: <1273124159.3573.7.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4BE1DBFE.2060909@free.fr>
On Wed, 2010-05-05 at 22:58 +0200, Benoit Papillault wrote:
> Real hardware are not capable of listening on multiple channels (except
> 2 ht20 channels in ht40 mode, maybe?). So I don't understand why we
> should have a per-interface channel.
>
> I think we should either have two strategies :
>
> - "first one is the winner" : once a channel has been set, it cannot be
> changed. For instance, if you create an AP interface (with hostapd) and
> latter a STA interface, the STA interface can only scan on the channel
> the AP is.
That's what you get now.
> - "last one is the winner" : in this case, the last call to set the
> channel is always successful. Of course, this will change channel on
> existing interfaces which might change their IE accordingly, through an
> appropriate API.
That's pretty much impossible to implement with the current split
between user and kernel space.
> I might be wrong, but I don't see this multi-channel usage...
Say you have two stations associated to two different APs. They can
powersave while they are on the channel for the other AP. It'll be done,
rather soon, trust me :)
johannes
next prev parent reply other threads:[~2010-05-06 5:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 10:36 [PATCH] cfg80211/mac80211: better channel handling Johannes Berg
2010-05-05 12:12 ` Johannes Berg
2010-05-05 13:25 ` [PATCH v2] " Johannes Berg
2010-05-05 20:58 ` Benoit Papillault
2010-05-06 5:35 ` Johannes Berg [this message]
2010-05-06 5:46 ` Benoit Papillault
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=1273124159.3573.7.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=benoit.papillault@free.fr \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).