All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Sven Schnelle <svens@stackframe.org>
Cc: ath10k@lists.infradead.org
Subject: Re: [RFC PATCH 0/2] ath10k: testmode support
Date: Mon, 2 Jun 2014 18:48:47 +0300	[thread overview]
Message-ID: <87iooj1fds.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <538B8446.50301@stackframe.org> (Sven Schnelle's message of "Sun,  1 Jun 2014 21:51:34 +0200")

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.

-- 
Kalle Valo

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2014-06-02 15:49 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 [this message]
2014-06-03  7:12     ` Sven Schnelle

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=87iooj1fds.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=svens@stackframe.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.