From: Sujith <m.sujith@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
Jouni.Malinen@Atheros.com
Subject: Re: [PATCH] mac80211: Add 802.11h CSA support
Date: Wed, 31 Dec 2008 16:11:44 +0530 [thread overview]
Message-ID: <18779.19560.719396.912447@localhost.localdomain> (raw)
In-Reply-To: <1230718812.4065.7.camel@johannes>
Johannes Berg wrote:
> On Wed, 2008-12-31 at 15:39 +0530, Sujith wrote:
> > Move to the advertised channel on reception of
> > a CSA element. This is needed for 802.11h compliance.
> >
> > Signed-off-by: Sujith <Sujith.Manoharan@atheros.com>
>
> One thing I've been wondering about though, should we have a hook into
> the driver to actually stop transmit at a lower level, where possible?
> For example Broadcom hardware we can actually set some value on the chip
> and then let it reject all frames, drain its FIFOs, and then in the
> driver we could schedule those frames again for afterwards.
I think that is needed only when handling Quiet IE, which I was planning to work
on separately, with a notification to the driver to stop transmission completely for a period of time.
> > + sdata->local->oper_channel = new_ch;
>
> Here you're setting oper_channel, but is that really the right thing to
> do? That means any hw config call that comes in between this and later
> will already switch to that channel, and hw config can happen for
> various other reasons, for instance PS mode stuff. I think we may need
> to have a separate variable?
Right, a *switch_to in sdata would suffice, I guess.
I'll send an updated patch.
Sujith
next prev parent reply other threads:[~2008-12-31 10:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 10:09 [PATCH] mac80211: Add 802.11h CSA support Sujith
2008-12-31 10:20 ` Johannes Berg
2008-12-31 10:41 ` Sujith [this message]
2008-12-31 10:24 ` Tomas Winkler
2008-12-31 10:44 ` Sujith
-- strict thread matches above, loose matches on Subject: below --
2009-01-06 3:58 Sujith
2009-01-06 13:05 ` Johannes Berg
2022-11-02 3:26 ` Wen Gong
2022-11-22 21:26 ` Johannes Berg
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=18779.19560.719396.912447@localhost.localdomain \
--to=m.sujith@gmail.com \
--cc=Jouni.Malinen@Atheros.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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