linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Liu CF/TW <cfliu.tw@gmail.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
	<linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath10k/mac80211: add rawtxrx, nohwcrypt module param for raw tx injection, sw crypto support.
Date: Mon, 11 May 2015 15:24:52 +0300	[thread overview]
Message-ID: <87wq0fi9nv.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <554CE438.5000208@candelatech.com> (Ben Greear's message of "Fri, 8 May 2015 09:28:40 -0700")

Ben Greear <greearb@candelatech.com> writes:

> Maybe we could have a way to specify both rx and rx mode independently of
> each other to support that use case as well?
>
> Maybe:
>
> txmode=x;  // 0 == native, 1 == raw (and maybe support other tx modes in the future as desired)
> rxmode=x;  // 0 == native, 1 == raw
> nohwcrypt=x; // 0 == standard hw crypt, 0x1 == rx-sw-crypt, 0x2 == tx-sw-crypt, 0x3 == tx/rx-sw-crypt

This looks overly complicated and hard to maintain for a very special
use case, not really excited about this.

-- 
Kalle Valo

      parent reply	other threads:[~2015-05-11 12:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06  1:06 [PATCH] ath10k/mac80211: add rawtxrx, nohwcrypt module param for raw tx injection, sw crypto support Liu CF/TW
2015-05-08 11:54 ` Kalle Valo
2015-05-08 16:28   ` Ben Greear
2015-05-08 17:35     ` Liu CF/TW
2015-05-08 17:52       ` Ben Greear
2015-05-11 12:12       ` Kalle Valo
2015-05-11 16:17         ` Ben Greear
2015-05-12 22:44           ` Liu CF/TW
2015-05-12 23:01             ` Liu CF/TW
2015-05-14 15:12             ` Kalle Valo
2015-05-14 19:35               ` Liu CF/TW
2015-05-14 21:16                 ` Ben Greear
2015-05-11 12:24     ` Kalle Valo [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=87wq0fi9nv.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath10k@lists.infradead.org \
    --cc=cfliu.tw@gmail.com \
    --cc=greearb@candelatech.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).