forked from Minki/linux
b24413180f
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>
394 lines
8.8 KiB
Plaintext
394 lines
8.8 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0
|
|
config PPC_47x
|
|
bool "Support for 47x variant"
|
|
depends on 44x
|
|
default n
|
|
select MPIC
|
|
help
|
|
This option enables support for the 47x family of processors and is
|
|
not currently compatible with other 44x or 46x varients
|
|
|
|
config BAMBOO
|
|
bool "Bamboo"
|
|
depends on 44x
|
|
default n
|
|
select PPC44x_SIMPLE
|
|
select 440EP
|
|
select PCI
|
|
help
|
|
This option enables support for the IBM PPC440EP evaluation board.
|
|
|
|
config BLUESTONE
|
|
bool "Bluestone"
|
|
depends on 44x
|
|
default n
|
|
select PPC44x_SIMPLE
|
|
select APM821xx
|
|
select PCI_MSI
|
|
select PPC4xx_MSI
|
|
select PPC4xx_PCI_EXPRESS
|
|
select IBM_EMAC_RGMII if IBM_EMAC
|
|
help
|
|
This option enables support for the APM APM821xx Evaluation board.
|
|
|
|
config EBONY
|
|
bool "Ebony"
|
|
depends on 44x
|
|
default y
|
|
select 440GP
|
|
select PCI
|
|
select OF_RTC
|
|
help
|
|
This option enables support for the IBM PPC440GP evaluation board.
|
|
|
|
config SAM440EP
|
|
bool "Sam440ep"
|
|
depends on 44x
|
|
default n
|
|
select 440EP
|
|
select PCI
|
|
help
|
|
This option enables support for the ACube Sam440ep board.
|
|
|
|
config SEQUOIA
|
|
bool "Sequoia"
|
|
depends on 44x
|
|
default n
|
|
select PPC44x_SIMPLE
|
|
select 440EPX
|
|
help
|
|
This option enables support for the AMCC PPC440EPX evaluation board.
|
|
|
|
config TAISHAN
|
|
bool "Taishan"
|
|
depends on 44x
|
|
default n
|
|
select PPC44x_SIMPLE
|
|
select 440GX
|
|
select PCI
|
|
help
|
|
This option enables support for the AMCC PPC440GX "Taishan"
|
|
evaluation board.
|
|
|
|
config KATMAI
|
|
bool "Katmai"
|
|
depends on 44x
|
|
default n
|
|
select PPC44x_SIMPLE
|
|
select 440SPe
|
|
select PCI
|
|
select PPC4xx_PCI_EXPRESS
|
|
select PCI_MSI
|
|
select PPC4xx_MSI
|
|
help
|
|
This option enables support for the AMCC PPC440SPe evaluation board.
|
|
|
|
config RAINIER
|
|
bool "Rainier"
|
|
depends on 44x
|
|
default n
|
|
select PPC44x_SIMPLE
|
|
select 440GRX
|
|
select PCI
|
|
help
|
|
This option enables support for the AMCC PPC440GRX evaluation board.
|
|
|
|
config WARP
|
|
bool "PIKA Warp"
|
|
depends on 44x
|
|
default n
|
|
select 440EP
|
|
help
|
|
This option enables support for the PIKA Warp(tm) Appliance. The Warp
|
|
is a small computer replacement with up to 9 ports of FXO/FXS plus VOIP
|
|
stations and trunks.
|
|
|
|
See http://www.pikatechnologies.com/ and follow the "PIKA for Computer
|
|
Telephony Developers" link for more information.
|
|
|
|
config ARCHES
|
|
bool "Arches"
|
|
depends on 44x
|
|
default n
|
|
select PPC44x_SIMPLE
|
|
select 460EX # Odd since it uses 460GT but the effects are the same
|
|
select PCI
|
|
select PPC4xx_PCI_EXPRESS
|
|
help
|
|
This option enables support for the AMCC Dual PPC460GT evaluation board.
|
|
|
|
config CANYONLANDS
|
|
bool "Canyonlands"
|
|
depends on 44x
|
|
default n
|
|
select 460EX
|
|
select PCI
|
|
select PPC4xx_PCI_EXPRESS
|
|
select PCI_MSI
|
|
select PPC4xx_MSI
|
|
select IBM_EMAC_RGMII if IBM_EMAC
|
|
select IBM_EMAC_ZMII if IBM_EMAC
|
|
help
|
|
This option enables support for the AMCC PPC460EX evaluation board.
|
|
|
|
config GLACIER
|
|
bool "Glacier"
|
|
depends on 44x
|
|
default n
|
|
select PPC44x_SIMPLE
|
|
select 460EX # Odd since it uses 460GT but the effects are the same
|
|
select PCI
|
|
select PPC4xx_PCI_EXPRESS
|
|
select IBM_EMAC_RGMII if IBM_EMAC
|
|
select IBM_EMAC_ZMII if IBM_EMAC
|
|
help
|
|
This option enables support for the AMCC PPC460GT evaluation board.
|
|
|
|
config REDWOOD
|
|
bool "Redwood"
|
|
depends on 44x
|
|
default n
|
|
select PPC44x_SIMPLE
|
|
select 460SX
|
|
select PCI
|
|
select PPC4xx_PCI_EXPRESS
|
|
select PCI_MSI
|
|
select PPC4xx_MSI
|
|
help
|
|
This option enables support for the AMCC PPC460SX Redwood board.
|
|
|
|
config EIGER
|
|
bool "Eiger"
|
|
depends on 44x
|
|
default n
|
|
select PPC44x_SIMPLE
|
|
select 460SX
|
|
select PCI
|
|
select PPC4xx_PCI_EXPRESS
|
|
select IBM_EMAC_RGMII if IBM_EMAC
|
|
help
|
|
This option enables support for the AMCC PPC460SX evaluation board.
|
|
|
|
config YOSEMITE
|
|
bool "Yosemite"
|
|
depends on 44x
|
|
default n
|
|
select PPC44x_SIMPLE
|
|
select 440EP
|
|
select PCI
|
|
help
|
|
This option enables support for the AMCC PPC440EP evaluation board.
|
|
|
|
config ISS4xx
|
|
bool "ISS 4xx Simulator"
|
|
depends on (44x || 40x)
|
|
default n
|
|
select 405GP if 40x
|
|
select 440GP if 44x && !PPC_47x
|
|
select PPC_FPU
|
|
select OF_RTC
|
|
help
|
|
This option enables support for the IBM ISS simulation environment
|
|
|
|
config CURRITUCK
|
|
bool "IBM Currituck (476fpe) Support"
|
|
depends on PPC_47x
|
|
default n
|
|
select SWIOTLB
|
|
select 476FPE
|
|
select PPC4xx_PCI_EXPRESS
|
|
help
|
|
This option enables support for the IBM Currituck (476fpe) evaluation board
|
|
|
|
config FSP2
|
|
bool "IBM FSP2 (476fpe) Support"
|
|
depends on PPC_47x
|
|
default n
|
|
select 476FPE
|
|
select IBM_EMAC_EMAC4 if IBM_EMAC
|
|
select IBM_EMAC_RGMII if IBM_EMAC
|
|
select COMMON_CLK
|
|
select DEFAULT_UIMAGE
|
|
help
|
|
This option enables support for the IBM FSP2 (476fpe) board
|
|
|
|
config AKEBONO
|
|
bool "IBM Akebono (476gtr) Support"
|
|
depends on PPC_47x
|
|
default n
|
|
select SWIOTLB
|
|
select 476FPE
|
|
select PPC4xx_PCI_EXPRESS
|
|
select PCI_MSI
|
|
select PPC4xx_HSTA_MSI
|
|
select I2C
|
|
select I2C_IBM_IIC
|
|
select NETDEVICES
|
|
select ETHERNET
|
|
select NET_VENDOR_IBM
|
|
select IBM_EMAC_EMAC4 if IBM_EMAC
|
|
select USB if USB_SUPPORT
|
|
select USB_OHCI_HCD_PLATFORM if USB_OHCI_HCD
|
|
select USB_EHCI_HCD_PLATFORM if USB_EHCI_HCD
|
|
select MMC_SDHCI
|
|
select MMC_SDHCI_PLTFM
|
|
select ATA
|
|
select SATA_AHCI_PLATFORM
|
|
help
|
|
This option enables support for the IBM Akebono (476gtr) evaluation board
|
|
|
|
|
|
config ICON
|
|
bool "Icon"
|
|
depends on 44x
|
|
default n
|
|
select PPC44x_SIMPLE
|
|
select 440SPe
|
|
select PCI
|
|
select PPC4xx_PCI_EXPRESS
|
|
help
|
|
This option enables support for the AMCC PPC440SPe evaluation board.
|
|
|
|
config XILINX_VIRTEX440_GENERIC_BOARD
|
|
bool "Generic Xilinx Virtex 5 FXT board support"
|
|
depends on 44x
|
|
default n
|
|
select XILINX_VIRTEX_5_FXT
|
|
select XILINX_INTC
|
|
help
|
|
This option enables generic support for Xilinx Virtex based boards
|
|
that use a 440 based processor in the Virtex 5 FXT FPGA architecture.
|
|
|
|
The generic virtex board support matches any device tree which
|
|
specifies 'xlnx,virtex440' in its compatible field. This includes
|
|
the Xilinx ML5xx reference designs using the powerpc core.
|
|
|
|
Most Virtex 5 designs should use this unless it needs to do some
|
|
special configuration at board probe time.
|
|
|
|
config XILINX_ML510
|
|
bool "Xilinx ML510 extra support"
|
|
depends on XILINX_VIRTEX440_GENERIC_BOARD
|
|
select PPC_PCI_CHOICE
|
|
select XILINX_PCI if PCI
|
|
select PPC_INDIRECT_PCI if PCI
|
|
select PPC_I8259 if PCI
|
|
help
|
|
This option enables extra support for features on the Xilinx ML510
|
|
board. The ML510 has a PCI bus with ALI south bridge.
|
|
|
|
config PPC44x_SIMPLE
|
|
bool "Simple PowerPC 44x board support"
|
|
depends on 44x
|
|
default n
|
|
help
|
|
This option enables the simple PowerPC 44x platform support.
|
|
|
|
config PPC4xx_GPIO
|
|
bool "PPC4xx GPIO support"
|
|
depends on 44x
|
|
select GPIOLIB
|
|
help
|
|
Enable gpiolib support for ppc440 based boards
|
|
|
|
config PPC4xx_OCM
|
|
bool "PPC4xx On Chip Memory (OCM) support"
|
|
depends on 4xx
|
|
select PPC_LIB_RHEAP
|
|
help
|
|
Enable OCM support for PowerPC 4xx platforms with on chip memory,
|
|
OCM provides the fast place for memory access to improve performance.
|
|
|
|
# 44x specific CPU modules, selected based on the board above.
|
|
config 440EP
|
|
bool
|
|
select PPC_FPU
|
|
select IBM440EP_ERR42
|
|
select IBM_EMAC_ZMII if IBM_EMAC
|
|
|
|
config 440EPX
|
|
bool
|
|
select PPC_FPU
|
|
select IBM_EMAC_EMAC4 if IBM_EMAC
|
|
select IBM_EMAC_RGMII if IBM_EMAC
|
|
select IBM_EMAC_ZMII if IBM_EMAC
|
|
select USB_EHCI_BIG_ENDIAN_MMIO
|
|
select USB_EHCI_BIG_ENDIAN_DESC
|
|
|
|
config 440GRX
|
|
bool
|
|
select IBM_EMAC_EMAC4 if IBM_EMAC
|
|
select IBM_EMAC_RGMII if IBM_EMAC
|
|
select IBM_EMAC_ZMII if IBM_EMAC
|
|
|
|
config 440GP
|
|
bool
|
|
select IBM_EMAC_ZMII if IBM_EMAC
|
|
|
|
config 440GX
|
|
bool
|
|
select IBM_EMAC_EMAC4 if IBM_EMAC
|
|
select IBM_EMAC_RGMII if IBM_EMAC
|
|
select IBM_EMAC_ZMII if IBM_EMAC #test only
|
|
select IBM_EMAC_TAH if IBM_EMAC #test only
|
|
|
|
config 440SP
|
|
bool
|
|
|
|
config 440SPe
|
|
bool
|
|
select IBM_EMAC_EMAC4 if IBM_EMAC
|
|
|
|
config 460EX
|
|
bool
|
|
select PPC_FPU
|
|
select IBM_EMAC_EMAC4 if IBM_EMAC
|
|
select IBM_EMAC_TAH if IBM_EMAC
|
|
|
|
config 460SX
|
|
bool
|
|
select PPC_FPU
|
|
select IBM_EMAC_EMAC4 if IBM_EMAC
|
|
select IBM_EMAC_RGMII if IBM_EMAC
|
|
select IBM_EMAC_ZMII if IBM_EMAC
|
|
select IBM_EMAC_TAH if IBM_EMAC
|
|
|
|
config 476FPE
|
|
bool
|
|
select PPC_FPU
|
|
|
|
config APM821xx
|
|
bool
|
|
select PPC_FPU
|
|
select IBM_EMAC_EMAC4 if IBM_EMAC
|
|
select IBM_EMAC_TAH if IBM_EMAC
|
|
|
|
config 476FPE_ERR46
|
|
depends on 476FPE
|
|
bool "Enable linker work around for PPC476FPE errata #46"
|
|
help
|
|
This option enables a work around for an icache bug on 476
|
|
that can cause execution of stale instructions when falling
|
|
through pages (IBM errata #46). It requires a recent version
|
|
of binutils which supports the --ppc476-workaround option.
|
|
|
|
The work around enables the appropriate linker options and
|
|
ensures that all module output sections are aligned to 4K
|
|
page boundaries. The work around is only required when
|
|
building modules.
|
|
|
|
# 44x errata/workaround config symbols, selected by the CPU models above
|
|
config IBM440EP_ERR42
|
|
bool
|
|
|
|
# Xilinx specific config options.
|
|
config XILINX_VIRTEX
|
|
bool
|
|
select DEFAULT_UIMAGE
|
|
|
|
# Xilinx Virtex 5 FXT FPGA architecture, selected by a Xilinx board above
|
|
config XILINX_VIRTEX_5_FXT
|
|
bool
|
|
select XILINX_VIRTEX
|
|
|