From: Dave <kilroyd@googlemail.com>
To: David.Woodhouse@intel.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 00/19] orinoco: WPA for Agere based cards
Date: Fri, 22 Aug 2008 00:05:51 +0100 [thread overview]
Message-ID: <48ADF4CF.9090400@gmail.com> (raw)
In-Reply-To: <1219357685-24731-1-git-send-email-kilroyd@gmail.com>
On 21 Aug, kilroyd@googlemail.com wrote:
> This patch series enables WPA on Agere based orinoco devices.
<snip>=20
> To use WPA, you will need an Agere firmware image. You can get the
> necessary file at
> <http://marc.info/?l=3Dorinoco-devel&m=3D121078835610877>, just extra=
ct
> 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=3Dorinoco-devel&m=3D120846933719051>.
Hi,
The quoted patchset introduces the capability to load firmware for
a particular variant of the orinoco wireless cards. At the moment
the firmware image is only readily available in an email archive.
Can we include this firmware in the linux-firmware tree? If so
what do I need to do to get it there?
The firmware in the above link was originally distributed by Agere
within a driver with a BSD-style license. The only modification
I've made is to add a header defining offsets into the main image.
The original driver can still be found at
<http://www.xs4all.nl/~pptp/agere/wl_lkm_718_release.tar.gz>. I've
included the text of the license below.
Thanks,
Dave Kilroy.
---
License extracted from hcf/hcf.c
* SOFTWARE LICENSE
*
* This software is provided subject to the following terms and conditi=
ons,
* which you should read carefully before using the software. Using th=
is
* software indicates your acceptance of these terms and conditions. I=
f you do
* not agree with these terms and conditions, do not use the software.
*
* COPYRIGHT =A9 1994 - 1995 by AT&T. All Rights Reserv=
ed
* COPYRIGHT =A9 1996 - 2000 by Lucent Technologies. All Rights Reserv=
ed
* COPYRIGHT =A9 2001 - 2004 by Agere Systems Inc. All Rights Reserv=
ed
* All rights reserved.
*
* Redistribution and use in source or binary forms, with or without
* modifications, are permitted provided that the following conditions =
are met:
*
* . Redistributions of source code must retain the above copyright not=
ice, this
* list of conditions and the following Disclaimer as comments in th=
e code as
* well as in the documentation and/or other materials provided with=
the
* distribution.
*
* . Redistributions in binary form must reproduce the above copyright =
notice,
* this list of conditions and the following Disclaimer in the docum=
entation
* and/or other materials provided with the distribution.
*
* . Neither the name of Agere Systems Inc. nor the names of the contri=
butors
* may be used to endorse or promote products derived from this soft=
ware
* without specific prior written permission.
*
* Disclaimer
*
* THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED WARRANT=
IES,
* INCLUDING, BUT NOT LIMITED TO, INFRINGEMENT AND THE IMPLIED WARRANTI=
ES OF
* MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.=
ANY
* USE, MODIFICATION OR DISTRIBUTION OF THIS SOFTWARE IS SOLELY AT THE =
USERS OWN
* RISK. IN NO EVENT SHALL AGERE SYSTEMS INC. OR CONTRIBUTORS BE LIABLE=
FOR ANY
* DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL D=
AMAGES
* (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR S=
ERVICES;
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAU=
SED AND
* ON ANY THEORY OF LIABILITY, INCLUDING, BUT NOT LIMITED TO, CONTRACT,=
STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN AN=
Y WAY OUT
* OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF S=
UCH
* DAMAGE.
--
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
prev parent reply other threads:[~2008-08-21 23:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 22:27 [PATCH v2 00/19] orinoco: WPA for Agere based cards kilroyd
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 ` Dave [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=48ADF4CF.9090400@gmail.com \
--to=kilroyd@googlemail.com \
--cc=David.Woodhouse@intel.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).