summaryrefslogtreecommitdiffstats
path: root/sys/dev/microcode/ral (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Initial bits for >=RT3090 support.damien2010-04-051-391/+391
| | | | | | | Probably not functionnal yet (but test reports are welcome). Update microcode for RT2860 while I'm here (remember to run make && make install under sys/dev/microcode/ral/).
* Build ral firmware on loongson (for Gdium).miod2010-02-091-6/+6
|
* fix a comment. no binary change.damien2008-04-151-2/+2
|
* Adjust a date correctly; spotted by jsgderaadt2008-03-061-2/+2
|
* New license from Paul Lin at Ralink; same terms, but now alsoderaadt2008-03-064-7/+757
| | | | including the firmware for the rt2860!
* cats went awayderaadt2007-08-011-4/+4
|
* Allow usb microcode to be built in a cross environment. System endian has beendrahn2007-04-051-1/+2
| | | | | factored out of the result binaries already. Still need to address non usb. ok deraadt.
* Clarify what hardware firmware is for.jsg2006-11-091-0/+2
|
* Separate rum(4) firmware from ral(4) ones.damien2006-08-174-196/+5
| | | | | | | | | ral(4) firmwares are built on PCI-capable architectures only while rum(4) firmware is built on USB-capable architectures only. Rename ral-rt2573 into rum-rt2573 and build rum-rt2573 on the zaurus too (pointed out by Patrick Heim). ok deraadt@
* - add rt2573 microcode. mostly from jolan@.niallo2006-06-164-5/+196
|
* System build pieces for armish arch.drahn2006-06-061-6/+6
|
* list the files the license applies toderaadt2006-01-101-0/+4
|
* - add preliminary support for Ralink Technology RT2561, RT2561S and RT2661damien2006-01-094-0/+2373
chipsets in ral(4). - restructure the code a bit; split ic/ral.c into ic/rt2560.c and ic/rt2661.c - import the 8051 microcode files required by these chipsets. - more to come; there is currently no automatic rate control and some features are untested (hostap and ibss modes for instance). most of the pre-802.11n capabilities of the RT2661 chipset are not supported (like frame aggregation, piggy-back). MIMO should work though the performance/range gain has not been measured.