From: Dave <kilroyd@googlemail.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org, Pavel Roskin <proski@gnu.org>,
orinoco-devel@lists.sourceforge.net,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] orinoco: enable cfg80211 "set_channel" operation
Date: Tue, 28 Jul 2009 17:27:54 +0100 [thread overview]
Message-ID: <4A6F270A.7030002@gmail.com> (raw)
In-Reply-To: <200907281634.26104.hs4233@mail.mn-solutions.de>
Holger Schurig wrote:
> Signed-off-by: Holger Schurig <hs4233@mail.mn-solutions.de>
Cool.
> + if (orinoco_lock(priv, &flags) != 0)
> + return -EBUSY;
> +
> + priv->channel = channel;
> + if (priv->iw_mode == NL80211_IFTYPE_MONITOR) {
> + /* Fast channel change - no commit if successful */
> + hermes_t *hw = &priv->hw;
> + err = hermes_docmd_wait(hw, HERMES_CMD_TEST |
> + HERMES_TEST_SET_CHANNEL,
> + channel, NULL);
> + }
> + orinoco_unlock(priv, &flags);
> +
> + return err;
> +}
Looks right for monitor mode (as you tested), but for ad-hoc the channel
change would be delayed until the next SIOCSIWCOMMIT. Which for cfg80211
is currently only on change_vif.
Adding a call to orinoco_commit(priv) in the ad-hoc case should push the
change to the card. I think we'll end up with this call in each of the
orinoco cfg80211 functions. Otherwise we have to work out how to do the
changes incrementally across the different hw/fw.
You can also eliminate orinoco_ioctl_setfreq from wext.c with this change.
Thanks,
Dave.
next parent reply other threads:[~2009-07-28 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200907281634.26104.hs4233@mail.mn-solutions.de>
2009-07-28 16:27 ` Dave [this message]
2009-07-28 16:29 ` [PATCH] orinoco: enable cfg80211 "set_channel" operation Johannes Berg
2009-07-28 16:31 ` Johannes Berg
2009-07-28 20:42 ` Dave
2009-07-29 7:16 ` Holger Schurig
2009-07-30 18:47 ` Dave
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=4A6F270A.7030002@gmail.com \
--to=kilroyd@googlemail.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=orinoco-devel@lists.sourceforge.net \
--cc=proski@gnu.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 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.