From: Mahesh Palivela <maheshp@posedge.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: Enable sw scan with chan context
Date: Tue, 12 Mar 2013 08:39:26 +0530 [thread overview]
Message-ID: <1363057766.778.8.camel@WLAN-SW-TEST-03> (raw)
In-Reply-To: <1363015558.5284.11.camel@jlt4.sipsolutions.net>
On Mon, 2013-03-11 at 17:25 +0200, Johannes Berg wrote:
> On Mon, 2013-03-11 at 20:51 +0530, Mahesh Palivela wrote:
>
> > I tested this patch. scan works.
>
> Works how? It never tells the driver to go to a different channel ...
sorry. I missed this. But my patch takes care of crash in mac80211 once
we remove 'use_chanctx' check in sw_scan function.
>
> Besides, telling the driver to go to one channel via the hw_config call,
> and using chanctx for vif configuration seems like a really bad idea.
>
Agree.
> > Anyways chan context is a WIP.
>
> It pretty much works.
For AP mode yes it works. But for STA mode, we have work I guess.
>
> > There is no driver which is using the chan ctx work yet.
>
> There is, our mvm driver uses it.
>
Thanks for the info. I will take a look.
> > I will continue adding code for chan ctx.
>
> What are you trying to achieve anyway?
>
VHT assoc. To enable VHT on both AP and STA. For VHT to work we need
chan_ctx. Isn't it?
> johannes
>
next prev parent reply other threads:[~2013-03-12 3:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 14:05 [PATCH] mac80211: Enable sw scan with chan context Mahesh Palivela
2013-03-11 14:39 ` Johannes Berg
2013-03-11 15:21 ` Mahesh Palivela
2013-03-11 15:25 ` Johannes Berg
2013-03-12 3:09 ` Mahesh Palivela [this message]
2013-03-12 10:09 ` Karl Beldan
2013-03-15 15:25 ` Johannes Berg
2013-03-14 13:46 ` Mahesh Palivela
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=1363057766.778.8.camel@WLAN-SW-TEST-03 \
--to=maheshp@posedge.com \
--cc=johannes@sipsolutions.net \
--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