From: "John W. Linville" <linville@tuxdriver.com>
To: Karl Relton <karllinuxtest.relton@ntlworld.com>
Cc: dwmw2@infradead.org, linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: [PATCH] Add prism 2/3 usb adaptor firmware for use with staging/wlan-ng driver.
Date: Tue, 30 Jun 2009 15:39:30 -0400 [thread overview]
Message-ID: <20090630193930.GD2722@tuxdriver.com> (raw)
In-Reply-To: <1246388712.4949.52.camel@localhost>
On Tue, Jun 30, 2009 at 08:05:12PM +0100, Karl Relton wrote:
> +
> +--------------------------------------------------------------------------
> +
> +Driver: staging/wlan-ng - prism 2/3 usb 802.11 wireless lan adapters
> +
> +File: prism2_ru.hex
> +
> +License:
> +
> +The following binary firmware files are (c) Conexant, and do not fall
> +under the GPL or MPL. They are assumed to have the same license as
> +their windows client drivers, ie everyone who bought a card that came
> +with a windows driver already has a copy of and license to use the
> +necessary firmware, albeit possibly an older version. These were bundled
> +with linux-wlan-ng for convenience only, as many newer adapters
> +(eg Prism 3 w/SSF) require a firmware download in order to function at
> +all.
> +
> +As far as is known, the last copyright holder of these
> +binaries was Conexant and that they were freely distributed.
Is this really good enough? What is the difference between the above
and cutting firmware images out of the (freely distributed) Broadcom
drivers for Windows?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
¡Viva Honduras Libre!
prev parent reply other threads:[~2009-06-30 19:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 19:05 [PATCH] Add prism 2/3 usb adaptor firmware for use with staging/wlan-ng driver Karl Relton
2009-06-30 19:17 ` Luis R. Rodriguez
2009-06-30 21:09 ` Karl Relton
2009-06-30 21:58 ` Luis R. Rodriguez
2009-07-01 16:16 ` Karl Relton
2009-07-01 17:14 ` Luis R. Rodriguez
2009-07-01 17:22 ` Pavel Roskin
2009-07-01 17:51 ` Dave
2009-07-01 18:12 ` Luis R. Rodriguez
2009-07-01 18:35 ` Dan Williams
2009-07-01 19:36 ` Insist on cfg80211 for new drivers? John W. Linville
2009-07-01 19:49 ` Luis R. Rodriguez
2009-07-01 19:53 ` Johannes Berg
2009-07-01 20:40 ` Kalle Valo
2009-07-01 21:52 ` Marcel Holtmann
2009-07-01 21:56 ` Luis R. Rodriguez
2009-07-01 22:08 ` Marcel Holtmann
2009-07-01 22:13 ` Greg KH
2009-07-01 22:18 ` Marcel Holtmann
2009-07-01 22:42 ` Greg KH
2009-07-02 11:07 ` Bartlomiej Zolnierkiewicz
2009-07-02 12:44 ` Dan Williams
2009-07-02 9:19 ` Christoph Hellwig
2009-07-06 12:52 ` Johannes Berg
2009-07-06 14:23 ` John W. Linville
2009-07-06 14:45 ` Larry Finger
2009-07-06 14:57 ` Johannes Berg
2009-07-06 15:05 ` Nick Kossifidis
2009-07-01 19:46 ` [PATCH] Add prism 2/3 usb adaptor firmware for use with staging/wlan-ng driver David Woodhouse
2009-07-02 16:59 ` Karl Relton
2009-06-30 19:39 ` John W. Linville [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=20090630193930.GD2722@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dwmw2@infradead.org \
--cc=karllinuxtest.relton@ntlworld.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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 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).