| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Tested by me and James Hastings.
|
| |
|
|
|
| |
workarounds. Some of them will soon stand in the way of armv7.
Off to the attic you go.
|
| |
|
|
| |
ok deraadt@
|
| |
|
|
|
|
| |
hppa reverse-stack gives us a valuable test case, but most developers don't
have a 2nd one to proceed further with this.
ok kettenis
|
| | |
|
| |
|
|
| |
including the firmware for the rt2860!
|
| | |
|
| |
|
|
|
| |
factored out of the result binaries already. Still need to address non usb.
ok deraadt.
|
| |
|
|
|
|
|
|
|
| |
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@
|
| | |
|
| | |
|
|
|
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.
|