From: Sven Schnelle <svens@stackframe.org>
To: kvalo@qca.qualcomm.com
Cc: ath10k@lists.infradead.org
Subject: Re: [RFC PATCH 0/2] ath10k: testmode support
Date: Tue, 03 Jun 2014 09:12:02 +0200 [thread overview]
Message-ID: <538D7542.2070007@stackframe.org> (raw)
In-Reply-To: <87iooj1fds.fsf@kamboji.qca.qualcomm.com>
Hi Kalle,
On 06/02/2014 05:48 PM, Kalle Valo wrote:
> Sven Schnelle <svens@stackframe.org> writes:
>
>> Only one small thing: The firmware expects the UTF commands in
>> segmented format. Should that splitting be done in your testmode
>> patch, or should userspace handle that?
> I would prefer to keep the driver as simple as possible. My idea here is
> that the testmode interface is only about tranmitting and receiving WMI
> packets, it does not look at all what's inside the packet. AFAIK the
> user space should be able to handle everything on it's own.
>
Ok, that's fine with me. I'm doing the fragmation in userspace already,
just wanted to mention that.
Thanks
Sven
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-06-03 7:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 9:19 [RFC PATCH 0/2] ath10k: testmode support Kalle Valo
2014-05-28 9:19 ` [RFC PATCH 1/2] ath10k: make ath10k_wmi_cmd_send() public Kalle Valo
2014-05-28 9:19 ` [RFC PATCH 2/2] ath10k: add testmode Kalle Valo
2014-05-29 11:43 ` Michal Kazior
2014-05-29 12:51 ` Kalle Valo
2014-05-30 6:17 ` Michal Kazior
2014-05-30 10:06 ` Kalle Valo
2014-05-30 10:22 ` Michal Kazior
2014-05-30 10:35 ` Kalle Valo
2014-05-30 10:40 ` Michal Kazior
2014-06-01 19:51 ` [RFC PATCH 0/2] ath10k: testmode support Sven Schnelle
2014-06-02 15:48 ` Kalle Valo
2014-06-03 7:12 ` Sven Schnelle [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=538D7542.2070007@stackframe.org \
--to=svens@stackframe.org \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@qca.qualcomm.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