From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, yi.zhu@intel.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: add spectrum capabilities
Date: Thu, 19 Jun 2008 00:58:54 +0300 [thread overview]
Message-ID: <1ba2fa240806181458u1b47474bkc5e3d74128588141@mail.gmail.com> (raw)
In-Reply-To: <1213823853.1312.37.camel@johannes.berg>
On Thu, Jun 19, 2008 at 12:17 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
>
>> Yes, this is handled by firmware, What is important is to make switch
>> on beacon edge.
>> Still our implementation uses also timer in mac rather then some mac
>> to driver over complicated synchronization.
>> Other thing is that the firmware enforce the switching, traffic on the
>> old channel is not allowed after the switch.
>
> Yeah, ok. As for enforcing the traffic, true as well. However, I'd like
> mac80211 to help out with this for those drivers that don't do it all in
> firmware (all others, I'd assume); it's not overly important that you
> switch instantly after receiving the switch beacon, if you take a bit
> longer to do that you'll just potentially miss a few packets. No big
> deal.
Sending few packets on the old channel would be the spec violation
meaning it will fail the certification if you would
be interested in one.
Anyhow I hope that our patch takes care of the cases with not
supporting fimrware as well.
Thanks
Tomas
prev parent reply other threads:[~2008-06-18 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 14:53 [PATCH 1/2] mac80211: add MAC80211_VERBOSE_SPECT_MGMT_DEBUG Kconfig option Tomas Winkler
2008-06-18 14:53 ` [PATCH 2/2] mac80211: add spectrum capabilities Tomas Winkler
2008-06-18 15:37 ` Johannes Berg
2008-06-18 16:17 ` Tomas Winkler
2008-06-18 17:23 ` Johannes Berg
2008-06-18 21:11 ` Tomas Winkler
2008-06-18 21:17 ` Johannes Berg
2008-06-18 21:58 ` Tomas Winkler [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=1ba2fa240806181458u1b47474bkc5e3d74128588141@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=yi.zhu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox