From: Felix Fietkau <nbd@openwrt.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 1/2] cfg80211: add a callback for querying the operating frequency and export it through nl80211
Date: Sun, 17 Jan 2010 21:12:17 +0100 [thread overview]
Message-ID: <4B536F21.1090509@openwrt.org> (raw)
In-Reply-To: <1263758423.28067.12.camel@johannes.local>
On 2010-01-17 9:00 PM, Johannes Berg wrote:
> On Sun, 2010-01-17 at 20:57 +0100, Johannes Berg wrote:
>> On Sun, 2010-01-17 at 20:54 +0100, Felix Fietkau wrote:
>>
>> > + int (*get_channel)(struct wiphy *wiphy,
>> > + struct ieee80211_channel **chan,
>> > + enum nl80211_channel_type *channel_type);
>>
>> Can you do that per netdev, please? We'll eventually get into having
>> to support different channels on different netdevs.
>
> OTOH, where is this really needed?
>
> If you have an IBSS or managed mode then you know from the BSS info what
> channel you should be on... APs are completely userspace controlled
> anyway, so are monitors.
I was thinking about scanning, but then again, that's not handled by my
patch series either. I'll simplify it and make it per-netdev.
- Felix
next prev parent reply other threads:[~2010-01-17 20:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 19:54 [PATCH 1/2] cfg80211: add a callback for querying the operating frequency and export it through nl80211 Felix Fietkau
2010-01-17 19:55 ` [PATCH 2/2] mac80211: implement the callback for querying the operating frequency Felix Fietkau
2010-01-17 19:57 ` [PATCH 1/2] cfg80211: add a callback for querying the operating frequency and export it through nl80211 Johannes Berg
2010-01-17 20:00 ` Johannes Berg
2010-01-17 20:12 ` Felix Fietkau [this message]
2010-01-17 20:14 ` Johannes Berg
2010-01-17 20:23 ` Felix Fietkau
2010-01-17 20:48 ` Johannes Berg
2010-01-17 21:01 ` Felix Fietkau
2010-01-17 21:03 ` Felix Fietkau
2010-01-17 21:05 ` Johannes Berg
2010-01-19 17:39 ` Luis R. Rodriguez
2010-01-20 7:32 ` Holger Schurig
2010-01-20 9:49 ` 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=4B536F21.1090509@openwrt.org \
--to=nbd@openwrt.org \
--cc=johannes@sipsolutions.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.