mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
synced 2025-12-17 10:44:43 +08:00
91ddce492d
A copyright notice is supposed to specify the years the work was created. Mauro Carvalho Chehab <mchehab@infradead.org> writes: > The oldest copyright I found for the Siano Linux driver is 2005, as > you can see at: > drivers/media/common/siano/smscoreapi.c > > As the driver talks with the Siano firmware, it has to be written > before or together with the driver. > > Browsing at the new, that seems to match the oldest news about the > first chipset supported by the driver (sms1000) is from 2006: > http://www.businesswire.com/news/home/20061206005282/en/Siano-SMS1000-Mobile-Digital-TV-Receiver-Chip > > This driver supports both the sms1xx and the newer sms27xx > chipsets. Due to that, the Rio firmware (ISDB-T) s probably newer, > as it support only the sms27xx chips, but it could be based on the > DVB-T firmware. > > So, if you really want to put some timestamp, except if someone > at either Siano or Hauppauge could tell us otherwise, I would stick > with a copyright notice starting from 2005, going u to the year that > they got merged at the firmware tree (as some changes might have > happened until the final version). So I'm specifying 2005-2014. Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
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:
linux-firmware@kernel.org
and also cc: to related mailing lists.
If your commit adds new firmware, it must update the WHENCE file to
clearly state the license under which the firmware is available, and
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
permitted to include it in a separate file and refer to it from the
WHENCE file ('See LICENSE.foo for details.').
And if it were possible, a changelog of the firmware itself.
Run 'make check' to check that WHENCE is consistent with the
repository contents.
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.