jianglin 1c85872cc8 create repository 4 jaren geleden
..
3com 1c85872cc8 create repository 4 jaren geleden
acenic 1c85872cc8 create repository 4 jaren geleden
adaptec 1c85872cc8 create repository 4 jaren geleden
advansys 1c85872cc8 create repository 4 jaren geleden
av7110 1c85872cc8 create repository 4 jaren geleden
bnx2 1c85872cc8 create repository 4 jaren geleden
bnx2x 1c85872cc8 create repository 4 jaren geleden
cis 1c85872cc8 create repository 4 jaren geleden
cpia2 1c85872cc8 create repository 4 jaren geleden
cxgb3 1c85872cc8 create repository 4 jaren geleden
dsp56k 1c85872cc8 create repository 4 jaren geleden
e100 1c85872cc8 create repository 4 jaren geleden
edgeport 1c85872cc8 create repository 4 jaren geleden
emi26 1c85872cc8 create repository 4 jaren geleden
emi62 1c85872cc8 create repository 4 jaren geleden
ess 1c85872cc8 create repository 4 jaren geleden
kaweth 1c85872cc8 create repository 4 jaren geleden
keyspan 1c85872cc8 create repository 4 jaren geleden
keyspan_pda 1c85872cc8 create repository 4 jaren geleden
korg 1c85872cc8 create repository 4 jaren geleden
matrox 1c85872cc8 create repository 4 jaren geleden
myricom 1c85872cc8 create repository 4 jaren geleden
ositech 1c85872cc8 create repository 4 jaren geleden
qlogic 1c85872cc8 create repository 4 jaren geleden
r128 1c85872cc8 create repository 4 jaren geleden
radeon 1c85872cc8 create repository 4 jaren geleden
sb16 1c85872cc8 create repository 4 jaren geleden
sun 1c85872cc8 create repository 4 jaren geleden
tehuti 1c85872cc8 create repository 4 jaren geleden
tigon 1c85872cc8 create repository 4 jaren geleden
ttusb-budget 1c85872cc8 create repository 4 jaren geleden
vicam 1c85872cc8 create repository 4 jaren geleden
yam 1c85872cc8 create repository 4 jaren geleden
yamaha 1c85872cc8 create repository 4 jaren geleden
.gitignore 1c85872cc8 create repository 4 jaren geleden
Makefile 1c85872cc8 create repository 4 jaren geleden
README.AddingFirmware 1c85872cc8 create repository 4 jaren geleden
WHENCE 1c85872cc8 create repository 4 jaren geleden
atmsar11.HEX 1c85872cc8 create repository 4 jaren geleden
ihex2fw.c 1c85872cc8 create repository 4 jaren geleden
mts_cdma.fw.ihex 1c85872cc8 create repository 4 jaren geleden
mts_edge.fw.ihex 1c85872cc8 create repository 4 jaren geleden
mts_gsm.fw.ihex 1c85872cc8 create repository 4 jaren geleden
ti_3410.fw.ihex 1c85872cc8 create repository 4 jaren geleden
ti_5052.fw.ihex 1c85872cc8 create repository 4 jaren geleden
whiteheat.HEX 1c85872cc8 create repository 4 jaren geleden
whiteheat_loader.HEX 1c85872cc8 create repository 4 jaren geleden
whiteheat_loader_debug.HEX 1c85872cc8 create repository 4 jaren geleden

README.AddingFirmware


DO NOT ADD FIRMWARE TO THIS DIRECTORY.
======================================

This directory is only here to contain firmware images extracted from old
device drivers which predate the common use of request_firmware().

As we update those drivers to use request_firmware() and keep a clean
separation between code and firmware, we put the extracted firmware
here.

This directory is _NOT_ for adding arbitrary new firmware images. The
place to add those is the separate linux-firmware repository:

git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git

That repository contains all these firmware images which have been
extracted from older drivers, as well various new firmware images which
we were never permitted to include in a GPL'd work, but which we _have_
been permitted to redistribute under separate cover.

To submit firmware to that repository, please send either a git binary
diff or preferably a git pull request to:
[email protected]
and also cc: to related mailing lists.

Your commit should include an update to the WHENCE file clearly
identifying the licence under which the firmware is available, and
that it is redistributable. If the licence is long and involved, it's
permitted to include it in a separate file and refer to it from the
WHENCE file.
And if it were possible, a changelog of the firmware itself.

Ideally, your commit should contain a Signed-Off-By: from someone
authoritative on the licensing of the firmware in question (i.e. from
within the company that owns the code).


WARNING:
=======

Don't send any "CONFIDENTIALITY STATEMENT" in your e-mail, patch or
request. Otherwise your firmware _will never be accepted_.

Maintainers are really busy, so don't expect a prompt reply.