From: kilroyd@googlemail.com
To: linux-wireless@vger.kernel.org
Cc: orinoco-devel@lists.sourceforge.net, David Kilroy <kilroyd@gmail.com>
Subject: [PATCH v2 00/19] orinoco: WPA for Agere based cards
Date: Thu, 21 Aug 2008 23:27:45 +0100 [thread overview]
Message-ID: <1219357685-24731-1-git-send-email-kilroyd@gmail.com> (raw)
This patch series enables WPA on Agere based orinoco devices.
Patchset overview
1-2: General scanning updates
3-9: Agere firmware download to RAM
10-12: Update orinoco to work with new firmware
13-19: WPA functionality
This patchset addresses a few issues raised the last time it was
submitted:
* fix compile/sparse warnings on 64 bit
* scan buffer size increased
The patchset is against wireless-testing (master-2008-08-20), is
sparse clean (UP), and should be bisectable. It is almost checkpatch
clean - the single warning looks like a false positive to me.
To use WPA, you will need an Agere firmware image. You can get the
necessary file at
<http://marc.info/?l=orinoco-devel&m=121078835610877>, just extract
and rename orinoco.fw to agere_sta_fw.bin and place it in
/lib/firmware (or distro equivalent). Alternatively you can try
extract firmware from a Windows driver using the program in
<http://marc.info/?l=orinoco-devel&m=120846933719051>.
Regards,
Dave.
next reply other threads:[~2008-08-21 22:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 22:27 kilroyd [this message]
2008-08-21 22:27 ` [PATCH v2 01/19] orinoco: Add ESSID specific scanning for Agere fw kilroyd
2008-08-21 22:27 ` [PATCH v2 02/19] orinoco: Update scan translation kilroyd
2008-08-21 22:27 ` [PATCH v2 03/19] orinoco: Specify all three parameters to every Hermes command kilroyd
2008-08-21 22:27 ` [PATCH v2 04/19] orinoco: Move EXPORT_SYMBOL declarations next to exported function kilroyd
2008-08-21 22:27 ` [PATCH v2 05/19] orinoco: Add function to execute Hermes initialisation commands synchronously kilroyd
2008-08-21 22:27 ` [PATCH v2 06/19] orinoco: Move firmware download functionality into new module kilroyd
2008-08-21 22:27 ` [PATCH v2 07/19] orinoco: Make firmware download logic more generic kilroyd
2008-08-21 22:27 ` [PATCH v2 08/19] orinoco: Extend hermes_dld routines for Agere firmware kilroyd
2008-08-21 22:27 ` [PATCH v2 09/19] orinoco: Invoke firmware download in main driver kilroyd
2008-08-21 22:27 ` [PATCH v2 10/19] orinoco: Fix transmit for Agere/Lucent with fw 9.x kilroyd
2008-08-21 22:27 ` [PATCH v2 11/19] orinoco: address checkpatch typedef warning kilroyd
2008-08-21 22:27 ` [PATCH v2 12/19] orinoco: Use extended Agere scans available on 9.x series firmwares kilroyd
2008-08-21 22:27 ` [PATCH v2 13/19] orinoco: Don't use boolean parameter to record encoding type kilroyd
2008-08-21 22:28 ` [PATCH v2 14/19] orinoco: Split wevent work thread from wevent sending kilroyd
2008-08-21 22:28 ` [PATCH v2 15/19] orinoco: Use a macro to define wireless handlers kilroyd
2008-08-21 22:28 ` [PATCH v2 16/19] orinoco: Add WE-18 ioctls for WPA kilroyd
2008-08-21 22:28 ` [PATCH v2 17/19] orinoco: Send association events to userspace kilroyd
2008-08-21 22:28 ` [PATCH v2 18/19] orinoco: Process bulk of receive interrupt in a tasklet kilroyd
2008-08-21 22:28 ` [PATCH v2 19/19] orinoco: Add MIC on TX and check on RX kilroyd
2008-08-21 23:05 ` [PATCH v2 00/19] orinoco: WPA for Agere based cards Dave
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=1219357685-24731-1-git-send-email-kilroyd@gmail.com \
--to=kilroyd@googlemail.com \
--cc=kilroyd@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=orinoco-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;
as well as URLs for NNTP newsgroup(s).