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 08:07:57 -06:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2007-06-12 10:30:17 -06:00
|
|
|
config PPC64
|
|
|
|
|
bool "64-bit kernel"
|
2015-02-05 12:36:04 -07:00
|
|
|
select ZLIB_DEFLATE
|
2007-06-12 10:30:17 -06:00
|
|
|
help
|
|
|
|
|
This option selects whether a 32-bit or a 64-bit kernel
|
|
|
|
|
will be built.
|
|
|
|
|
|
|
|
|
|
menu "Processor support"
|
|
|
|
|
choice
|
|
|
|
|
prompt "Processor Type"
|
|
|
|
|
depends on PPC32
|
|
|
|
|
help
|
2007-06-17 17:06:52 -06:00
|
|
|
There are five families of 32 bit PowerPC chips supported.
|
|
|
|
|
The most common ones are the desktop and server CPUs (601, 603,
|
|
|
|
|
604, 740, 750, 74xx) CPUs from Freescale and IBM, with their
|
2008-01-28 10:28:53 -07:00
|
|
|
embedded 512x/52xx/82xx/83xx/86xx counterparts.
|
2015-03-18 10:29:13 -06:00
|
|
|
The other embedded parts, namely 4xx, 8xx, e200 (55xx) and e500
|
2007-06-17 17:06:52 -06:00
|
|
|
(85xx) each form a family of their own that is not compatible
|
|
|
|
|
with the others.
|
|
|
|
|
|
|
|
|
|
If unsure, select 52xx/6xx/7xx/74xx/82xx/83xx/86xx.
|
|
|
|
|
|
2009-06-14 08:45:50 -06:00
|
|
|
config PPC_BOOK3S_32
|
2008-01-28 10:28:53 -07:00
|
|
|
bool "512x/52xx/6xx/7xx/74xx/82xx/83xx/86xx"
|
2007-06-12 10:30:17 -06:00
|
|
|
select PPC_FPU
|
|
|
|
|
|
|
|
|
|
config PPC_85xx
|
|
|
|
|
bool "Freescale 85xx"
|
|
|
|
|
select E500
|
|
|
|
|
|
|
|
|
|
config PPC_8xx
|
|
|
|
|
bool "Freescale 8xx"
|
|
|
|
|
select FSL_SOC
|
2016-12-07 00:47:28 -07:00
|
|
|
select SYS_SUPPORTS_HUGETLBFS
|
2007-06-12 10:30:17 -06:00
|
|
|
|
|
|
|
|
config 40x
|
|
|
|
|
bool "AMCC 40x"
|
|
|
|
|
select PPC_DCR_NATIVE
|
2007-12-20 21:39:26 -07:00
|
|
|
select PPC_UDBG_16550
|
2008-03-27 08:43:31 -06:00
|
|
|
select 4xx_SOC
|
2018-11-15 12:05:32 -07:00
|
|
|
select HAVE_PCI
|
2007-06-12 10:30:17 -06:00
|
|
|
|
|
|
|
|
config 44x
|
2010-03-05 03:43:12 -07:00
|
|
|
bool "AMCC 44x, 46x or 47x"
|
2007-06-12 10:30:17 -06:00
|
|
|
select PPC_DCR_NATIVE
|
2007-10-18 06:55:13 -06:00
|
|
|
select PPC_UDBG_16550
|
2008-03-27 08:43:31 -06:00
|
|
|
select 4xx_SOC
|
2018-11-15 12:05:32 -07:00
|
|
|
select HAVE_PCI
|
2008-09-24 10:01:24 -06:00
|
|
|
select PHYS_64BIT
|
2007-06-12 10:30:17 -06:00
|
|
|
|
|
|
|
|
config E200
|
|
|
|
|
bool "Freescale e200"
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2009-07-23 17:15:59 -06:00
|
|
|
choice
|
|
|
|
|
prompt "Processor Type"
|
2009-06-02 15:17:37 -06:00
|
|
|
depends on PPC64
|
2009-07-23 17:15:59 -06:00
|
|
|
help
|
|
|
|
|
There are two families of 64 bit PowerPC chips supported.
|
|
|
|
|
The most common ones are the desktop and server CPUs
|
2018-02-20 12:08:29 -07:00
|
|
|
(POWER5, 970, POWER5+, POWER6, POWER7, POWER8, POWER9 ...)
|
2009-07-23 17:15:59 -06:00
|
|
|
|
|
|
|
|
The other are the "embedded" processors compliant with the
|
|
|
|
|
"Book 3E" variant of the architecture
|
|
|
|
|
|
|
|
|
|
config PPC_BOOK3S_64
|
|
|
|
|
bool "Server processors"
|
2009-06-02 15:17:37 -06:00
|
|
|
select PPC_FPU
|
2011-07-12 23:00:41 -06:00
|
|
|
select PPC_HAVE_PMU_SUPPORT
|
2011-06-28 03:54:48 -06:00
|
|
|
select SYS_SUPPORTS_HUGETLBFS
|
2016-04-29 07:26:31 -06:00
|
|
|
select HAVE_ARCH_TRANSPARENT_HUGEPAGE
|
2018-09-20 12:09:47 -06:00
|
|
|
select ARCH_ENABLE_THP_MIGRATION if TRANSPARENT_HUGEPAGE
|
2013-11-18 02:28:13 -07:00
|
|
|
select ARCH_SUPPORTS_NUMA_BALANCING
|
2014-04-07 16:39:08 -06:00
|
|
|
select IRQ_WORK
|
2009-06-02 15:17:37 -06:00
|
|
|
|
2009-07-23 17:15:59 -06:00
|
|
|
config PPC_BOOK3E_64
|
|
|
|
|
bool "Embedded processors"
|
|
|
|
|
select PPC_FPU # Make it a choice ?
|
2011-05-10 13:29:42 -06:00
|
|
|
select PPC_SMP_MUXED_IPI
|
2012-11-14 11:49:49 -07:00
|
|
|
select PPC_DOORBELL
|
2009-07-23 17:15:59 -06:00
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2012-04-17 12:45:28 -06:00
|
|
|
choice
|
|
|
|
|
prompt "CPU selection"
|
|
|
|
|
default GENERIC_CPU
|
|
|
|
|
help
|
|
|
|
|
This will create a kernel which is optimised for a particular CPU.
|
|
|
|
|
The resulting kernel may not run on other CPUs, so use this with care.
|
|
|
|
|
|
|
|
|
|
If unsure, select Generic.
|
|
|
|
|
|
|
|
|
|
config GENERIC_CPU
|
2018-02-20 12:08:30 -07:00
|
|
|
bool "Generic (POWER4 and above)"
|
2018-06-07 04:10:20 -06:00
|
|
|
depends on PPC64 && !CPU_LITTLE_ENDIAN
|
2012-04-17 12:45:28 -06:00
|
|
|
|
2018-02-20 12:08:30 -07:00
|
|
|
config GENERIC_CPU
|
|
|
|
|
bool "Generic (POWER8 and above)"
|
2018-06-07 04:10:20 -06:00
|
|
|
depends on PPC64 && CPU_LITTLE_ENDIAN
|
2018-02-20 12:08:30 -07:00
|
|
|
select ARCH_HAS_FAST_MULTIPLIER
|
|
|
|
|
|
2018-06-07 04:10:20 -06:00
|
|
|
config GENERIC_CPU
|
|
|
|
|
bool "Generic 32 bits powerpc"
|
|
|
|
|
depends on PPC32 && !PPC_8xx
|
|
|
|
|
|
2012-04-17 12:45:28 -06:00
|
|
|
config CELL_CPU
|
|
|
|
|
bool "Cell Broadband Engine"
|
2013-10-21 18:05:25 -06:00
|
|
|
depends on PPC_BOOK3S_64 && !CPU_LITTLE_ENDIAN
|
2012-04-17 12:45:28 -06:00
|
|
|
|
|
|
|
|
config POWER5_CPU
|
|
|
|
|
bool "POWER5"
|
2013-10-21 18:05:25 -06:00
|
|
|
depends on PPC_BOOK3S_64 && !CPU_LITTLE_ENDIAN
|
2012-04-17 12:45:28 -06:00
|
|
|
|
|
|
|
|
config POWER6_CPU
|
|
|
|
|
bool "POWER6"
|
2013-10-21 18:05:25 -06:00
|
|
|
depends on PPC_BOOK3S_64 && !CPU_LITTLE_ENDIAN
|
2012-04-17 12:45:28 -06:00
|
|
|
|
|
|
|
|
config POWER7_CPU
|
|
|
|
|
bool "POWER7"
|
2013-08-20 18:55:36 -06:00
|
|
|
depends on PPC_BOOK3S_64
|
2014-09-15 18:49:14 -06:00
|
|
|
select ARCH_HAS_FAST_MULTIPLIER
|
2013-08-20 18:55:36 -06:00
|
|
|
|
2014-09-15 18:47:49 -06:00
|
|
|
config POWER8_CPU
|
|
|
|
|
bool "POWER8"
|
|
|
|
|
depends on PPC_BOOK3S_64
|
2014-09-15 18:49:14 -06:00
|
|
|
select ARCH_HAS_FAST_MULTIPLIER
|
2013-08-20 18:55:36 -06:00
|
|
|
|
2018-02-20 12:08:32 -07:00
|
|
|
config POWER9_CPU
|
|
|
|
|
bool "POWER9"
|
|
|
|
|
depends on PPC_BOOK3S_64
|
|
|
|
|
select ARCH_HAS_FAST_MULTIPLIER
|
|
|
|
|
|
2013-08-20 18:55:36 -06:00
|
|
|
config E5500_CPU
|
|
|
|
|
bool "Freescale e5500"
|
|
|
|
|
depends on E500
|
|
|
|
|
|
|
|
|
|
config E6500_CPU
|
|
|
|
|
bool "Freescale e6500"
|
|
|
|
|
depends on E500
|
2012-04-17 12:45:28 -06:00
|
|
|
|
2018-06-07 04:10:20 -06:00
|
|
|
config 860_CPU
|
|
|
|
|
bool "8xx family"
|
|
|
|
|
depends on PPC_8xx
|
|
|
|
|
|
2018-06-07 04:10:22 -06:00
|
|
|
config E300C2_CPU
|
|
|
|
|
bool "e300c2 (832x)"
|
|
|
|
|
depends on PPC_BOOK3S_32
|
|
|
|
|
|
|
|
|
|
config E300C3_CPU
|
|
|
|
|
bool "e300c3 (831x)"
|
|
|
|
|
depends on PPC_BOOK3S_32
|
|
|
|
|
|
2012-04-17 12:45:28 -06:00
|
|
|
endchoice
|
|
|
|
|
|
2018-06-07 04:10:18 -06:00
|
|
|
config TARGET_CPU_BOOL
|
|
|
|
|
bool
|
|
|
|
|
default !GENERIC_CPU
|
|
|
|
|
|
|
|
|
|
config TARGET_CPU
|
|
|
|
|
string
|
|
|
|
|
depends on TARGET_CPU_BOOL
|
|
|
|
|
default "cell" if CELL_CPU
|
|
|
|
|
default "power5" if POWER5_CPU
|
|
|
|
|
default "power6" if POWER6_CPU
|
|
|
|
|
default "power7" if POWER7_CPU
|
|
|
|
|
default "power8" if POWER8_CPU
|
|
|
|
|
default "power9" if POWER9_CPU
|
2018-06-07 04:10:20 -06:00
|
|
|
default "860" if 860_CPU
|
2018-06-07 04:10:22 -06:00
|
|
|
default "e300c2" if E300C2_CPU
|
|
|
|
|
default "e300c3" if E300C3_CPU
|
2018-06-07 04:10:18 -06:00
|
|
|
|
2009-06-14 08:45:50 -06:00
|
|
|
config PPC_BOOK3S
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on PPC_BOOK3S_32 || PPC_BOOK3S_64
|
2009-03-10 11:53:27 -06:00
|
|
|
|
2009-07-23 17:15:59 -06:00
|
|
|
config PPC_BOOK3E
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on PPC_BOOK3E_64
|
|
|
|
|
|
2009-06-02 15:17:37 -06:00
|
|
|
config 6xx
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on PPC32 && PPC_BOOK3S
|
perf_counter: powerpc: Add processor back-end for MPC7450 family
This adds support for the performance monitor hardware on the
MPC7450 family of processors (7450, 7451, 7455, 7447/7457, 7447A,
7448), used in the later Apple G4 powermacs/powerbooks and other
machines. These machines have 6 hardware counters with a unique
set of events which can be counted on each counter, with some
events being available on multiple counters.
Raw event codes for these processors are (PMC << 8) + PMCSEL.
If PMC is non-zero then the event is that selected by the given
PMCSEL value for that PMC (hardware counter). If PMC is zero
then the event selected is one of the low-numbered ones that are
common to several PMCs. In this case PMCSEL must be <= 22 and
the event is what that PMCSEL value would select on PMC1 (but
it may be placed any other PMC that has the same event for that
PMCSEL value).
For events that count cycles or occurrences that exceed a threshold,
the threshold requested can be specified in the 0x3f000 bits of the
raw event codes. If the event uses the threshold multiplier bit
and that bit should be set, that is indicated with the 0x40000 bit
of the raw event code.
This fills in some of the generic cache events. Unfortunately there
are quite a few blank spaces in the table, partly because these
processors tend to count cache hits rather than cache accesses.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linuxppc-dev@ozlabs.org
Cc: benh@kernel.crashing.org
LKML-Reference: <19000.55631.802122.696927@cargo.ozlabs.ibm.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-06-17 05:53:51 -06:00
|
|
|
select PPC_HAVE_PMU_SUPPORT
|
2009-06-02 15:17:37 -06:00
|
|
|
|
2007-06-12 10:30:17 -06:00
|
|
|
config E500
|
2008-02-04 17:27:55 -07:00
|
|
|
select FSL_EMB_PERFMON
|
2010-10-08 07:32:11 -06:00
|
|
|
select PPC_FSL_BOOK3E
|
2007-06-12 10:30:17 -06:00
|
|
|
bool
|
|
|
|
|
|
2008-06-16 08:41:32 -06:00
|
|
|
config PPC_E500MC
|
|
|
|
|
bool "e500mc Support"
|
|
|
|
|
select PPC_FPU
|
2013-04-09 02:46:26 -06:00
|
|
|
select COMMON_CLK
|
2008-06-16 08:41:32 -06:00
|
|
|
depends on E500
|
2012-07-10 18:26:48 -06:00
|
|
|
help
|
|
|
|
|
This must be enabled for running on e500mc (and derivatives
|
|
|
|
|
such as e5500/e6500), and must be disabled for running on
|
|
|
|
|
e500v1 or e500v2.
|
2008-06-16 08:41:32 -06:00
|
|
|
|
2007-06-12 10:30:17 -06:00
|
|
|
config PPC_FPU
|
|
|
|
|
bool
|
|
|
|
|
default y if PPC64
|
|
|
|
|
|
2009-10-16 17:31:48 -06:00
|
|
|
config FSL_EMB_PERFMON
|
|
|
|
|
bool "Freescale Embedded Perfmon"
|
|
|
|
|
depends on E500 || PPC_83xx
|
|
|
|
|
help
|
|
|
|
|
This is the Performance Monitor support found on the e500 core
|
|
|
|
|
and some e300 cores (c3 and c4). Select this only if your
|
|
|
|
|
core supports the Embedded Performance Monitor APU
|
|
|
|
|
|
2010-02-25 17:09:45 -07:00
|
|
|
config FSL_EMB_PERF_EVENT
|
|
|
|
|
bool
|
|
|
|
|
depends on FSL_EMB_PERFMON && PERF_EVENTS && !PPC_PERF_CTRS
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config FSL_EMB_PERF_EVENT_E500
|
|
|
|
|
bool
|
|
|
|
|
depends on FSL_EMB_PERF_EVENT && E500
|
|
|
|
|
default y
|
|
|
|
|
|
2007-06-12 10:30:17 -06:00
|
|
|
config 4xx
|
|
|
|
|
bool
|
|
|
|
|
depends on 40x || 44x
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config BOOKE
|
|
|
|
|
bool
|
2009-07-23 17:15:59 -06:00
|
|
|
depends on E200 || E500 || 44x || PPC_BOOK3E
|
2007-06-12 10:30:17 -06:00
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
config FSL_BOOKE
|
|
|
|
|
bool
|
2010-10-08 07:32:11 -06:00
|
|
|
depends on (E200 || E500) && PPC32
|
2007-06-12 10:30:17 -06:00
|
|
|
default y
|
|
|
|
|
|
2010-10-08 07:32:11 -06:00
|
|
|
# this is for common code between PPC32 & PPC64 FSL BOOKE
|
|
|
|
|
config PPC_FSL_BOOK3E
|
|
|
|
|
bool
|
|
|
|
|
select FSL_EMB_PERFMON
|
2011-05-10 13:29:42 -06:00
|
|
|
select PPC_SMP_MUXED_IPI
|
2011-10-10 04:50:44 -06:00
|
|
|
select SYS_SUPPORTS_HUGETLBFS if PHYS_64BIT || PPC64
|
2012-11-14 11:49:49 -07:00
|
|
|
select PPC_DOORBELL
|
2010-10-08 07:32:11 -06:00
|
|
|
default y if FSL_BOOKE
|
2008-02-04 17:27:55 -07:00
|
|
|
|
2007-06-12 10:30:17 -06:00
|
|
|
config PTE_64BIT
|
|
|
|
|
bool
|
2008-09-24 10:01:24 -06:00
|
|
|
depends on 44x || E500 || PPC_86xx
|
|
|
|
|
default y if PHYS_64BIT
|
2007-06-12 10:30:17 -06:00
|
|
|
|
|
|
|
|
config PHYS_64BIT
|
2008-09-24 10:01:24 -06:00
|
|
|
bool 'Large physical address support' if E500 || PPC_86xx
|
|
|
|
|
depends on (44x || E500 || PPC_86xx) && !PPC_83xx && !PPC_82xx
|
2018-04-03 08:24:20 -06:00
|
|
|
select PHYS_ADDR_T_64BIT
|
2007-06-12 10:30:17 -06:00
|
|
|
---help---
|
|
|
|
|
This option enables kernel support for larger than 32-bit physical
|
2008-09-24 10:01:24 -06:00
|
|
|
addresses. This feature may not be available on all cores.
|
|
|
|
|
|
|
|
|
|
If you have more than 3.5GB of RAM or so, you also need to enable
|
|
|
|
|
SWIOTLB under Kernel Options for this to work. The actual number
|
|
|
|
|
is platform-dependent.
|
2007-06-12 10:30:17 -06:00
|
|
|
|
|
|
|
|
If in doubt, say N here.
|
|
|
|
|
|
|
|
|
|
config ALTIVEC
|
|
|
|
|
bool "AltiVec Support"
|
2014-07-09 20:29:25 -06:00
|
|
|
depends on 6xx || PPC_BOOK3S_64 || (PPC_E500MC && PPC64)
|
2007-06-12 10:30:17 -06:00
|
|
|
---help---
|
|
|
|
|
This option enables kernel support for the Altivec extensions to the
|
|
|
|
|
PowerPC processor. The kernel currently supports saving and restoring
|
|
|
|
|
altivec registers, and turning on the 'altivec enable' bit so user
|
|
|
|
|
processes can execute altivec instructions.
|
|
|
|
|
|
|
|
|
|
This option is only usefully if you have a processor that supports
|
|
|
|
|
altivec (G4, otherwise known as 74xx series), but does not have
|
|
|
|
|
any affect on a non-altivec cpu (it does, however add code to the
|
|
|
|
|
kernel).
|
|
|
|
|
|
|
|
|
|
If in doubt, say Y here.
|
|
|
|
|
|
2008-06-24 22:07:18 -06:00
|
|
|
config VSX
|
|
|
|
|
bool "VSX Support"
|
2014-07-09 20:29:25 -06:00
|
|
|
depends on PPC_BOOK3S_64 && ALTIVEC && PPC_FPU
|
2008-06-24 22:07:18 -06:00
|
|
|
---help---
|
|
|
|
|
|
|
|
|
|
This option enables kernel support for the Vector Scaler extensions
|
|
|
|
|
to the PowerPC processor. The kernel currently supports saving and
|
|
|
|
|
restoring VSX registers, and turning on the 'VSX enable' bit so user
|
|
|
|
|
processes can execute VSX instructions.
|
|
|
|
|
|
|
|
|
|
This option is only useful if you have a processor that supports
|
|
|
|
|
VSX (P7 and above), but does not have any affect on a non-VSX
|
|
|
|
|
CPUs (it does, however add code to the kernel).
|
|
|
|
|
|
|
|
|
|
If in doubt, say Y here.
|
|
|
|
|
|
2014-08-20 07:09:03 -06:00
|
|
|
config SPE_POSSIBLE
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on E200 || (E500 && !PPC_E500MC)
|
|
|
|
|
|
2007-06-12 10:30:17 -06:00
|
|
|
config SPE
|
|
|
|
|
bool "SPE Support"
|
2014-08-20 07:09:03 -06:00
|
|
|
depends on SPE_POSSIBLE
|
2007-06-12 10:30:17 -06:00
|
|
|
default y
|
|
|
|
|
---help---
|
|
|
|
|
This option enables kernel support for the Signal Processing
|
|
|
|
|
Extensions (SPE) to the PowerPC processor. The kernel currently
|
|
|
|
|
supports saving and restoring SPE registers, and turning on the
|
|
|
|
|
'spe enable' bit so user processes can execute SPE instructions.
|
|
|
|
|
|
|
|
|
|
This option is only useful if you have a processor that supports
|
|
|
|
|
SPE (e500, otherwise known as 85xx series), but does not have any
|
|
|
|
|
effect on a non-spe cpu (it does, however add code to the kernel).
|
|
|
|
|
|
|
|
|
|
If in doubt, say Y here.
|
|
|
|
|
|
|
|
|
|
config PPC_STD_MMU
|
2009-06-02 15:17:37 -06:00
|
|
|
def_bool y
|
|
|
|
|
depends on PPC_BOOK3S
|
2007-06-12 10:30:17 -06:00
|
|
|
|
|
|
|
|
config PPC_STD_MMU_32
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on PPC_STD_MMU && PPC32
|
|
|
|
|
|
2018-04-16 05:27:24 -06:00
|
|
|
config ARCH_ENABLE_SPLIT_PMD_PTLOCK
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on PPC_BOOK3S_64
|
|
|
|
|
|
2016-04-29 07:25:53 -06:00
|
|
|
config PPC_RADIX_MMU
|
|
|
|
|
bool "Radix MMU Support"
|
|
|
|
|
depends on PPC_BOOK3S_64
|
2017-07-06 16:39:20 -06:00
|
|
|
select ARCH_HAS_GIGANTIC_PAGE if (MEMORY_ISOLATION && COMPACTION) || CMA
|
2016-04-29 07:25:53 -06:00
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Enable support for the Power ISA 3.0 Radix style MMU. Currently this
|
|
|
|
|
is only implemented by IBM Power9 CPUs, if you don't have one of them
|
|
|
|
|
you can probably disable this.
|
|
|
|
|
|
2017-10-24 09:48:49 -06:00
|
|
|
config PPC_RADIX_MMU_DEFAULT
|
|
|
|
|
bool "Default to using the Radix MMU when possible"
|
|
|
|
|
depends on PPC_RADIX_MMU
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
When the hardware supports the Radix MMU, default to using it unless
|
|
|
|
|
"disable_radix[=yes]" is specified on the kernel command line.
|
|
|
|
|
|
|
|
|
|
If this option is disabled, the Hash MMU will be used by default,
|
|
|
|
|
unless "disable_radix=no" is specified on the kernel command line.
|
|
|
|
|
|
|
|
|
|
If you're unsure, say Y.
|
|
|
|
|
|
2017-07-06 16:39:05 -06:00
|
|
|
config ARCH_ENABLE_HUGEPAGE_MIGRATION
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on PPC_BOOK3S_64 && HUGETLB_PAGE && MIGRATION
|
|
|
|
|
|
|
|
|
|
|
2008-12-18 12:13:24 -07:00
|
|
|
config PPC_MMU_NOHASH
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on !PPC_STD_MMU
|
|
|
|
|
|
2009-02-12 15:12:40 -07:00
|
|
|
config PPC_BOOK3E_MMU
|
|
|
|
|
def_bool y
|
2009-07-23 17:15:59 -06:00
|
|
|
depends on FSL_BOOKE || PPC_BOOK3E
|
2009-02-12 15:12:40 -07:00
|
|
|
|
2007-06-12 10:30:17 -06:00
|
|
|
config PPC_MM_SLICES
|
|
|
|
|
bool
|
2017-10-18 22:08:43 -06:00
|
|
|
default y if PPC_BOOK3S_64
|
powerpc/mm/slice: Fix hugepage allocation at hint address on 8xx
On the 8xx, the page size is set in the PMD entry and applies to
all pages of the page table pointed by the said PMD entry.
When an app has some regular pages allocated (e.g. see below) and tries
to mmap() a huge page at a hint address covered by the same PMD entry,
the kernel accepts the hint allthough the 8xx cannot handle different
page sizes in the same PMD entry.
10000000-10001000 r-xp 00000000 00:0f 2597 /root/malloc
10010000-10011000 rwxp 00000000 00:0f 2597 /root/malloc
mmap(0x10080000, 524288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS|0x40000, -1, 0) = 0x10080000
This results the app remaining forever in do_page_fault()/hugetlb_fault()
and when interrupting that app, we get the following warning:
[162980.035629] WARNING: CPU: 0 PID: 2777 at arch/powerpc/mm/hugetlbpage.c:354 hugetlb_free_pgd_range+0xc8/0x1e4
[162980.035699] CPU: 0 PID: 2777 Comm: malloc Tainted: G W 4.14.6 #85
[162980.035744] task: c67e2c00 task.stack: c668e000
[162980.035783] NIP: c000fe18 LR: c00e1eec CTR: c00f90c0
[162980.035830] REGS: c668fc20 TRAP: 0700 Tainted: G W (4.14.6)
[162980.035854] MSR: 00029032 <EE,ME,IR,DR,RI> CR: 24044224 XER: 20000000
[162980.036003]
[162980.036003] GPR00: c00e1eec c668fcd0 c67e2c00 00000010 c6869410 10080000 00000000 77fb4000
[162980.036003] GPR08: ffff0001 0683c001 00000000 ffffff80 44028228 10018a34 00004008 418004fc
[162980.036003] GPR16: c668e000 00040100 c668e000 c06c0000 c668fe78 c668e000 c6835ba0 c668fd48
[162980.036003] GPR24: 00000000 73ffffff 74000000 00000001 77fb4000 100fffff 10100000 10100000
[162980.036743] NIP [c000fe18] hugetlb_free_pgd_range+0xc8/0x1e4
[162980.036839] LR [c00e1eec] free_pgtables+0x12c/0x150
[162980.036861] Call Trace:
[162980.036939] [c668fcd0] [c00f0774] unlink_anon_vmas+0x1c4/0x214 (unreliable)
[162980.037040] [c668fd10] [c00e1eec] free_pgtables+0x12c/0x150
[162980.037118] [c668fd40] [c00eabac] exit_mmap+0xe8/0x1b4
[162980.037210] [c668fda0] [c0019710] mmput.part.9+0x20/0xd8
[162980.037301] [c668fdb0] [c001ecb0] do_exit+0x1f0/0x93c
[162980.037386] [c668fe00] [c001f478] do_group_exit+0x40/0xcc
[162980.037479] [c668fe10] [c002a76c] get_signal+0x47c/0x614
[162980.037570] [c668fe70] [c0007840] do_signal+0x54/0x244
[162980.037654] [c668ff30] [c0007ae8] do_notify_resume+0x34/0x88
[162980.037744] [c668ff40] [c000dae8] do_user_signal+0x74/0xc4
[162980.037781] Instruction dump:
[162980.037821] 7fdff378 81370000 54a3463a 80890020 7d24182e 7c841a14 712a0004 4082ff94
[162980.038014] 2f890000 419e0010 712a0ff0 408200e0 <0fe00000> 54a9000a 7f984840 419d0094
[162980.038216] ---[ end trace c0ceeca8e7a5800a ]---
[162980.038754] BUG: non-zero nr_ptes on freeing mm: 1
[162985.363322] BUG: non-zero nr_ptes on freeing mm: -1
In order to fix this, this patch uses the address space "slices"
implemented for BOOK3S/64 and enhanced to support PPC32 by the
preceding patch.
This patch modifies the context.id on the 8xx to be in the range
[1:16] instead of [0:15] in order to identify context.id == 0 as
not initialised contexts as done on BOOK3S
This patch activates CONFIG_PPC_MM_SLICES when CONFIG_HUGETLB_PAGE is
selected for the 8xx
Alltough we could in theory have as many slices as PMD entries, the
current slices implementation limits the number of low slices to 16.
This limitation is not preventing us to fix the initial issue allthough
it is suboptimal. It will be cured in a subsequent patch.
Fixes: 4b91428699477 ("powerpc/8xx: Implement support of hugepages")
Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
2018-02-22 07:27:26 -07:00
|
|
|
default y if PPC_8xx && HUGETLB_PAGE
|
2007-06-12 10:30:17 -06:00
|
|
|
|
2009-06-17 05:50:04 -06:00
|
|
|
config PPC_HAVE_PMU_SUPPORT
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config PPC_PERF_CTRS
|
|
|
|
|
def_bool y
|
perf: Do the big rename: Performance Counters -> Performance Events
Bye-bye Performance Counters, welcome Performance Events!
In the past few months the perfcounters subsystem has grown out its
initial role of counting hardware events, and has become (and is
becoming) a much broader generic event enumeration, reporting, logging,
monitoring, analysis facility.
Naming its core object 'perf_counter' and naming the subsystem
'perfcounters' has become more and more of a misnomer. With pending
code like hw-breakpoints support the 'counter' name is less and
less appropriate.
All in one, we've decided to rename the subsystem to 'performance
events' and to propagate this rename through all fields, variables
and API names. (in an ABI compatible fashion)
The word 'event' is also a bit shorter than 'counter' - which makes
it slightly more convenient to write/handle as well.
Thanks goes to Stephane Eranian who first observed this misnomer and
suggested a rename.
User-space tooling and ABI compatibility is not affected - this patch
should be function-invariant. (Also, defconfigs were not touched to
keep the size down.)
This patch has been generated via the following script:
FILES=$(find * -type f | grep -vE 'oprofile|[^K]config')
sed -i \
-e 's/PERF_EVENT_/PERF_RECORD_/g' \
-e 's/PERF_COUNTER/PERF_EVENT/g' \
-e 's/perf_counter/perf_event/g' \
-e 's/nb_counters/nb_events/g' \
-e 's/swcounter/swevent/g' \
-e 's/tpcounter_event/tp_event/g' \
$FILES
for N in $(find . -name perf_counter.[ch]); do
M=$(echo $N | sed 's/perf_counter/perf_event/g')
mv $N $M
done
FILES=$(find . -name perf_event.*)
sed -i \
-e 's/COUNTER_MASK/REG_MASK/g' \
-e 's/COUNTER/EVENT/g' \
-e 's/\<event\>/event_id/g' \
-e 's/counter/event/g' \
-e 's/Counter/Event/g' \
$FILES
... to keep it as correct as possible. This script can also be
used by anyone who has pending perfcounters patches - it converts
a Linux kernel tree over to the new naming. We tried to time this
change to the point in time where the amount of pending patches
is the smallest: the end of the merge window.
Namespace clashes were fixed up in a preparatory patch - and some
stylistic fallout will be fixed up in a subsequent patch.
( NOTE: 'counters' are still the proper terminology when we deal
with hardware registers - and these sed scripts are a bit
over-eager in renaming them. I've undone some of that, but
in case there's something left where 'counter' would be
better than 'event' we can undo that on an individual basis
instead of touching an otherwise nicely automated patch. )
Suggested-by: Stephane Eranian <eranian@google.com>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Acked-by: Paul Mackerras <paulus@samba.org>
Reviewed-by: Arjan van de Ven <arjan@linux.intel.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Howells <dhowells@redhat.com>
Cc: Kyle McMartin <kyle@mcmartin.ca>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: <linux-arch@vger.kernel.org>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-09-21 04:02:48 -06:00
|
|
|
depends on PERF_EVENTS && PPC_HAVE_PMU_SUPPORT
|
2009-06-17 05:50:04 -06:00
|
|
|
help
|
perf: Do the big rename: Performance Counters -> Performance Events
Bye-bye Performance Counters, welcome Performance Events!
In the past few months the perfcounters subsystem has grown out its
initial role of counting hardware events, and has become (and is
becoming) a much broader generic event enumeration, reporting, logging,
monitoring, analysis facility.
Naming its core object 'perf_counter' and naming the subsystem
'perfcounters' has become more and more of a misnomer. With pending
code like hw-breakpoints support the 'counter' name is less and
less appropriate.
All in one, we've decided to rename the subsystem to 'performance
events' and to propagate this rename through all fields, variables
and API names. (in an ABI compatible fashion)
The word 'event' is also a bit shorter than 'counter' - which makes
it slightly more convenient to write/handle as well.
Thanks goes to Stephane Eranian who first observed this misnomer and
suggested a rename.
User-space tooling and ABI compatibility is not affected - this patch
should be function-invariant. (Also, defconfigs were not touched to
keep the size down.)
This patch has been generated via the following script:
FILES=$(find * -type f | grep -vE 'oprofile|[^K]config')
sed -i \
-e 's/PERF_EVENT_/PERF_RECORD_/g' \
-e 's/PERF_COUNTER/PERF_EVENT/g' \
-e 's/perf_counter/perf_event/g' \
-e 's/nb_counters/nb_events/g' \
-e 's/swcounter/swevent/g' \
-e 's/tpcounter_event/tp_event/g' \
$FILES
for N in $(find . -name perf_counter.[ch]); do
M=$(echo $N | sed 's/perf_counter/perf_event/g')
mv $N $M
done
FILES=$(find . -name perf_event.*)
sed -i \
-e 's/COUNTER_MASK/REG_MASK/g' \
-e 's/COUNTER/EVENT/g' \
-e 's/\<event\>/event_id/g' \
-e 's/counter/event/g' \
-e 's/Counter/Event/g' \
$FILES
... to keep it as correct as possible. This script can also be
used by anyone who has pending perfcounters patches - it converts
a Linux kernel tree over to the new naming. We tried to time this
change to the point in time where the amount of pending patches
is the smallest: the end of the merge window.
Namespace clashes were fixed up in a preparatory patch - and some
stylistic fallout will be fixed up in a subsequent patch.
( NOTE: 'counters' are still the proper terminology when we deal
with hardware registers - and these sed scripts are a bit
over-eager in renaming them. I've undone some of that, but
in case there's something left where 'counter' would be
better than 'event' we can undo that on an individual basis
instead of touching an otherwise nicely automated patch. )
Suggested-by: Stephane Eranian <eranian@google.com>
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Acked-by: Paul Mackerras <paulus@samba.org>
Reviewed-by: Arjan van de Ven <arjan@linux.intel.com>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Howells <dhowells@redhat.com>
Cc: Kyle McMartin <kyle@mcmartin.ca>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: <linux-arch@vger.kernel.org>
LKML-Reference: <new-submission>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
2009-09-21 04:02:48 -06:00
|
|
|
This enables the powerpc-specific perf_event back-end.
|
2009-06-17 05:50:04 -06:00
|
|
|
|
2017-04-04 20:44:49 -06:00
|
|
|
config FORCE_SMP
|
|
|
|
|
# Allow platforms to force SMP=y by selecting this
|
|
|
|
|
bool
|
|
|
|
|
select SMP
|
|
|
|
|
|
2007-06-12 10:30:17 -06:00
|
|
|
config SMP
|
2010-03-05 03:43:12 -07:00
|
|
|
depends on PPC_BOOK3S || PPC_BOOK3E || FSL_BOOKE || PPC_47x
|
2017-04-05 01:54:49 -06:00
|
|
|
select GENERIC_IRQ_MIGRATION
|
2017-04-04 20:44:49 -06:00
|
|
|
bool "Symmetric multi-processing support" if !FORCE_SMP
|
2007-06-12 10:30:17 -06:00
|
|
|
---help---
|
|
|
|
|
This enables support for systems with more than one CPU. If you have
|
|
|
|
|
a system with only one CPU, say N. If you have a system with more
|
|
|
|
|
than one CPU, say Y. Note that the kernel does not currently
|
|
|
|
|
support SMP machines with 603/603e/603ev or PPC750 ("G3") processors
|
|
|
|
|
since they have inadequate hardware support for multiprocessor
|
|
|
|
|
operation.
|
|
|
|
|
|
|
|
|
|
If you say N here, the kernel will run on single and multiprocessor
|
|
|
|
|
machines, but will use only one CPU of a multiprocessor machine. If
|
|
|
|
|
you say Y here, the kernel will run on single-processor machines.
|
|
|
|
|
On a single-processor machine, the kernel will run faster if you say
|
|
|
|
|
N here.
|
|
|
|
|
|
|
|
|
|
If you don't know what to do here, say N.
|
|
|
|
|
|
|
|
|
|
config NR_CPUS
|
2009-05-17 09:13:16 -06:00
|
|
|
int "Maximum number of CPUs (2-8192)"
|
|
|
|
|
range 2 8192
|
2007-06-12 10:30:17 -06:00
|
|
|
depends on SMP
|
|
|
|
|
default "32" if PPC64
|
|
|
|
|
default "4"
|
|
|
|
|
|
|
|
|
|
config NOT_COHERENT_CACHE
|
|
|
|
|
bool
|
2017-08-08 05:58:54 -06:00
|
|
|
depends on 4xx || PPC_8xx || E200 || PPC_MPC512x || GAMECUBE_COMMON
|
2010-03-05 03:43:12 -07:00
|
|
|
default n if PPC_47x
|
2007-06-12 10:30:17 -06:00
|
|
|
default y
|
|
|
|
|
|
2007-07-17 16:21:29 -06:00
|
|
|
config CHECK_CACHE_COHERENCY
|
2007-06-12 10:30:17 -06:00
|
|
|
bool
|
|
|
|
|
|
2012-11-14 11:49:49 -07:00
|
|
|
config PPC_DOORBELL
|
|
|
|
|
bool
|
|
|
|
|
|
2007-06-12 10:30:17 -06:00
|
|
|
endmenu
|
2013-11-20 04:15:05 -07:00
|
|
|
|
2015-05-11 04:01:02 -06:00
|
|
|
config VDSO32
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on PPC32 || CPU_BIG_ENDIAN
|
|
|
|
|
help
|
|
|
|
|
This symbol controls whether we build the 32-bit VDSO. We obviously
|
|
|
|
|
want to do that if we're building a 32-bit kernel. If we're building
|
|
|
|
|
a 64-bit kernel then we only want a 32-bit VDSO if we're building for
|
|
|
|
|
big endian. That is because the only little endian configuration we
|
|
|
|
|
support is ppc64le which is 64-bit only.
|
|
|
|
|
|
2013-11-20 22:33:55 -07:00
|
|
|
choice
|
|
|
|
|
prompt "Endianness selection"
|
|
|
|
|
default CPU_BIG_ENDIAN
|
2013-11-20 04:15:05 -07:00
|
|
|
help
|
|
|
|
|
This option selects whether a big endian or little endian kernel will
|
|
|
|
|
be built.
|
|
|
|
|
|
2013-11-20 22:33:55 -07:00
|
|
|
config CPU_BIG_ENDIAN
|
|
|
|
|
bool "Build big endian kernel"
|
|
|
|
|
help
|
|
|
|
|
Build a big endian kernel.
|
|
|
|
|
|
|
|
|
|
If unsure, select this option.
|
|
|
|
|
|
|
|
|
|
config CPU_LITTLE_ENDIAN
|
|
|
|
|
bool "Build little endian kernel"
|
2015-04-21 23:36:50 -06:00
|
|
|
depends on PPC_BOOK3S_64
|
2014-04-24 01:23:39 -06:00
|
|
|
select PPC64_BOOT_WRAPPER
|
2013-11-20 22:33:55 -07:00
|
|
|
help
|
|
|
|
|
Build a little endian kernel.
|
|
|
|
|
|
2013-11-20 04:15:05 -07:00
|
|
|
Note that if cross compiling a little endian kernel,
|
|
|
|
|
CROSS_COMPILE must point to a toolchain capable of targeting
|
|
|
|
|
little endian powerpc.
|
2013-11-20 22:33:55 -07:00
|
|
|
|
|
|
|
|
endchoice
|
2014-04-24 01:23:39 -06:00
|
|
|
|
|
|
|
|
config PPC64_BOOT_WRAPPER
|
|
|
|
|
def_bool n
|
|
|
|
|
depends on CPU_LITTLE_ENDIAN
|