Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Question of CSA callback
Date: Thu, 7 Apr 2011 13:56:20 +0200	[thread overview]
Message-ID: <op.vtkgr6op3ri7v4@arend-laptop> (raw)
In-Reply-To: <1302177128.3779.12.camel@jlt3.sipsolutions.net>

On Thu, 07 Apr 2011 13:52:08 +0200, Johannes Berg  
<johannes@sipsolutions.net> wrote:

> On Thu, 2011-04-07 at 13:42 +0200, Arend van Spriel wrote:
>> Hi Johannes,
>>
>> Recently I have taken a look at csa switch callback. After looking more
>> closely I decided to let mac80211 handle this itself, but I noticed
>> something strange in the interface so maybe you can clarify this.
>>
>> void (*channel_switch)(struct ieee80211_hw *hw,
>> 		       struct ieee80211_channel_switch *ch_switch);
>>
>> void ieee80211_chswitch_done(struct ieee80211_vif *vif, bool success);
>>
>> Basically we get a channel switch callback for iee80211_hw and for the
>> ieee80211_chswitch_done() the driver has to provide a vif. Should the
>> channel switch also operate on a vif?
>
> Ah, well, no, not right now anyway -- mac80211 doesn't support
> multi-channel operation yet.
>
> However, I think this kind of hw offload isn't necessary for your device
> at all.

Indeed I concluded we do not need this, but I just wanted to clarify the  
intended use of the interface.

Gr. AvS
-- 
"The most merciful thing in the world, I think, is the inability of the  
human
mind to correlate all its contents." - "The Call of Cthulhu"


      reply	other threads:[~2011-04-07 11:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07 11:42 Question of CSA callback Arend van Spriel
2011-04-07 11:52 ` Johannes Berg
2011-04-07 11:56   ` Arend van Spriel [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=op.vtkgr6op3ri7v4@arend-laptop \
    --to=arend@broadcom.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