path: root/firmware
diff options
authorDavid Woodhouse <David.Woodhouse@intel.com>2009-04-06 17:41:48 -0700
committerDavid Woodhouse <David.Woodhouse@intel.com>2009-04-06 21:04:17 -0700
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')
1 files changed, 34 insertions, 0 deletions
diff --git a/firmware/README.AddingFirmware b/firmware/README.AddingFirmware
new file mode 100644
index 00000000000..e24cd8986d8
--- /dev/null
+++ b/firmware/README.AddingFirmware
@@ -0,0 +1,34 @@
+ ======================================
+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
+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/dwmw2/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:
+ David Woodhouse <dwmw2@infradead.org>
+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.
+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).