aboutsummaryrefslogtreecommitdiffstats
path: root/firmware
diff options
context:
space:
mode:
authorDavid Woodhouse <David.Woodhouse@intel.com>2009-04-06 20:41:48 -0400
committerDavid Woodhouse <David.Woodhouse@intel.com>2009-04-07 00:04:17 -0400
commit0f8e5c298fc801e8eca69e1409604c05d36e0cc4 (patch)
tree1249d7762730ed56c8a782ceffe676b30790f8c1 /firmware
parentcec20f36d6e5a10db315714c6c3da90792368382 (diff)
Add README.AddingFirmware file. Basically telling people not to.
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'firmware')
-rw-r--r--firmware/README.AddingFirmware34
1 files changed, 34 insertions, 0 deletions
diff --git a/firmware/README.AddingFirmware b/firmware/README.AddingFirmware
new file mode 100644
index 000000000000..e24cd8986d8b
--- /dev/null
+++ b/firmware/README.AddingFirmware
@@ -0,0 +1,34 @@
1
2 DO NOT ADD FIRMWARE TO THIS DIRECTORY.
3 ======================================
4
5This directory is only here to contain firmware images extracted from old
6device drivers which predate the common use of request_firmware().
7
8As we update those drivers to use request_firmware() and keep a clean
9separation between code and firmware, we put the extracted firmware
10here.
11
12This directory is _NOT_ for adding arbitrary new firmware images. The
13place to add those is the separate linux-firmware repository:
14
15 git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git
16
17That repository contains all these firmware images which have been
18extracted from older drivers, as well various new firmware images which
19we were never permitted to include in a GPL'd work, but which we _have_
20been permitted to redistribute under separate cover.
21
22To submit firmware to that repository, please send either a git binary
23diff or preferably a git pull request to:
24 David Woodhouse <dwmw2@infradead.org>
25
26Your commit should include an update to the WHENCE file clearly
27identifying the licence under which the firmware is available, and
28that it is redistributable. If the licence is long and involved, it's
29permitted to include it in a separate file and refer to it from the
30WHENCE file.
31
32Ideally, your commit should contain a Signed-Off-By: from someone
33authoritative on the licensing of the firmware in question (i.e. from
34within the company that owns the code).