blob: bcb5f46aff832ed16e72478cb7bab61e7c932561
1 | |
2 | DO NOT ADD FIRMWARE TO THIS DIRECTORY. |
3 | ====================================== |
4 | |
5 | This directory is only here to contain firmware images extracted from old |
6 | device drivers which predate the common use of request_firmware(). |
7 | |
8 | As we update those drivers to use request_firmware() and keep a clean |
9 | separation between code and firmware, we put the extracted firmware |
10 | here. |
11 | |
12 | This directory is _NOT_ for adding arbitrary new firmware images. The |
13 | place to add those is the separate linux-firmware repository: |
14 | |
15 | git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git |
16 | |
17 | That repository contains all these firmware images which have been |
18 | extracted from older drivers, as well various new firmware images which |
19 | we were never permitted to include in a GPL'd work, but which we _have_ |
20 | been permitted to redistribute under separate cover. |
21 | |
22 | To submit firmware to that repository, please send either a git binary |
23 | diff or preferably a git pull request to: |
24 | linux-firmware@kernel.org |
25 | and also cc: to related mailing lists. |
26 | |
27 | Your commit should include an update to the WHENCE file clearly |
28 | identifying the licence under which the firmware is available, and |
29 | that it is redistributable. If the licence is long and involved, it's |
30 | permitted to include it in a separate file and refer to it from the |
31 | WHENCE file. |
32 | And if it were possible, a changelog of the firmware itself. |
33 | |
34 | Ideally, your commit should contain a Signed-Off-By: from someone |
35 | authoritative on the licensing of the firmware in question (i.e. from |
36 | within the company that owns the code). |
37 | |
38 | |
39 | WARNING: |
40 | ======= |
41 | |
42 | Don't send any "CONFIDENTIALITY STATEMENT" in your e-mail, patch or |
43 | request. Otherwise your firmware _will never be accepted_. |
44 | |
45 | Maintainers are really busy, so don't expect a prompt reply. |
46 |