dchvs
/
Jetpack
forked from rrcarlosr/Jetpack
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Jetpack/kernel/kernel-4.9/firmware
History
dchvs 2b47ea911d Add CTI sources 
Elroy L4T r32.4.4 – JetPack 4.4.1
 		2021-01-25 16:30:42 -06:00
..
3com Add CTI sources 2021-01-25 16:30:42 -06:00
acenic Add CTI sources 2021-01-25 16:30:42 -06:00
adaptec Add CTI sources 2021-01-25 16:30:42 -06:00
advansys Add CTI sources 2021-01-25 16:30:42 -06:00
av7110 Add CTI sources 2021-01-25 16:30:42 -06:00
bnx2 Add CTI sources 2021-01-25 16:30:42 -06:00
bnx2x Add CTI sources 2021-01-25 16:30:42 -06:00
cis Add CTI sources 2021-01-25 16:30:42 -06:00
cpia2 Add CTI sources 2021-01-25 16:30:42 -06:00
cxgb3 Add CTI sources 2021-01-25 16:30:42 -06:00
dsp56k Add CTI sources 2021-01-25 16:30:42 -06:00
e100 Add CTI sources 2021-01-25 16:30:42 -06:00
edgeport Add CTI sources 2021-01-25 16:30:42 -06:00
emi26 Add CTI sources 2021-01-25 16:30:42 -06:00
emi62 Add CTI sources 2021-01-25 16:30:42 -06:00
ess Add CTI sources 2021-01-25 16:30:42 -06:00
kaweth Add CTI sources 2021-01-25 16:30:42 -06:00
keyspan Add CTI sources 2021-01-25 16:30:42 -06:00
keyspan_pda Add CTI sources 2021-01-25 16:30:42 -06:00
korg Add CTI sources 2021-01-25 16:30:42 -06:00
matrox Add CTI sources 2021-01-25 16:30:42 -06:00
myricom Add CTI sources 2021-01-25 16:30:42 -06:00
ositech Add CTI sources 2021-01-25 16:30:42 -06:00
qlogic Add CTI sources 2021-01-25 16:30:42 -06:00
r128 Add CTI sources 2021-01-25 16:30:42 -06:00
radeon Add CTI sources 2021-01-25 16:30:42 -06:00
sb16 Add CTI sources 2021-01-25 16:30:42 -06:00
sun Add CTI sources 2021-01-25 16:30:42 -06:00
tehuti Add CTI sources 2021-01-25 16:30:42 -06:00
tigon Add CTI sources 2021-01-25 16:30:42 -06:00
ttusb-budget Add CTI sources 2021-01-25 16:30:42 -06:00
vicam Add CTI sources 2021-01-25 16:30:42 -06:00
yam Add CTI sources 2021-01-25 16:30:42 -06:00
yamaha Add CTI sources 2021-01-25 16:30:42 -06:00
Makefile Add CTI sources 2021-01-25 16:30:42 -06:00
README.AddingFirmware Add CTI sources 2021-01-25 16:30:42 -06:00
WHENCE Add CTI sources 2021-01-25 16:30:42 -06:00
atmsar11.HEX Add CTI sources 2021-01-25 16:30:42 -06:00
ihex2fw.c Add CTI sources 2021-01-25 16:30:42 -06:00
mts_cdma.fw.ihex Add CTI sources 2021-01-25 16:30:42 -06:00
mts_edge.fw.ihex Add CTI sources 2021-01-25 16:30:42 -06:00
mts_gsm.fw.ihex Add CTI sources 2021-01-25 16:30:42 -06:00
ti_3410.fw.ihex Add CTI sources 2021-01-25 16:30:42 -06:00
ti_5052.fw.ihex Add CTI sources 2021-01-25 16:30:42 -06:00
whiteheat.HEX Add CTI sources 2021-01-25 16:30:42 -06:00
whiteheat_loader.HEX Add CTI sources 2021-01-25 16:30:42 -06:00
whiteheat_loader_debug.HEX Add CTI sources 2021-01-25 16:30:42 -06:00

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.