From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Pushpal Sidhu <psidhu@gateworks.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v4 0/2] ath10k: testmode support
Date: Fri, 14 Nov 2014 17:09:21 +0200 [thread overview]
Message-ID: <87389lstst.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAD1M061Gky-a28Rokmgyd-5x_m_h1SNmj9ZxUd4v1fP=bae35g@mail.gmail.com> (Pushpal Sidhu's message of "Thu, 13 Nov 2014 16:08:30 -0800")
Pushpal Sidhu <psidhu@gateworks.com> writes:
> On Thu, Sep 11, 2014 at 1:43 PM, Kalle Valo <kvalo@qca.qualcomm.com> wrote:
>> Kalle Valo <kvalo@qca.qualcomm.com> writes:
>>
>>> latest version of my testmode patches. Getting closer, more or less cosmetic
>>> changes this time :)
>
> While looking through this patchset (sorry it took two months), I have
> to wonder: what's this utf.bin blob? It seems in order to use
> testmode, we need this binary blob that I can't seem to find (I looked
> in linux-firmware and https://github.com/kvalo/ath10k-firmware). If,
> for whatever reason, this binary blob is not releasable, what's the
> point of adding in testmode to this driver?
testmode is for functionality needed in the factory, it's not meant for
normal users. That's why all distros should have CONFIG_NL80211_TESTMODE
disabled.
--
Kalle Valo
next prev parent reply other threads:[~2014-11-14 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 15:23 [PATCH v4 0/2] ath10k: testmode support Kalle Valo
2014-09-10 15:23 ` [PATCH v4 1/2] ath10k: make ath10k_wmi_cmd_send() public Kalle Valo
2014-09-10 15:23 ` [PATCH v4 2/2] ath10k: add testmode Kalle Valo
2014-09-11 9:47 ` Michal Kazior
2014-09-11 10:39 ` Kalle Valo
2014-09-11 20:43 ` [PATCH v4 0/2] ath10k: testmode support Kalle Valo
2014-11-14 0:08 ` Pushpal Sidhu
2014-11-14 15:09 ` Kalle Valo [this message]
2014-11-15 1:00 ` Tim Harvey
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=87389lstst.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=psidhu@gateworks.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;
as well as URLs for NNTP newsgroup(s).