From: Michal Kazior <michal.kazior@tieto.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Thomas Pedersen <thomas@cozybit.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"devel@lists.open80211s.org" <devel@lists.open80211s.org>,
"linville@tuxdriver.com" <linville@tuxdriver.com>
Subject: Re: [RFC] nl80211: don't require netdev UP for wdev
Date: Wed, 9 May 2012 12:16:16 +0200 [thread overview]
Message-ID: <4FAA43F0.6050401@tieto.com> (raw)
In-Reply-To: <1336557043.4323.15.camel@jlt3.sipsolutions.net>
Johannes Berg wrote:
>>> We should do the same for AP mode as well, since the channel really
>>> becomes relevant only upon start_ap(), before that there's no real
>>> concept of a channel since you don't use it yet anyway.
>>
>> Maybe we should do the same with monitor interface type, i.e. introduce
>> start_monitor() and have it pass the channel.
>
> No, that's the special case that doesn't work that way -- monitor mode
> interfaces are also great for debugging when they're just concurrently
> running with other interfaces and don't have their own channel setting.
We can make monitor interface to be a slave to other non-monitor
interface by passing an extra parameter in start_monitor(). We could
then have such a monitor interface follow channel changes of a given
non-monitor interface (or rather it wouldn't be using a channel on it's
own).
>> But then I'm thinking we shouldn't really be changing interface types
>> explicitly, since they would be set implicitly by start_ap() and such.
>> We could then use the NL80211_IFTYPE_UNSPECIFIED when we're not associated.
>
> From some point of view, it should work that way, yes.
>
> Given how entrenched interface types are we definitely can't get rid of
> them though, and they're still needed to do concurrency management etc.
Well, I don't think we can get completely rid of them, too. Or do you
mean something else?
--
Pozdrawiam / Best regards, Michal Kazior.
next prev parent reply other threads:[~2012-05-09 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 22:28 [RFC] nl80211: don't require netdev UP for wdev Thomas Pedersen
2012-05-09 9:15 ` Johannes Berg
2012-05-09 9:41 ` Michal Kazior
2012-05-09 9:50 ` Johannes Berg
2012-05-09 10:16 ` Michal Kazior [this message]
2012-05-09 11:40 ` Johannes Berg
2012-05-10 18:06 ` Thomas Pedersen
2012-05-10 18:12 ` Johannes Berg
2012-05-10 19:47 ` Thomas Pedersen
2012-05-10 19:52 ` 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=4FAA43F0.6050401@tieto.com \
--to=michal.kazior@tieto.com \
--cc=devel@lists.open80211s.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=thomas@cozybit.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.