From: Larry Finger <Larry.Finger@lwfinger.net>
To: Jiri Slaby <jirislaby@gmail.com>,
Nick Kossifidis <mickflemm@gmail.com>,
"Luis R. Rodriguez" <mcgrof@qca.qualcomm.com>,
Bob Copeland <me@bobcopeland.com>
Cc: wireless <linux-wireless@vger.kernel.org>,
ath5k-devel@lists.ath5k.org,
"Steinar Løklingholm" <steinar@megawatt.no>
Subject: Problem with hardware crypto
Date: Sat, 19 Nov 2011 22:57:13 -0600 [thread overview]
Message-ID: <4EC888A9.3050505@lwfinger.net> (raw)
On openSUSE 12.1 with kernel 3.1, Steinar Løklingholm reports that he needs to
use the "nohwcrypt=1" option when loading ath5k, otherwise the interface does
not work.
His bug report is at https://bugzilla.novell.com/show_bug.cgi?id=731576.
Is this a known problem? If not, I would appreciate someone looking at this report.
Thanks,
Larry
reply other threads:[~2011-11-20 4:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4EC888A9.3050505@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=ath5k-devel@lists.ath5k.org \
--cc=jirislaby@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@qca.qualcomm.com \
--cc=me@bobcopeland.com \
--cc=mickflemm@gmail.com \
--cc=steinar@megawatt.no \
/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).