linux-stable/firmware
Luis R. Rodriguez 0cd5246bf8 firmware/Makefile: force recompilation if makefile changes
If you modify the target asm we currently do not force the recompilation
of the firmware files.  The target asm is in the firmware/Makefile, peg
this file as a dependency to require re-compilation of firmware targets
when the asm changes.

Link: http://lkml.kernel.org/r/20170123150727.4883-1-mcgrof@kernel.org
Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Michal Marek <mmarek@suse.com>
Cc: Ming Lei <ming.lei@canonical.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Tom Gundersen <teg@jklm.no>
Cc: David Woodhouse <dwmw2@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2017-05-08 17:15:10 -07:00
..
3com tokenring: delete all remaining driver support 2012-05-15 20:23:16 -04:00
acenic
adaptec
advansys
av7110
bnx2 bnx2: Update firmware and version 2011-03-14 15:00:12 -07:00
bnx2x bnx2x: Update firmware to 6.2.9 2011-03-31 17:03:36 -07:00
cis pcnet_cs: add cis of KTI PE520 pcmcia network card 2010-01-06 20:37:58 -08:00
cpia2
cxgb3 firmware: Remove obsolete Chelsio cxgb3 firmware 2012-08-02 06:23:25 -06:00
dsp56k
e100
edgeport
emi26
emi62 USB: emi62: Provide the correct bitstream firmware 2013-12-10 22:38:45 -08:00
ess
kaweth
keyspan
keyspan_pda Update broken web addresses in the kernel. 2010-10-18 11:03:14 +02:00
korg
matrox drm/mga: Use request_firmware() to load microcode 2009-08-27 10:46:54 +10:00
myricom
ositech
qlogic firmware,IB/qib: revert firmware file move 2013-04-05 12:19:39 -07:00
r128 drm/r128: Use request_firmware() to load CCE microcode 2009-08-27 10:47:00 +10:00
radeon radeon: Use request_firmware() 2009-08-31 09:09:30 +10:00
sb16
sun
tehuti
tigon
ttusb-budget
vicam
yam
yamaha
.gitignore
atmsar11.HEX
ihex2fw.c firmware/ihex2fw.c: restore missing default in switch statement 2015-04-17 09:03:56 -04:00
Makefile firmware/Makefile: force recompilation if makefile changes 2017-05-08 17:15:10 -07:00
mts_cdma.fw.ihex
mts_edge.fw.ihex
mts_gsm.fw.ihex
README.AddingFirmware firmware: Update information in linux.git about adding firmware 2015-05-07 09:48:42 -06:00
ti_3410.fw.ihex
ti_5052.fw.ihex
WHENCE WHENCE: use https://linuxtv.org for LinuxTV URLs 2015-12-04 10:35:11 -02:00
whiteheat.HEX
whiteheat_loader.HEX
whiteheat_loader_debug.HEX

	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.