linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Replacement for local->hw.conf.channel
Date: Mon, 08 Jul 2013 20:31:29 +0200	[thread overview]
Message-ID: <1373308289.8312.17.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <51DB0302.5050201@candelatech.com>

On Mon, 2013-07-08 at 11:20 -0700, Ben Greear wrote:
> On 07/04/2013 12:27 AM, Johannes Berg wrote:
> > On Wed, 2013-07-03 at 17:01 -0700, Ben Greear wrote:
> >> I'm trying to port some patches forward to 3.10....
> >>
> >> I am trying to find the current channel for a radio.  Since
> >> hw.conf.channel no longer exists, what is the best way to
> >> go about this?
> >
> > Well there's hw.conf.chandef.chan now I think, but that can be NULL and
> > generic mac80211 code must not use it. There's no single current channel
> > any more, you want vif->chanctx or so.
> 
>  From looking at the scanning code (line 542 or so), it appears
> 
> local->_oper_chandef.chan
> 
> might work?

No, don't use that in any new code. It's purely for compatibility with
drivers that aren't converted to channel contexts (yet).

> In 3.9, ath9k_htc was giving me a null channel in the code below:
> 
> 	chanctx_conf = rcu_dereference(sdata->vif.chanctx_conf);
> 	if (chanctx_conf)
> 		channel = chanctx_conf->def.chan;
> 	else
> 		channel = NULL;

Well that of course happens if the vif isn't bound to a channel context.

johannes


  reply	other threads:[~2013-07-08 18:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04  0:01 Replacement for local->hw.conf.channel Ben Greear
2013-07-04  7:27 ` Johannes Berg
2013-07-08 18:20   ` Ben Greear
2013-07-08 18:31     ` Johannes Berg [this message]
2013-07-08 18:47       ` Ben Greear
2013-07-09 14:35         ` Johannes Berg
2013-07-09 16:32           ` Ben Greear

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=1373308289.8312.17.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    /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).