]>
Commit | Line | Data |
---|---|---|
9b414888 XVP |
1 | |
2 | Linux firmware | |
3 | ============== | |
4 | ||
5 | <http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git> | |
6 | ||
7 | git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git | |
8 | ||
9 | This repository contains all these firmware images which have been | |
10 | extracted from older drivers, as well various new firmware images which | |
11 | we were never permitted to include in a GPL'd work, but which we _have_ | |
12 | been permitted to redistribute under separate cover. | |
13 | ||
14 | To submit firmware to this repository, please send either a git binary | |
15 | diff or preferably a git pull request to: | |
a4f3bc03 | 16 | linux-firmware@kernel.org |
9b414888 XVP |
17 | and also cc: to related mailing lists. |
18 | ||
19 | Your commit should include an update to the WHENCE file clearly | |
20 | identifying the licence under which the firmware is available, and | |
21 | that it is redistributable. If the licence is long and involved, it's | |
22 | permitted to include it in a separate file and refer to it from the | |
23 | WHENCE file. | |
24 | And if it were possible, a changelog of the firmware itself. | |
25 | ||
26 | Ideally, your commit should contain a Signed-Off-By: from someone | |
27 | authoritative on the licensing of the firmware in question (i.e. from | |
28 | within the company that owns the code). | |
29 | ||
30 | ||
31 | WARNING: | |
32 | ======= | |
33 | ||
34 | Don't send any "CONFIDENTIALITY STATEMENT" in your e-mail, patch or | |
35 | request. Otherwise your firmware _will never be accepted_. | |
36 | ||
37 | Maintainers are really busy, so don't expect a prompt reply. |