From: Milan Plzik <milan.plzik@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Support for 1.103 firmware on at76 devices
Date: Fri, 04 Jul 2008 19:43:35 +0200 [thread overview]
Message-ID: <1215193415.4619.16.camel@localhost> (raw)
Hello,
following series of patches applies to current wireless-testing adds
support for 1.103 firmware (and thus for at least RC4/TKIP, AES/CCMP was
not possible to test, although support is implemented). In this form
patches should autodetect firmware version and properly operate with
both, but only operation with 1.103 firmware was tested, as the primary
intention was to get these devices working with this version of
firmware.
Patches are more or less split to first fix issues in current driver,
then adds support for WEP and finally for WPA.
Please test the driver if possible, and send me reports about any
possible bugs, or objections; I will try to implement required changes.
Unfortunately, I'm leaving for a vacation on July 6th up to July 17th,
so I will not be able to respond during this period.
Best regards,
Milan Plzik
reply other threads:[~2008-07-04 17:43 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=1215193415.4619.16.camel@localhost \
--to=milan.plzik@gmail.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).