License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license of the kernel, which is GPL version 2.
Update the files which contain no license information with the 'GPL-2.0'
SPDX license identifier. The SPDX identifier is a legally binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the use cases:
- file had no licensing information it it.
- file was a */uapi/* one with no licensing information in it,
- file was a */uapi/* one with existing licensing information,
Further patches will be generated in subsequent months to fix up cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base worksheet, and did an initial spot review of a few 1000 files.
The 4.13 kernel was the starting point of the analysis with 60,537 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately clear with lawyers working with the Linux Foundation.
Criteria used to select files for SPDX license identifier tagging was:
- Files considered eligible had to be source code files.
- Make and config files were included as candidates if they contained >5
lines of source
- File already had some variant of a license header in it (even if <5
lines).
All documentation files were explicitly excluded.
The following heuristics were used to determine which SPDX license
identifiers to apply.
- when both scanners couldn't find any license traces, file was
considered to have no license information in it, and the top level
COPYING file license applied.
For non */uapi/* files that summary was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 11139
and resulted in the first patch in this series.
If that file was a */uapi/* path one, it was "GPL-2.0 WITH
Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was:
SPDX license identifier # files
---------------------------------------------------|-------
GPL-2.0 WITH Linux-syscall-note 930
and resulted in the second patch in this series.
- if a file had some form of licensing information in it, and was one
of the */uapi/* ones, it was denoted with the Linux-syscall-note if
any GPL family license was found in the file or had no licensing in
it (per prior point). Results summary:
SPDX license identifier # files
---------------------------------------------------|------
GPL-2.0 WITH Linux-syscall-note 270
GPL-2.0+ WITH Linux-syscall-note 169
((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
LGPL-2.1+ WITH Linux-syscall-note 15
GPL-1.0+ WITH Linux-syscall-note 14
((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
LGPL-2.0+ WITH Linux-syscall-note 4
LGPL-2.1 WITH Linux-syscall-note 3
((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1
and that resulted in the third patch in this series.
- when the two scanners agreed on the detected license(s), that became
the concluded license(s).
- when there was disagreement between the two scanners (one detected a
license but the other didn't, or they both detected different
licenses) a manual inspection of the file occurred.
- In most cases a manual inspection of the information in the file
resulted in a clear resolution of the license that should apply (and
which scanner probably needed to revisit its heuristics).
- When it was not immediately clear, the license identifier was
confirmed with lawyers working with the Linux Foundation.
- If there was any question as to the appropriate license identifier,
the file was flagged for further research and to be revisited later
in time.
In total, over 70 hours of logged manual review was done on the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version early this week with:
- a full scancode scan run, collecting the matched texts, detected
license ids and scores
- reviewing anything where there was a license detected (about 500+
files) to ensure that the applied SPDX license was correct
- reviewing anything where there was no detection but the patch license
was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
SPDX license was correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 21:07:57 +07:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2007-03-16 20:13:18 +07:00
|
|
|
config PPC_PS3
|
2007-08-08 23:39:02 +07:00
|
|
|
bool "Sony PS3"
|
2015-09-07 06:58:00 +07:00
|
|
|
depends on PPC64 && PPC_BOOK3S && CPU_BIG_ENDIAN
|
2007-03-16 20:13:18 +07:00
|
|
|
select PPC_CELL
|
|
|
|
|
select USB_OHCI_LITTLE_ENDIAN
|
|
|
|
|
select USB_OHCI_BIG_ENDIAN_MMIO
|
|
|
|
|
select USB_EHCI_BIG_ENDIAN_MMIO
|
2018-11-16 02:05:32 +07:00
|
|
|
select HAVE_PCI
|
2007-03-16 20:13:18 +07:00
|
|
|
help
|
|
|
|
|
This option enables support for the Sony PS3 game console
|
2007-08-08 23:39:02 +07:00
|
|
|
and other platforms using the PS3 hypervisor. Enabling this
|
|
|
|
|
option will allow building otheros.bld, a kernel image suitable
|
|
|
|
|
for programming into flash memory, and vmlinux, a kernel image
|
|
|
|
|
suitable for loading via kexec.
|
2007-03-16 20:13:18 +07:00
|
|
|
|
2006-11-23 06:46:51 +07:00
|
|
|
menu "PS3 Platform Options"
|
|
|
|
|
depends on PPC_PS3
|
|
|
|
|
|
2007-03-01 11:13:38 +07:00
|
|
|
config PS3_ADVANCED
|
|
|
|
|
depends on PPC_PS3
|
|
|
|
|
bool "PS3 Advanced configuration options"
|
|
|
|
|
help
|
|
|
|
|
This gives you access to some advanced options for the PS3. The
|
|
|
|
|
defaults should be fine for most users, but these options may make
|
|
|
|
|
it possible to better control the kernel configuration if you know
|
|
|
|
|
what you are doing.
|
|
|
|
|
|
|
|
|
|
Note that the answer to this question won't directly affect the
|
|
|
|
|
kernel: saying N will just cause the configurator to skip all
|
|
|
|
|
the questions about these options.
|
|
|
|
|
|
|
|
|
|
Most users should say N to this question.
|
|
|
|
|
|
2006-11-23 06:46:51 +07:00
|
|
|
config PS3_HTAB_SIZE
|
|
|
|
|
depends on PPC_PS3
|
2007-03-01 11:13:38 +07:00
|
|
|
int "PS3 Platform pagetable size" if PS3_ADVANCED
|
2006-11-23 06:46:51 +07:00
|
|
|
range 18 20
|
|
|
|
|
default 20
|
|
|
|
|
help
|
|
|
|
|
This option is only for experts who may have the desire to fine
|
|
|
|
|
tune the pagetable size on their system. The value here is
|
|
|
|
|
expressed as the log2 of the page table size. Valid values are
|
|
|
|
|
18, 19, and 20, corresponding to 256KB, 512KB and 1MB respectively.
|
|
|
|
|
|
|
|
|
|
If unsure, choose the default (20) with the confidence that your
|
|
|
|
|
system will have optimal runtime performance.
|
|
|
|
|
|
|
|
|
|
config PS3_DYNAMIC_DMA
|
2012-10-03 01:16:42 +07:00
|
|
|
depends on PPC_PS3
|
2006-11-23 06:46:51 +07:00
|
|
|
bool "PS3 Platform dynamic DMA page table management"
|
|
|
|
|
help
|
|
|
|
|
This option will enable kernel support to take advantage of the
|
|
|
|
|
per device dynamic DMA page table management provided by the Cell
|
|
|
|
|
processor's IO Controller. This support incurs some runtime
|
|
|
|
|
overhead and also slightly increases kernel memory usage. The
|
|
|
|
|
current implementation should be considered experimental.
|
|
|
|
|
|
|
|
|
|
This support is mainly for Linux kernel development. If unsure,
|
|
|
|
|
say N.
|
|
|
|
|
|
2006-12-09 09:27:47 +07:00
|
|
|
config PS3_VUART
|
|
|
|
|
depends on PPC_PS3
|
2007-06-16 05:01:06 +07:00
|
|
|
tristate
|
2006-12-09 09:27:47 +07:00
|
|
|
|
2007-02-12 15:55:16 +07:00
|
|
|
config PS3_PS3AV
|
2007-06-16 05:01:06 +07:00
|
|
|
depends on PPC_PS3
|
2007-03-01 11:13:38 +07:00
|
|
|
tristate "PS3 AV settings driver" if PS3_ADVANCED
|
2007-06-16 05:01:06 +07:00
|
|
|
select PS3_VUART
|
2007-02-12 15:55:16 +07:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Include support for the PS3 AV Settings driver.
|
|
|
|
|
|
2012-04-01 05:23:10 +07:00
|
|
|
This support is required for PS3 graphics and sound. In
|
2007-02-12 15:55:16 +07:00
|
|
|
general, all users will say Y or M.
|
|
|
|
|
|
2007-02-08 03:20:01 +07:00
|
|
|
config PS3_SYS_MANAGER
|
2007-06-16 05:01:06 +07:00
|
|
|
depends on PPC_PS3
|
|
|
|
|
tristate "PS3 System Manager driver" if PS3_ADVANCED
|
|
|
|
|
select PS3_VUART
|
2007-12-10 11:17:43 +07:00
|
|
|
default y
|
2007-02-08 03:20:01 +07:00
|
|
|
help
|
|
|
|
|
Include support for the PS3 System Manager.
|
|
|
|
|
|
2012-04-01 05:23:10 +07:00
|
|
|
This support is required for PS3 system control. In
|
2007-06-16 05:01:06 +07:00
|
|
|
general, all users will say Y or M.
|
2007-02-08 03:20:01 +07:00
|
|
|
|
2012-04-01 08:03:30 +07:00
|
|
|
config PS3_REPOSITORY_WRITE
|
|
|
|
|
bool "PS3 Repository write support" if PS3_ADVANCED
|
|
|
|
|
depends on PPC_PS3
|
|
|
|
|
help
|
|
|
|
|
Enables support for writing to the PS3 System Repository.
|
|
|
|
|
|
|
|
|
|
This support is intended for bootloaders that need to store data
|
|
|
|
|
in the repository for later boot stages.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N here and reduce the size of the kernel by a
|
|
|
|
|
small amount.
|
|
|
|
|
|
2007-06-21 21:14:21 +07:00
|
|
|
config PS3_STORAGE
|
|
|
|
|
depends on PPC_PS3
|
|
|
|
|
tristate
|
|
|
|
|
|
2007-07-21 18:37:45 +07:00
|
|
|
config PS3_DISK
|
|
|
|
|
tristate "PS3 Disk Storage Driver"
|
|
|
|
|
depends on PPC_PS3 && BLOCK
|
|
|
|
|
select PS3_STORAGE
|
|
|
|
|
help
|
|
|
|
|
Include support for the PS3 Disk Storage.
|
|
|
|
|
|
|
|
|
|
This support is required to access the PS3 hard disk.
|
|
|
|
|
In general, all users will say Y or M.
|
|
|
|
|
|
2007-07-21 18:37:47 +07:00
|
|
|
config PS3_ROM
|
|
|
|
|
tristate "PS3 BD/DVD/CD-ROM Storage Driver"
|
|
|
|
|
depends on PPC_PS3 && SCSI
|
|
|
|
|
select PS3_STORAGE
|
|
|
|
|
help
|
|
|
|
|
Include support for the PS3 ROM Storage.
|
|
|
|
|
|
|
|
|
|
This support is required to access the PS3 BD/DVD/CD-ROM drive.
|
|
|
|
|
In general, all users will say Y or M.
|
|
|
|
|
Also make sure to say Y or M to "SCSI CDROM support" later.
|
|
|
|
|
|
2007-07-21 18:37:48 +07:00
|
|
|
config PS3_FLASH
|
|
|
|
|
tristate "PS3 FLASH ROM Storage Driver"
|
|
|
|
|
depends on PPC_PS3
|
|
|
|
|
select PS3_STORAGE
|
|
|
|
|
help
|
|
|
|
|
Include support for the PS3 FLASH ROM Storage.
|
|
|
|
|
|
|
|
|
|
This support is required to access the PS3 FLASH ROM, which
|
|
|
|
|
contains the boot loader and some boot options.
|
2012-04-01 05:23:10 +07:00
|
|
|
In general, PS3 OtherOS users will say Y or M.
|
2007-07-21 18:37:48 +07:00
|
|
|
|
|
|
|
|
As this driver needs a fixed buffer of 256 KiB of memory, it can
|
|
|
|
|
be disabled on the kernel command line using "ps3flash=off", to
|
|
|
|
|
not allocate this fixed buffer.
|
|
|
|
|
|
2009-03-06 09:54:09 +07:00
|
|
|
config PS3_VRAM
|
|
|
|
|
tristate "PS3 Video RAM Storage Driver"
|
|
|
|
|
depends on FB_PS3=y && BLOCK && m
|
|
|
|
|
help
|
|
|
|
|
This driver allows you to use excess PS3 video RAM as volatile
|
|
|
|
|
storage or system swap.
|
|
|
|
|
|
2008-01-19 03:32:46 +07:00
|
|
|
config PS3_LPM
|
|
|
|
|
tristate "PS3 Logical Performance Monitor support"
|
|
|
|
|
depends on PPC_PS3
|
|
|
|
|
help
|
|
|
|
|
Include support for the PS3 Logical Performance Monitor.
|
|
|
|
|
|
|
|
|
|
This support is required to use the logical performance monitor
|
|
|
|
|
of the PS3's LV1 hypervisor.
|
|
|
|
|
|
|
|
|
|
If you intend to use the advanced performance monitoring and
|
|
|
|
|
profiling support of the Cell processor with programs like
|
|
|
|
|
oprofile and perfmon2, then say Y or M, otherwise say N.
|
|
|
|
|
|
2011-08-31 13:32:26 +07:00
|
|
|
config PS3GELIC_UDBG
|
|
|
|
|
bool "PS3 udbg output via UDP broadcasts on Ethernet"
|
|
|
|
|
depends on PPC_PS3
|
|
|
|
|
help
|
|
|
|
|
Enables udbg early debugging output by sending broadcast UDP
|
|
|
|
|
via the Ethernet port (UDP port number 18194).
|
|
|
|
|
|
|
|
|
|
This driver uses a trivial implementation and is independent
|
2012-04-01 05:23:10 +07:00
|
|
|
from the main PS3 gelic network driver.
|
2011-08-31 13:32:26 +07:00
|
|
|
|
|
|
|
|
If in doubt, say N here.
|
|
|
|
|
|
2006-11-23 06:46:51 +07:00
|
|
|
endmenu
|