From: Ben Hutchings <ben@decadent.org.uk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH firmware 5/6] Add RT3090 firmware from rt2860sta
Date: Sat, 27 Feb 2010 21:32:27 +0000 [thread overview]
Message-ID: <1267306347.16186.109.camel@localhost> (raw)
In-Reply-To: <1267306076.16186.103.camel@localhost>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
---
The binary changes are omitted from this message as they are impossible
to review.
Ben.
WHENCE | 10 ++++++++++
rt3090.bin | Bin 0 -> 8192 bytes
2 files changed, 10 insertions(+), 0 deletions(-)
create mode 100644 rt3090.bin
diff --git a/WHENCE b/WHENCE
index ffc9248..d62468e 100644
--- a/WHENCE
+++ b/WHENCE
@@ -1000,6 +1000,16 @@ Downloaded from http://www.ralinktech.com/ralink/Home/Support/Linux.html
--------------------------------------------------------------------------
+Driver: rt2860sta - Ralink RT3090 wireless MACs
+
+File: rt3090.bin
+
+Licence: Redistributable. See LICENCE.ralink-firmware.txt for details
+
+Found in hex form in kernel source.
+
+--------------------------------------------------------------------------
+
Driver: rt2870sta - Ralink RT2870, RT3070, RT3071, RT3072 wireless MACs
File: rt2870.bin
next prev parent reply other threads:[~2010-02-27 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 21:27 Please pull 'upstream' branch of http://git.decadent.org.uk/git/linux-firmware.git Ben Hutchings
2010-02-27 21:29 ` [PATCH firmware 1/6] Correct various filenames Ben Hutchings
2010-02-27 21:30 ` [PATCH firmware 2/6] Use 'File:' field name in front of each filename Ben Hutchings
2010-02-27 21:30 ` [PATCH firmware 3/6] Specify drivers using firmware by module/object name Ben Hutchings
2010-02-27 21:31 ` [PATCH firmware 4/6] Update firmware from rt2870sta Ben Hutchings
2010-02-27 21:32 ` Ben Hutchings [this message]
2010-02-27 21:33 ` [PATCH firmware 6/6] Add firmware for lgs8g75 Ben Hutchings
2010-03-02 15:00 ` Mauro Carvalho Chehab
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=1267306347.16186.109.camel@localhost \
--to=ben@decadent.org.uk \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@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