All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] b43: allow disabling hardware encryption
Date: Wed, 22 Aug 2007 00:22:45 +0200	[thread overview]
Message-ID: <200708220022.45381.mb@bu3sch.de> (raw)
In-Reply-To: <1187712498.4218.3.camel@johannes.berg>

On Tuesday 21 August 2007 18:08:18 Johannes Berg wrote:
> For debugging it seems useful to be able to turn off
> hardware encryption. With the changes I made to mac80211
> that is now simple.
> 
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
> 
> ---
>  drivers/net/wireless/b43/main.c |    7 +++++++
>  1 file changed, 7 insertions(+)
> 
> --- wireless-dev.orig/drivers/net/wireless/b43/main.c	2007-08-21 16:41:30.955923881 +0200
> +++ wireless-dev/drivers/net/wireless/b43/main.c	2007-08-21 16:47:46.175923881 +0200
> @@ -96,6 +96,10 @@ static int modparam_hwpctl;
>  module_param_named(hwpctl, modparam_hwpctl, int, 0444);
>  MODULE_PARM_DESC(hwpctl, "Enable hardware-side power control (default off)");
>  
> +static int modparam_nohwcrypt;
> +module_param_named(nohwcrypt, modparam_nohwcrypt, int, 0644);
> +MODULE_PARM_DESC(nohwcrypt, "Disable hardware encryption.");
> +
>  static const struct ssb_device_id b43_ssb_tbl[] = {
>  	SSB_DEVICE(SSB_VENDOR_BROADCOM, SSB_DEV_80211, 5),
>  	SSB_DEVICE(SSB_VENDOR_BROADCOM, SSB_DEV_80211, 6),
> @@ -2850,6 +2854,9 @@ static int b43_dev_set_key(struct ieee80
>  	u8 index;
>  	int err = -EINVAL;
>  
> +	if (modparam_nohwcrypt)
> +		return -ENOSPC;
> +
>  	if (!dev)
>  		return -ENODEV;
>  	switch (key->alg) {

I queued this, although your mac80211 patch that changes the key
stuff is not in, yet. /me looks at John. :)

-- 
Greetings Michael.

      reply	other threads:[~2007-08-21 22:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 16:08 [PATCH] b43: allow disabling hardware encryption Johannes Berg
2007-08-21 22:22 ` Michael Buesch [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=200708220022.45381.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=johannes@sipsolutions.net \
    --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 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.