From: Ben Hutchings <ben@decadent.org.uk>
To: Ivo van Doorn <IvDoorn@gmail.com>,
Gertjan van Wingerde <gwingerde@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Firmware files for Ralink RT28x0
Date: Sun, 10 Apr 2011 16:56:02 +0100 [thread overview]
Message-ID: <1302450962.5282.129.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
I notice that rt2800{pci,usb} each specify only one firmware image,
regardless of the controller version.
This is inconsistent with rt28{6,7}0sta and with the firmware images in
linux-firmware.
If you think that a single image per bus type can cover all controllers,
please identify those firmware images, test them on each hardware
generation, and get them into linux-firmware.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next reply other threads:[~2011-04-10 15:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 15:56 Ben Hutchings [this message]
2011-04-10 16:18 ` Firmware files for Ralink RT28x0 Larry Finger
2011-04-10 16:35 ` Ivo Van Doorn
2011-04-10 17:49 ` Ben Hutchings
2011-04-10 18:06 ` Ivo Van Doorn
2011-04-10 19:04 ` Ben Hutchings
-- strict thread matches above, loose matches on Subject: below --
2011-04-10 17:02 Xose Vazquez Perez
2011-04-10 17:29 Xose Vazquez Perez
2011-04-10 17:35 ` Ivo Van Doorn
2011-04-10 18:12 ` Xose Vazquez Perez
2011-04-10 18:26 ` Larry Finger
2011-04-10 19:25 Xose Vazquez Perez
2011-04-10 21:03 ` Ben Hutchings
2011-04-10 21:30 ` Larry Finger
2011-04-10 21:46 ` Xose Vazquez Perez
2011-04-10 22:37 ` Larry Finger
2011-04-10 22:56 ` Xose Vazquez Perez
2011-04-11 3:01 ` Larry Finger
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=1302450962.5282.129.camel@localhost \
--to=ben@decadent.org.uk \
--cc=IvDoorn@gmail.com \
--cc=gwingerde@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.