You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
sandy ec51644259 pl283 349pulus 7 release code 4 years ago
..
3com pl283 349pulus 7 release code 4 years ago
acenic pl283 349pulus 7 release code 4 years ago
adaptec pl283 349pulus 7 release code 4 years ago
advansys pl283 349pulus 7 release code 4 years ago
av7110 pl283 349pulus 7 release code 4 years ago
bnx2 pl283 349pulus 7 release code 4 years ago
bnx2x pl283 349pulus 7 release code 4 years ago
cis pl283 349pulus 7 release code 4 years ago
cpia2 pl283 349pulus 7 release code 4 years ago
cxgb3 pl283 349pulus 7 release code 4 years ago
dsp56k pl283 349pulus 7 release code 4 years ago
e100 pl283 349pulus 7 release code 4 years ago
edgeport pl283 349pulus 7 release code 4 years ago
emi26 pl283 349pulus 7 release code 4 years ago
emi62 pl283 349pulus 7 release code 4 years ago
ess pl283 349pulus 7 release code 4 years ago
kaweth pl283 349pulus 7 release code 4 years ago
keyspan pl283 349pulus 7 release code 4 years ago
keyspan_pda pl283 349pulus 7 release code 4 years ago
korg pl283 349pulus 7 release code 4 years ago
matrox pl283 349pulus 7 release code 4 years ago
myricom pl283 349pulus 7 release code 4 years ago
ositech pl283 349pulus 7 release code 4 years ago
qlogic pl283 349pulus 7 release code 4 years ago
r128 pl283 349pulus 7 release code 4 years ago
radeon pl283 349pulus 7 release code 4 years ago
sb16 pl283 349pulus 7 release code 4 years ago
sun pl283 349pulus 7 release code 4 years ago
tehuti pl283 349pulus 7 release code 4 years ago
tigon pl283 349pulus 7 release code 4 years ago
ttusb-budget pl283 349pulus 7 release code 4 years ago
vicam pl283 349pulus 7 release code 4 years ago
yam pl283 349pulus 7 release code 4 years ago
yamaha pl283 349pulus 7 release code 4 years ago
Makefile pl283 349pulus 7 release code 4 years ago
README.AddingFirmware pl283 349pulus 7 release code 4 years ago
WHENCE pl283 349pulus 7 release code 4 years ago
atmsar11.HEX pl283 349pulus 7 release code 4 years ago
ihex2fw.c pl283 349pulus 7 release code 4 years ago
mts_cdma.fw.ihex pl283 349pulus 7 release code 4 years ago
mts_edge.fw.ihex pl283 349pulus 7 release code 4 years ago
mts_gsm.fw.ihex pl283 349pulus 7 release code 4 years ago
ti_3410.fw.ihex pl283 349pulus 7 release code 4 years ago
ti_5052.fw.ihex pl283 349pulus 7 release code 4 years ago
whiteheat.HEX pl283 349pulus 7 release code 4 years ago
whiteheat_loader.HEX pl283 349pulus 7 release code 4 years ago
whiteheat_loader_debug.HEX pl283 349pulus 7 release code 4 years ago

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:
linux-firmware@kernel.org
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.