All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Thomas Pedersen <thomas@cozybit.com>
Cc: linux-wireless@vger.kernel.org, devel@lists.open80211s.org,
	linville@tuxdriver.com
Subject: Re: [RFC] nl80211: don't require netdev UP for wdev
Date: Thu, 10 May 2012 21:52:09 +0200	[thread overview]
Message-ID: <1336679529.4334.35.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAG6hwVNTRYpr_H4za0Jf8gVU2=W5f6ZmzCiZsK4Ad2cGa26jDQ@mail.gmail.com> (sfid-20120510_214803_866961_870A1B62)

On Thu, 2012-05-10 at 12:47 -0700, Thomas Pedersen wrote:

> > We could, but that'd mean that it can be NULL if the user doesn't set
> > it, which seems a bit odd to me too and then the driver again would have
> > to sort it out. I'd prefer if we could sort it out in cfg80211 so the
> > driver (mac80211) is simpler.
> 
> For this, we can store a default channel and type in the default mesh config.

That would still break older userspace though, it would get the default
channel instead of the channel it set before, right?

> >> Also, with IBSS the desired channel is pushed to the driver along with
> >> the setup parameters. What do you think about calling
> >> __nl80211_set_channel() directly instead of relying on the cfg80211
> >> driver to handle this?
> >
> > No, that's certainly not possible. In IBSS the channel is just the
> > default channel if we don't find an IBSS. And in any case I'd rather
> > call set_channel less than more.
> 
> So cfg80211_set_freq() from cfg80211_join_mesh() is out, too?

I think we should just pass the channel to the join_mesh callback.

I just did this a bit for AP mode. Now, in AP mode we have one
advantage: we can rely on userspace setting the channel because
hostapd/wpa_s always does that. For mesh, we may not have that luxury?

For AP, it looks roughly like this:
http://p.sipsolutions.net/35913f571ea5bd43.txt

Maybe we can do something similar for mesh and mostly get rid of setting
the channel directly.

johannes


      reply	other threads:[~2012-05-10 19:52 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
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 [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=1336679529.4334.35.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=devel@lists.open80211s.org \
    --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.