linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: users@rt2x00.serialmonkey.com, linux-wireless@vger.kernel.org
Subject: Re: Firmware files for Ralink RT28x0
Date: Sun, 10 Apr 2011 23:46:45 +0200	[thread overview]
Message-ID: <4DA22545.6050209@gmail.com> (raw)
In-Reply-To: <1302469406.5282.341.camel@localhost>

On 04/10/2011 11:03 PM, Ben Hutchings wrote:

> These files aren't used by the Ralink drivers.  So why should you
> believe the labels on them?

Because the hardware manufacturer says that:
http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2011-March/003380.html

Anyway, the firmware in staging(or ralink web) drivers look different because
they are different _versions_ of the _same_ firmware.

rt2870.bin: before 4096 bytes, now 8192 bytes.

> linux-firmware is not *actively* maintained; it requires people to send
> submissions (repeatedly...).

On 04/06/2010, *ONE YEAR AGO* , I sent a patch to rt2870.bin rt2860.bin.
It went to /dev/null

A similar patch was sent by the *driver maintainer* on 10/30/2010.
It went to /dev/null

The same patch was sent by the *hardware manufacturer* on 03/11/2011
It went to /dev/null

Torvalds, Mozart and God are pending.

> I think there may be a problem with distribution of Intel Pro Wireless
> firmware because Intel requires users to accept a EULA.

If it's included in Fedora then there are zero issues with licenses.

  parent reply	other threads:[~2011-04-10 21:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-10 19:25 Firmware files for Ralink RT28x0 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 [this message]
2011-04-10 22:37     ` Larry Finger
2011-04-10 22:56       ` Xose Vazquez Perez
2011-04-11  3:01         ` Larry Finger
2011-04-11  3:06         ` Firmware for rt2800pci and rt2800usb Larry Finger
2011-04-11  5:48           ` Steev Klimaszewski
2011-04-11  9:12           ` Gertjan van Wingerde
2011-04-11 13:01             ` Larry Finger
2011-04-11 13:32               ` Gertjan van Wingerde
2011-04-11 15:05               ` Johannes Stezenbach
2011-04-11 11:14           ` Juan Carlos Garza
2011-04-11 11:23             ` Ben Hutchings
2011-04-11 12:21               ` Juan Carlos Garza
2011-04-11 13:19               ` Larry Finger
2011-04-11 14:56           ` Chí-Thanh Christopher Nguyễn
  -- strict thread matches above, loose matches on Subject: below --
2011-04-10 17:29 Firmware files for Ralink RT28x0 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 17:02 Xose Vazquez Perez
2011-04-10 15:56 Ben Hutchings
2011-04-10 16:18 ` 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

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=4DA22545.6050209@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=linux-wireless@vger.kernel.org \
    --cc=users@rt2x00.serialmonkey.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).