RepoMirrors
/
linux-firmware
mirror of git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
linux-firmware/README

44 lines
1.6 KiB
Plaintext
Raw Normal View History

linux-firmware: add README basic info about how to submit files or patches. Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
2012-04-21 22:27:14 +00:00
Linux firmware
==============
<http://git.kernel.org/?p=linux/kernel/git/firmware/linux-firmware.git>
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
This 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 this repository, please send either a git binary
diff or preferably a git pull request to:
README: Update the submission address to linux-firmware@kernel.org This new alias will reach all maintainers. Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
2014-06-03 20:04:26 +00:00
linux-firmware@kernel.org
linux-firmware: add README basic info about how to submit files or patches. Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
2012-04-21 22:27:14 +00:00
and also cc: to related mailing lists.
README: Say that files must be listed in WHENCE, and how to check it - Say that new files must, not 'should', be listed in WHENCE - State the expected form of a reference to a separate licence file - Mention 'make check' Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
2016-09-18 01:47:17 +00:00
If your commit adds new firmware, it must update the WHENCE file to
clearly state the license under which the firmware is available, and
README: clarify redistribution requirements covering patents Firmware licenses on linux-firmware should include an implicit or explicit patent grant to end users for full device operation otherwise it would start making linux-firmware useless for many Linux distributions which have positions against patent encumbered software [0] [1] [2] and it would mean cherry picking firmware files out. It can also mean making it problematic to redistribute linux-firmware in some jurisdictions which could have different positions on patents, or have already outlawed software patents. Licenses with implicit patent grants are allowed given that otherwise we couldn't carry permissively licensed firmwares which would be silly, but using permissively licensed firmware files which remove patent grants explicitly are not allowed. A clarifications is needed as one attempt was already made to include firmware encumbered by patents without a grant [3] and it was decided we would not allow these. We clarify this to make this requirement explicit and prevent these type of further attempts. [0] https://www.debian.org/legal/patent [1] http://fedoraproject.org/wiki/Software_Patents#Red_Hat.27s_position_on_Software_Patents [2] http://www.openinventionnetwork.com/about-us/ [3] https://lkml.org/lkml/2014/3/14/182 Cc: netdev@vger.kernel.org Cc: linux-wireless@vger.kernel.org Cc: linux-kernel@vger.kernel.org Signed-off-by: Luis R. Rodriguez <mcgrof@suse.com> Signed-off-by: Kyle McMartin <kyle@kernel.org>
2015-05-19 20:22:31 +00:00
that it is redistributable. Being redistributable includes ensuring
the firmware license provided includes an implicit or explicit
patent grant to end users to ensure full functionality of device
operation with the firmware. If the license is long and involved, it's
linux-firmware: add README basic info about how to submit files or patches. Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
2012-04-21 22:27:14 +00:00
permitted to include it in a separate file and refer to it from the
README: Say that files must be listed in WHENCE, and how to check it - Say that new files must, not 'should', be listed in WHENCE - State the expected form of a reference to a separate licence file - Mention 'make check' Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
2016-09-18 01:47:17 +00:00
WHENCE file ('See LICENSE.foo for details.').
linux-firmware: add README basic info about how to submit files or patches. Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
2012-04-21 22:27:14 +00:00
And if it were possible, a changelog of the firmware itself.
README: Say that files must be listed in WHENCE, and how to check it - Say that new files must, not 'should', be listed in WHENCE - State the expected form of a reference to a separate licence file - Mention 'make check' Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
2016-09-18 01:47:17 +00:00
Run 'make check' to check that WHENCE is consistent with the
repository contents.
linux-firmware: add README basic info about how to submit files or patches. Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
2012-04-21 22:27:14 +00:00
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.