From: Johannes Berg <johannes@sipsolutions.net>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
rt2400-devel@lists.sourceforge.net
Subject: Re: [PATCH] rt2x00: Add module parameter to disable HW crypto
Date: Wed, 06 Aug 2008 17:42:29 +0200 [thread overview]
Message-ID: <1218037349.23048.14.camel@johannes.berg> (raw)
In-Reply-To: <200808061806.40006.IvDoorn@gmail.com> (sfid-20080806_174135_651759_33254611)
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
On Wed, 2008-08-06 at 18:06 +0200, Ivo van Doorn wrote:
> On Wednesday 06 August 2008, Johannes Berg wrote:
> > On Wed, 2008-08-06 at 17:27 +0200, Ivo van Doorn wrote:
> > > Add a module parameter to rt61 and rt73 to disable
> > > HW crypto. The option should only be checked when
> > > determining if the SUPPORT_HW_CRYPTO flag should
> > > be set or not.
> >
> > I wonder if instead mac80211 should have an option for this. It'd be
> > trivial to simply not tell the hardware about the keys.
>
> Then it probably needs to be a per physical interface configuration option,
> which can only be toggled when the interface is down. Because I don't think
> you want the option to be global for all available physical interfaces.
Why not? It's mostly a debug option anyway. We can hide it away in
debugfs per phy, but I wouldn't really care if it was global since the
driver isn't supposed to be broken :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2008-08-06 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 15:27 [PATCH] rt2x00: Add module parameter to disable HW crypto Ivo van Doorn
2008-08-06 15:22 ` Johannes Berg
2008-08-06 16:06 ` Ivo van Doorn
2008-08-06 15:42 ` Johannes Berg [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=1218037349.23048.14.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rt2400-devel@lists.sourceforge.net \
/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