From: Amitkumar Karwar <akarwar@marvell.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Cathy Luo" <cluo@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
Xinming Hu <huxm@marvell.com>
Subject: RE: [PATCH v3 2/2] mwifiex: add hostcmd wext ioctl support
Date: Wed, 13 Jul 2016 15:25:58 +0000 [thread overview]
Message-ID: <35fedc2035a64135a4d995aca379d4e9@SC-EXCH04.marvell.com> (raw)
In-Reply-To: <87y455a7u3.fsf@purkki.adurom.net>
Hi Kalle,
> -----Original Message-----
> From: Kalle Valo [mailto:kvalo@codeaurora.org]
> Sent: Wednesday, July 13, 2016 8:44 PM
> To: Amitkumar Karwar
> Cc: linux-wireless@vger.kernel.org; Cathy Luo; Nishant Sarmukadam;
> Xinming Hu
> Subject: Re: [PATCH v3 2/2] mwifiex: add hostcmd wext ioctl support
>
> Amitkumar Karwar <akarwar@marvell.com> writes:
>
> > From: Xinming Hu <huxm@marvell.com>
> >
> > This patch adds ndo_ioctl support to mwifiex netdev handlers.
> > This will be used to download hostcmds to firmware from userspace.
> > This is needed for manufacturing mode support in mwifiex. ndo_ioctl is
> > allowed only when mfg mode is enabled via module load parameters.
> >
> > Signed-off-by: Xinming Hu <huxm@marvell.com>
> > Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
> > ---
> > v3: Add "select WIRELESS_EXT" in Kconfig to resolve kbuild test robot
> errors.
> > WEXT_PRIV seems to have a dependency with WIRELESS_EXT.
> > v2: 1) Sequence of these two patches are changed to resolve
> compilation
> > error seen if only 1/2 is applied.
> > 2) Add "select WEXT_PRIV" in Kconfig to resolve warnings reported
> by
> > kbuild test robot.
>
> Why can't you use nl80211 testmode interface?
These two patches facilitates user to configure manufacturing mode. We have a separate firmware for this mode.
It's needed to run special WiFi conductive and radiated tests at factory. The userspace tools used for this purpose expects WEXT interface.
Regards,
Amitkumar
next prev parent reply other threads:[~2016-07-13 15:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 13:48 [PATCH v3 1/2] mwifiex: add manufacturing mode support Amitkumar Karwar
2016-07-13 13:48 ` [PATCH v3 2/2] mwifiex: add hostcmd wext ioctl support Amitkumar Karwar
2016-07-13 15:14 ` Kalle Valo
2016-07-13 15:25 ` Amitkumar Karwar [this message]
2016-07-13 15:48 ` Kalle Valo
2016-07-13 15:59 ` Amitkumar Karwar
2016-07-16 14:42 ` kbuild test robot
2016-07-13 15:50 ` [PATCH v3 1/2] mwifiex: add manufacturing mode support Kalle Valo
2016-07-13 15:57 ` Amitkumar Karwar
2016-07-13 16:31 ` Kalle Valo
2016-07-13 16:39 ` Amitkumar Karwar
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=35fedc2035a64135a4d995aca379d4e9@SC-EXCH04.marvell.com \
--to=akarwar@marvell.com \
--cc=cluo@marvell.com \
--cc=huxm@marvell.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.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