H3-BSP4-4-linux/firmware
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2017-12-01 01:00:54 +08:00
..
3com first commit 2017-12-01 01:00:54 +08:00
acenic first commit 2017-12-01 01:00:54 +08:00
adaptec first commit 2017-12-01 01:00:54 +08:00
advansys first commit 2017-12-01 01:00:54 +08:00
av7110 first commit 2017-12-01 01:00:54 +08:00
bnx2 first commit 2017-12-01 01:00:54 +08:00
bnx2x first commit 2017-12-01 01:00:54 +08:00
cis first commit 2017-12-01 01:00:54 +08:00
cpia2 first commit 2017-12-01 01:00:54 +08:00
cxgb3 first commit 2017-12-01 01:00:54 +08:00
dsp56k first commit 2017-12-01 01:00:54 +08:00
e100 first commit 2017-12-01 01:00:54 +08:00
edgeport first commit 2017-12-01 01:00:54 +08:00
emi26 first commit 2017-12-01 01:00:54 +08:00
emi62 first commit 2017-12-01 01:00:54 +08:00
ess first commit 2017-12-01 01:00:54 +08:00
kaweth first commit 2017-12-01 01:00:54 +08:00
keyspan first commit 2017-12-01 01:00:54 +08:00
keyspan_pda first commit 2017-12-01 01:00:54 +08:00
korg first commit 2017-12-01 01:00:54 +08:00
matrox first commit 2017-12-01 01:00:54 +08:00
myricom first commit 2017-12-01 01:00:54 +08:00
ositech first commit 2017-12-01 01:00:54 +08:00
qlogic first commit 2017-12-01 01:00:54 +08:00
r128 first commit 2017-12-01 01:00:54 +08:00
radeon first commit 2017-12-01 01:00:54 +08:00
sb16 first commit 2017-12-01 01:00:54 +08:00
sun first commit 2017-12-01 01:00:54 +08:00
tehuti first commit 2017-12-01 01:00:54 +08:00
tigon first commit 2017-12-01 01:00:54 +08:00
ttusb-budget first commit 2017-12-01 01:00:54 +08:00
vicam first commit 2017-12-01 01:00:54 +08:00
yam first commit 2017-12-01 01:00:54 +08:00
yamaha first commit 2017-12-01 01:00:54 +08:00
atmsar11.HEX first commit 2017-12-01 01:00:54 +08:00
ihex2fw.c first commit 2017-12-01 01:00:54 +08:00
Makefile first commit 2017-12-01 01:00:54 +08:00
mts_cdma.fw.ihex first commit 2017-12-01 01:00:54 +08:00
mts_edge.fw.ihex first commit 2017-12-01 01:00:54 +08:00
mts_gsm.fw.ihex first commit 2017-12-01 01:00:54 +08:00
README.AddingFirmware first commit 2017-12-01 01:00:54 +08:00
ti_3410.fw.ihex first commit 2017-12-01 01:00:54 +08:00
ti_5052.fw.ihex first commit 2017-12-01 01:00:54 +08:00
WHENCE first commit 2017-12-01 01:00:54 +08:00
whiteheat.HEX first commit 2017-12-01 01:00:54 +08:00
whiteheat_loader.HEX first commit 2017-12-01 01:00:54 +08:00
whiteheat_loader_debug.HEX first commit 2017-12-01 01:00:54 +08:00

	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.