Build firmware for rsu(4), rtwn(4), and urtwn(4).
We have to install the files with new filenames (removal of "fw" from each of
the filenames) and change the driver to use the new filenames,
such tha

Build firmware for rsu(4), rtwn(4), and urtwn(4).
We have to install the files with new filenames (removal of "fw" from each of
the filenames) and change the driver to use the new filenames,
such that the package becomes irrelevant.

Discussed with deraadt@ and sthen@

ok deraadt@

show more ...

"Dr. Jones. Again we see there is nothing you can possess which I cannot
take away."

remove uyap. no effect except on hppa where it was strangely enabled.

build firmware for myx(4)

enter afb

Add dev/microcode/udl/ to build.

Do enter the tigon directory, and build there, and ship them. We have tried
for many years to contact all the potential copyright owners and people who used
to distribute this (ie. wpaul and such),

Do enter the tigon directory, and build there, and ship them. We have tried
for many years to contact all the potential copyright owners and people who used
to distribute this (ie. wpaul and such), to get the original license text
clarified. We believe the original license on the source did specifically
allow re-distribution. We believe we have done enough in this situation,
especially considering how dead this product us. If anyone else knows more,
please let us know.
ok kettenis

show more ...

firmware (if not store in a seeprom in the device) for the uticom(4)
this was compiled by someone from the full source code published by TI
under a surprisingly free license (which is probably not ev

firmware (if not store in a seeprom in the device) for the uticom(4)
this was compiled by someone from the full source code published by TI
under a surprisingly free license (which is probably not even actually
enforceable in any way, since they forgot to put the phrase Copyright
above it... where do they hire their lawyers?? anyways, everyone benefits)

show more ...

descend into tht

enable bnx firmware builds

enter rum

permission from Zydas to include ZD1211 firmware

sort

- add preliminary support for Ralink Technology RT2561, RT2561S and RT2661
chipsets in ral(4).
- restructure the code a bit; split ic/ral.c into ic/rt2560.c and ic/rt2661.c
- import the 8051 microc

- add preliminary support for Ralink Technology RT2561, RT2561S and RT2661
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.

show more ...

no longer install the tigon firmware. Bill Paul, who built these firmwares
for the various *BSD projects, has not replied to various emails from me
trying to find out what the licensing status of th

no longer install the tigon firmware. Bill Paul, who built these firmwares
for the various *BSD projects, has not replied to various emails from me
trying to find out what the licensing status of these files are. In a few
weeks this firmware will be deleted from the tree. It's a real shame.
One again, people have played fast and loose with licensing and the law.

show more ...

Use vfs firmware loader for fxp(4) interrupt coalescing microcode.
Initial work by Dmitry Bogdan <bogdan@eastonline.ru> with a help
from me and Theo.

ok deraadt@

firmware loading from the filesystem. pci subsystem type things
are still done early, but audio subsystem setup is deferred till
after root is mounted. tested by mcbride

not yds yet

filesystem firmware loading written over the pacific 2 weeks ago, tested
by mickey

build uyap firmware

typhoon microcode file build

enter kue & symbol

build and install neomagic firmware

build & install tigon firmwares

flat firmware file creation and installation