rt2x00: Update rt2860/rt2870 firmware
Quoted 2 lines · Ivo van Doorn
Update rt2860 and rt2870 to the latest version, as extracted from the latest legacy drivers from the Ralink website.
ping!
linux-firmware still brings older ones.
is there any wrong ?
Quoted 10 lines · Xose Vazquez Perez
Quoted 2 lines · Ivo van Doorn
Update rt2860 and rt2870 to the latest version, as extracted from the latest legacy drivers from the Ralink website.
ping!
linux-firmware still brings older ones.
is there any wrong ?
pong! Ivo ?
Hi,
Quoted 10 lines
Quoted 8 lines
Quoted 2 lines
Update rt2860 and rt2870 to the latest version, as extracted from the latest legacy drivers from the Ralink website.
ping!
linux-firmware still brings older ones.
is there any wrong ?
pong! Ivo ?
I have already send a patch to update the
firmwares some time ago already.
If there is another update, feel free to send a new patch to the linux-firmware maintainer.
Ivo
Quoted 5 lines · Ivo Van Doorn
I have already send a patch to update the
firmwares some time ago already.If there is another update, feel free to send a new patch to the linux-firmware maintainer.
I did it _ten_ months ago, but no luck. So I asked you to do it. Again to /dev/null. Thanks anyway.
next step?
Quoted 5 lines · Xose Vazquez Perez
Quoted 3 lines · Ivo Van Doorn
I have already send a patch to update the
firmwares some time ago already.
Quoted 7 lines
Quoted 2 lines
If there is another update, feel free to send a new patch to the linux-firmware maintainer.
I did it _ten_ months ago, but no luck. So I asked you to do it. Again to
/dev/null. Thanks anyway.next step?
Did your proposed change have a good/strong reference to the license file in WHENCE? My experience is that the maintainer drops changes that do not, usually without comment. I also found that "found in hex form in source" did not work the way it did for your previous versions. Only when I provided a license from the vendor did I get anywhere. Is LICENCE.ralink-firmware.txt valid for this new version?
Larry
Quoted 5 lines · Larry Finger
Did your proposed change have a good/strong reference to the license file in WHENCE? My experience is that the maintainer drops changes that do not, usually without comment. I also found that "found in hex form in source" did not work the way it did for your previous versions. Only when I provided a license from the vendor did I get anywhere. Is LICENCE.ralink-firmware.txt valid for this new version?
I didn't see any wrong in my patch. LICENCE.ralink-firmware.txt has not changed.
Maybe someone from @ralink can send an 'official' request.
Signature · 4 lines
«Allá muevan feroz guerra, ciegos reyes por un palmo más de tierra; que yo aquí tengo por mío cuanto abarca el mar bravío, a quien nadie impuso leyes. Y no hay playa, sea cualquiera, ni bandera de esplendor, que no sienta mi derecho y dé pecho a mi valor.»