From: wen <allen.z.wen@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Ironic kernel panic when changing STATION channel type (b/t HT20 and HT40)
Date: Tue, 11 Jun 2013 16:44:04 -0700 [thread overview]
Message-ID: <51B7B644.5040207@gmail.com> (raw)
Hello developers!
I am new to linux wireless driver coding, and is trying to implement
Notify Channel Width Action frame.
Along with sending the action frame to request AP send data using
specified bandwidth (20MHZ or 40MHZ), STATION also need to change its
channel type accordingly (b/t HT20 and HT40).
For now, my implementation on action frame and updating sending rate b/t
HT20 rates and HT40 rates works fine, but not for channel type change.
One way I tried to change channel type is calling
ieee80211_set_channel_type() primitive. This can change channel type as
wish on AP side, but ironically, it causes kernel panic (inside
ieee80211_set_channel_type() function) when called exactly on STATION,
even the same way as it is called on AP.
Another way I tried is through calling drv_config(), which causes kernel
panic on both AP and STATION side also.
I truly appreciate it if you could help me with your rich experience!
Thanks in advance!
Wen
reply other threads:[~2013-06-11 23:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51B7B644.5040207@gmail.com \
--to=allen.z.wen@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).