From: Pavel Roskin <proski@gnu.org>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: "bcm43xx-dev@lists.berlios.de" <bcm43xx-dev@lists.berlios.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Wireless-testing's b43 panics in b43_generate_txhdr on packet transmit
Date: Sat, 31 May 2008 13:06:44 -0400 [thread overview]
Message-ID: <1212253604.2766.15.camel@rd> (raw)
In-Reply-To: <69e28c910805310954s6c478001h837415a6a63d26f0@mail.gmail.com>
On Sat, 2008-05-31 at 18:54 +0200, Stefanik G=E1bor wrote:
> On Sat, May 31, 2008 at 6:48 PM, Pavel Roskin <proski@gnu.org> wrote:
> > It's strange that other drivers (b43legacy, ath5k) use
> > info->control.hw_key->hw_key_idx under the same conditions (see how
> > use_encryption is calculated), but don't have any problems on the s=
ame
> > network (but I need to recheck).
>=20
> Hmm... does ath5k use hardware crypto?
No, it doesn't, at least with WEP, if I understand ath5k_set_key()
correctly.
> B43 does (but not with
> nohwcrypt - and that appears to be a valid workaround), b43legacy
> doesn't AFAIK.
Although the code with use_encryption is present in b43legacy, it don't
see any references to "set_key", so I guess you are right.
Well, that explains something.
--=20
Regards,
Pavel Roskin
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Roskin <proski@gnu.org>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: "bcm43xx-dev@lists.berlios.de" <bcm43xx-dev@lists.berlios.de>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Wireless-testing's b43 panics in b43_generate_txhdr on packet transmit
Date: Sat, 31 May 2008 13:06:44 -0400 [thread overview]
Message-ID: <1212253604.2766.15.camel@rd> (raw)
In-Reply-To: <69e28c910805310954s6c478001h837415a6a63d26f0@mail.gmail.com>
On Sat, 2008-05-31 at 18:54 +0200, Stefanik Gábor wrote:
> On Sat, May 31, 2008 at 6:48 PM, Pavel Roskin <proski@gnu.org> wrote:
> > It's strange that other drivers (b43legacy, ath5k) use
> > info->control.hw_key->hw_key_idx under the same conditions (see how
> > use_encryption is calculated), but don't have any problems on the same
> > network (but I need to recheck).
>
> Hmm... does ath5k use hardware crypto?
No, it doesn't, at least with WEP, if I understand ath5k_set_key()
correctly.
> B43 does (but not with
> nohwcrypt - and that appears to be a valid workaround), b43legacy
> doesn't AFAIK.
Although the code with use_encryption is present in b43legacy, it don't
see any references to "set_key", so I guess you are right.
Well, that explains something.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-05-31 17:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-31 14:23 Wireless-testing's b43 panics in b43_generate_txhdr on packet transmit Stefanik Gábor
2008-05-31 14:23 ` Stefanik Gábor
2008-05-31 15:11 ` Michael Buesch
2008-05-31 15:11 ` Michael Buesch
2008-05-31 16:34 ` Stefanik Gábor
2008-05-31 16:41 ` Michael Buesch
2008-05-31 16:41 ` Michael Buesch
2008-05-31 16:50 ` Pavel Roskin
2008-05-31 16:50 ` Pavel Roskin
2008-05-31 17:54 ` Michael Buesch
2008-05-31 17:54 ` Michael Buesch
2008-05-31 20:22 ` Johannes Berg
2008-05-31 20:29 ` Stefanik Gábor
2008-05-31 20:29 ` Stefanik Gábor
2008-05-31 20:48 ` Michael Buesch
2008-05-31 20:48 ` Michael Buesch
[not found] ` <20080602000841.qjrd66s3esgscko0-cebfxv@fcnzpbc.arg@webmail.spamcop.net>
2008-06-02 4:33 ` Pavel Roskin
2008-06-02 7:47 ` Johannes Berg
2008-05-31 16:48 ` Pavel Roskin
2008-05-31 16:48 ` Pavel Roskin
2008-05-31 16:54 ` Stefanik Gábor
2008-05-31 17:06 ` Pavel Roskin [this message]
2008-05-31 17:06 ` Pavel Roskin
2008-05-31 17:59 ` Michael Buesch
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=1212253604.2766.15.camel@rd \
--to=proski@gnu.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netrolller.3d@gmail.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 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.