We cannot include them because that is a direct violation of the GPL license, if the firmware was GPL then perhaps it could be added, but even then it is not recommended since it is much cleaner to read the file and dump that into the registers. That will also allow users to upgrade the firmware image without upgrading the kernel.
It seems that Linux general firmware policy is to include them in the driver rather then in separate file:
<kernel dir>/drivers/net/typhoon-firmware.h - BSD license! yet still in kernel mainline and no GPL volation
<kernel dir>drivers/net/tokenring/3c359_microcode.h even better:
* The firmware this driver downloads into the tokenring card is a
* separate program and is not GPL'd source code, even though the Linux
* side driver and the routine that loads this data into the card are.
* This firmware is licensed to you strictly for use in conjunction
* with the use of 3Com 3C359 TokenRing adapters. There is no
* waranty expressed or implied about its fitness for any purpose.
Any way OpenBSD developers asked for ISC licensed firmware and they got one:
http://www.openbsd.org/cgi-bin/cvsweb/s ... ocode/ral/
http://www.openbsd.org/cgi-bin/cvsweb/s ... web-markup
How about asking Ralink for GPL microcode (or use ISC one)