2005-09-26 06:04:21 +00:00
|
|
|
menu "Kernel hacking"
|
|
|
|
|
|
|
|
|
|
source "lib/Kconfig.debug"
|
|
|
|
|
|
2009-06-09 20:48:51 +00:00
|
|
|
config PPC_DISABLE_WERROR
|
|
|
|
|
bool "Don't build arch/powerpc code with -Werror"
|
|
|
|
|
default n
|
|
|
|
|
help
|
|
|
|
|
This option tells the compiler NOT to build the code under
|
|
|
|
|
arch/powerpc with the -Werror flag (which means warnings
|
|
|
|
|
are treated as errors).
|
|
|
|
|
|
|
|
|
|
Only enable this if you are hitting a build failure in the
|
|
|
|
|
arch/powerpc code caused by a warning, and you don't feel
|
|
|
|
|
inclined to fix it.
|
|
|
|
|
|
|
|
|
|
config PPC_WERROR
|
|
|
|
|
bool
|
|
|
|
|
depends on !PPC_DISABLE_WERROR
|
|
|
|
|
default y
|
|
|
|
|
|
2008-11-20 03:24:07 +00:00
|
|
|
config PRINT_STACK_DEPTH
|
|
|
|
|
int "Stack depth to print" if DEBUG_KERNEL
|
|
|
|
|
default 64
|
|
|
|
|
help
|
|
|
|
|
This option allows you to set the stack depth that the kernel
|
|
|
|
|
prints in stack traces. This can be useful if your display is
|
|
|
|
|
too small and stack traces cause important information to
|
|
|
|
|
scroll off the screen.
|
|
|
|
|
|
2006-09-06 23:23:12 +00:00
|
|
|
config HCALL_STATS
|
|
|
|
|
bool "Hypervisor call instrumentation"
|
2009-10-26 18:50:29 +00:00
|
|
|
depends on PPC_PSERIES && DEBUG_FS && TRACEPOINTS
|
2006-09-06 23:23:12 +00:00
|
|
|
help
|
|
|
|
|
Adds code to keep track of the number of hypervisor calls made and
|
2007-05-09 05:12:20 +00:00
|
|
|
the amount of time spent in hypervisor calls. Wall time spent in
|
2006-09-06 23:23:12 +00:00
|
|
|
each call is always calculated, and if available CPU cycles spent
|
|
|
|
|
are also calculated. A directory named hcall_inst is added at the
|
|
|
|
|
root of the debugfs filesystem. Within the hcall_inst directory
|
|
|
|
|
are files that contain CPU specific call statistics.
|
|
|
|
|
|
|
|
|
|
This option will add a small amount of overhead to all hypervisor
|
|
|
|
|
calls.
|
|
|
|
|
|
2009-05-18 02:10:05 +00:00
|
|
|
config PPC_EMULATED_STATS
|
|
|
|
|
bool "Emulated instructions tracking"
|
|
|
|
|
depends on DEBUG_FS
|
|
|
|
|
help
|
|
|
|
|
Adds code to keep track of the number of instructions that are
|
|
|
|
|
emulated by the in-kernel emulator. Counters for the various classes
|
|
|
|
|
of emulated instructions are available under
|
|
|
|
|
powerpc/emulated_instructions/ in the root of the debugfs file
|
|
|
|
|
system. Optionally (controlled by
|
|
|
|
|
powerpc/emulated_instructions/do_warn in debugfs), rate-limited
|
|
|
|
|
warnings can be printed to the console when instructions are
|
|
|
|
|
emulated.
|
|
|
|
|
|
2008-06-24 01:32:32 +00:00
|
|
|
config CODE_PATCHING_SELFTEST
|
|
|
|
|
bool "Run self-tests of the code-patching code."
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
default n
|
|
|
|
|
|
2008-06-24 01:33:03 +00:00
|
|
|
config FTR_FIXUP_SELFTEST
|
|
|
|
|
bool "Run self-tests of the feature-fixup code."
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
default n
|
|
|
|
|
|
2008-08-05 23:10:01 +00:00
|
|
|
config MSI_BITMAP_SELFTEST
|
|
|
|
|
bool "Run self-tests of the MSI bitmap code."
|
|
|
|
|
depends on DEBUG_KERNEL
|
|
|
|
|
default n
|
|
|
|
|
|
2005-09-26 06:04:21 +00:00
|
|
|
config XMON
|
|
|
|
|
bool "Include xmon kernel debugger"
|
2008-07-23 16:30:15 +00:00
|
|
|
depends on DEBUG_KERNEL
|
2005-09-26 06:04:21 +00:00
|
|
|
help
|
|
|
|
|
Include in-kernel hooks for the xmon kernel monitor/debugger.
|
|
|
|
|
Unless you are intending to debug the kernel, say N here.
|
2005-10-10 12:15:52 +00:00
|
|
|
Make sure to enable also CONFIG_BOOTX_TEXT on Macs. Otherwise
|
|
|
|
|
nothing will appear on the screen (xmon writes directly to the
|
|
|
|
|
framebuffer memory).
|
|
|
|
|
The cmdline option 'xmon' or 'xmon=early' will drop into xmon
|
|
|
|
|
very early during boot. 'xmon=on' will just enable the xmon
|
|
|
|
|
debugger hooks. 'xmon=off' will disable the debugger hooks
|
|
|
|
|
if CONFIG_XMON_DEFAULT is set.
|
2006-09-08 14:29:21 +00:00
|
|
|
xmon will print a backtrace on the very first invocation.
|
|
|
|
|
'xmon=nobt' will disable this autobacktrace.
|
2005-10-10 12:15:52 +00:00
|
|
|
|
|
|
|
|
config XMON_DEFAULT
|
|
|
|
|
bool "Enable xmon by default"
|
|
|
|
|
depends on XMON
|
|
|
|
|
help
|
|
|
|
|
xmon is normally disabled unless booted with 'xmon=on'.
|
|
|
|
|
Use 'xmon=off' to disable xmon init during runtime.
|
|
|
|
|
|
2006-11-22 23:46:45 +00:00
|
|
|
config XMON_DISASSEMBLY
|
|
|
|
|
bool "Include disassembly support in xmon"
|
|
|
|
|
depends on XMON
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Include support for disassembling in xmon. You probably want
|
|
|
|
|
to say Y here, unless you're building for a memory-constrained
|
|
|
|
|
system.
|
|
|
|
|
|
2008-07-23 16:30:15 +00:00
|
|
|
config DEBUGGER
|
|
|
|
|
bool
|
|
|
|
|
depends on KGDB || XMON
|
|
|
|
|
default y
|
|
|
|
|
|
2005-09-26 06:04:21 +00:00
|
|
|
config BDI_SWITCH
|
|
|
|
|
bool "Include BDI-2000 user context switcher"
|
2005-10-10 12:15:52 +00:00
|
|
|
depends on DEBUG_KERNEL && PPC32
|
2005-09-26 06:04:21 +00:00
|
|
|
help
|
|
|
|
|
Include in-kernel support for the Abatron BDI2000 debugger.
|
|
|
|
|
Unless you are intending to debug the kernel with one of these
|
|
|
|
|
machines, say N here.
|
|
|
|
|
|
|
|
|
|
config BOOTX_TEXT
|
|
|
|
|
bool "Support for early boot text console (BootX or OpenFirmware only)"
|
2009-03-10 17:53:27 +00:00
|
|
|
depends on PPC_OF && PPC_BOOK3S
|
2005-09-26 06:04:21 +00:00
|
|
|
help
|
|
|
|
|
Say Y here to see progress messages from the boot firmware in text
|
|
|
|
|
mode. Requires either BootX or Open Firmware.
|
|
|
|
|
|
2006-05-09 06:03:51 +00:00
|
|
|
config PPC_EARLY_DEBUG
|
|
|
|
|
bool "Early debugging (dangerous)"
|
2007-12-11 03:48:24 +00:00
|
|
|
help
|
|
|
|
|
Say Y to enable some early debugging facilities that may be available
|
|
|
|
|
for your processor/board combination. Those facilities are hacks
|
|
|
|
|
intended to debug problems early during boot, this should not be
|
|
|
|
|
enabled in a production kernel.
|
|
|
|
|
Note that enabling this will also cause the kernel default log level
|
|
|
|
|
to be pushed to max automatically very early during boot
|
2006-05-09 06:03:51 +00:00
|
|
|
|
2006-01-11 00:54:09 +00:00
|
|
|
choice
|
2006-05-09 06:03:51 +00:00
|
|
|
prompt "Early debugging console"
|
|
|
|
|
depends on PPC_EARLY_DEBUG
|
2006-01-11 00:54:09 +00:00
|
|
|
help
|
2006-05-09 06:03:51 +00:00
|
|
|
Use the selected console for early debugging. Careful, if you
|
|
|
|
|
enable debugging for the wrong type of machine your kernel
|
|
|
|
|
_will not boot_.
|
2006-01-11 00:54:09 +00:00
|
|
|
|
2013-04-29 03:42:43 +00:00
|
|
|
config PPC_EARLY_DEBUG_BOOTX
|
|
|
|
|
bool "BootX or OpenFirmware"
|
|
|
|
|
depends on BOOTX_TEXT
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for a machine using BootX
|
|
|
|
|
or OpenFirmware.
|
|
|
|
|
|
2006-01-11 00:54:09 +00:00
|
|
|
config PPC_EARLY_DEBUG_LPAR
|
|
|
|
|
bool "LPAR HV Console"
|
|
|
|
|
depends on PPC_PSERIES
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for a machine with a HVC
|
|
|
|
|
console on vterm 0.
|
|
|
|
|
|
powerpc/pseries: Re-implement HVSI as part of hvc_vio
On pseries machines, consoles are provided by the hypervisor using
a low level get_chars/put_chars type interface. However, this is
really just a transport to the service processor which implements
them either as "raw" console (networked consoles, HMC, ...) or as
"hvsi" serial ports.
The later is a simple packet protocol on top of the raw character
interface that is supposed to convey additional "serial port" style
semantics. In practice however, all it does is provide a way to
read the CD line and set/clear our DTR line, that's it.
We currently implement the "raw" protocol as an hvc console backend
(/dev/hvcN) and the "hvsi" protocol using a separate tty driver
(/dev/hvsi0).
However this is quite impractical. The arbitrary difference between
the two type of devices has been a major source of user (and distro)
confusion. Additionally, there's an additional mini -hvsi implementation
in the pseries platform code for our low level debug console and early
boot kernel messages, which means code duplication, though that low
level variant is impractical as it's incapable of doing the initial
protocol negociation to establish the link to the FSP.
This essentially replaces the dedicated hvsi driver and the platform
udbg code completely by extending the existing hvc_vio backend used
in "raw" mode so that:
- It now supports HVSI as well
- We add support for hvc backend providing tiocm{get,set}
- It also provides a udbg interface for early debug and boot console
This is overall less code, though this will only be obvious once we
remove the old "hvsi" driver, which is still available for now. When
the old driver is enabled, the new code still kicks in for the low
level udbg console, replacing the old mini implementation in the platform
code, it just doesn't provide the higher level "hvc" interface.
In addition to producing generally simler code, this has several benefits
over our current situation:
- The user/distro only has to deal with /dev/hvcN for the hypervisor
console, avoiding all sort of confusion that has plagued us in the past
- The tty, kernel and low level debug console all use the same code
base which supports the full protocol establishment process, thus the
console is now available much earlier than it used to be with the
old HVSI driver. The kernel console works much earlier and udbg is
available much earlier too. Hackers can enable a hard coded very-early
debug console as well that works with HVSI (previously that was only
supported for the "raw" mode).
I've tried to keep the same semantics as hvsi relative to how I react
to things like CD changes, with some subtle differences though:
- I clear DTR on close if HUPCL is set
- Current hvsi triggers a hangup if it detects a up->down transition
on CD (you can still open a console with CD down). My new implementation
triggers a hangup if the link to the FSP is severed, and severs it upon
detecting a up->down transition on CD.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2011-05-12 03:46:38 +00:00
|
|
|
config PPC_EARLY_DEBUG_LPAR_HVSI
|
|
|
|
|
bool "LPAR HVSI Console"
|
|
|
|
|
depends on PPC_PSERIES
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for a machine with a HVSI
|
|
|
|
|
console on a specified vterm.
|
|
|
|
|
|
2006-01-11 00:54:09 +00:00
|
|
|
config PPC_EARLY_DEBUG_G5
|
|
|
|
|
bool "Apple G5"
|
|
|
|
|
depends on PPC_PMAC64
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for Apple G5 machines.
|
|
|
|
|
|
2006-06-23 08:20:16 +00:00
|
|
|
config PPC_EARLY_DEBUG_RTAS_PANEL
|
2006-01-11 00:54:09 +00:00
|
|
|
bool "RTAS Panel"
|
|
|
|
|
depends on PPC_RTAS
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging via the RTAS panel.
|
|
|
|
|
|
2006-06-23 08:20:16 +00:00
|
|
|
config PPC_EARLY_DEBUG_RTAS_CONSOLE
|
|
|
|
|
bool "RTAS Console"
|
|
|
|
|
depends on PPC_RTAS
|
|
|
|
|
select UDBG_RTAS_CONSOLE
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging via the RTAS console.
|
|
|
|
|
|
2006-01-11 00:54:09 +00:00
|
|
|
config PPC_EARLY_DEBUG_MAPLE
|
|
|
|
|
bool "Maple real mode"
|
|
|
|
|
depends on PPC_MAPLE
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for Maple.
|
|
|
|
|
|
2007-02-04 22:36:49 +00:00
|
|
|
config PPC_EARLY_DEBUG_PAS_REALMODE
|
|
|
|
|
bool "PA Semi real mode"
|
|
|
|
|
depends on PPC_PASEMI
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for PA Semi.
|
|
|
|
|
Output will be on UART0.
|
|
|
|
|
|
2007-02-02 07:47:17 +00:00
|
|
|
config PPC_EARLY_DEBUG_BEAT
|
|
|
|
|
bool "Beat HV Console"
|
|
|
|
|
depends on PPC_CELLEB
|
|
|
|
|
select PPC_UDBG_BEAT
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for Celleb with Beat.
|
|
|
|
|
|
2007-05-08 02:59:31 +00:00
|
|
|
config PPC_EARLY_DEBUG_44x
|
|
|
|
|
bool "Early serial debugging for IBM/AMCC 44x CPUs"
|
2011-09-19 17:44:48 +00:00
|
|
|
# PPC_EARLY_DEBUG on 440 leaves AS=1 mappings above the TLB high water
|
|
|
|
|
# mark, which doesn't work with current 440 KVM.
|
|
|
|
|
depends on 44x && !KVM
|
2007-05-08 02:59:31 +00:00
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for IBM 44x chips via the
|
2007-12-21 04:39:28 +00:00
|
|
|
inbuilt serial port. If you enable this, ensure you set
|
|
|
|
|
PPC_EARLY_DEBUG_44x_PHYSLOW below to suit your target board.
|
2007-05-08 02:59:31 +00:00
|
|
|
|
2007-12-21 04:39:26 +00:00
|
|
|
config PPC_EARLY_DEBUG_40x
|
|
|
|
|
bool "Early serial debugging for IBM/AMCC 40x CPUs"
|
|
|
|
|
depends on 40x
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for IBM 40x chips via the
|
|
|
|
|
inbuilt serial port. This works on chips with a 16550 compatible
|
|
|
|
|
UART. Xilinx chips with uartlite cannot use this option.
|
|
|
|
|
|
2007-07-16 16:43:43 +00:00
|
|
|
config PPC_EARLY_DEBUG_CPM
|
|
|
|
|
bool "Early serial debugging for Freescale CPM-based serial ports"
|
|
|
|
|
depends on SERIAL_CPM
|
|
|
|
|
select PIN_TLB if PPC_8xx
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for Freescale chips
|
|
|
|
|
using a CPM-based serial port. This assumes that the bootwrapper
|
|
|
|
|
has run, and set up the CPM in a particular way.
|
|
|
|
|
|
2009-12-12 06:31:51 +00:00
|
|
|
config PPC_EARLY_DEBUG_USBGECKO
|
|
|
|
|
bool "Early debugging through the USB Gecko adapter"
|
|
|
|
|
depends on GAMECUBE_COMMON
|
|
|
|
|
select USBGECKO_UDBG
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for Nintendo GameCube/Wii
|
|
|
|
|
consoles via an external USB Gecko adapter.
|
|
|
|
|
|
2011-04-14 22:32:08 +00:00
|
|
|
config PPC_EARLY_DEBUG_WSP
|
|
|
|
|
bool "Early debugging via WSP's internal UART"
|
|
|
|
|
depends on PPC_WSP
|
|
|
|
|
select PPC_UDBG_16550
|
|
|
|
|
|
2011-08-31 06:32:26 +00:00
|
|
|
config PPC_EARLY_DEBUG_PS3GELIC
|
|
|
|
|
bool "Early debugging through the PS3 Ethernet port"
|
|
|
|
|
depends on PPC_PS3
|
|
|
|
|
select PS3GELIC_UDBG
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for the PlayStation3 via
|
|
|
|
|
UDP broadcasts sent out through the Ethernet port.
|
|
|
|
|
|
2011-09-19 17:44:59 +00:00
|
|
|
config PPC_EARLY_DEBUG_OPAL_RAW
|
|
|
|
|
bool "OPAL raw console"
|
|
|
|
|
depends on HVC_OPAL
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for the PowerNV platform
|
|
|
|
|
using a "raw" console
|
|
|
|
|
|
|
|
|
|
config PPC_EARLY_DEBUG_OPAL_HVSI
|
|
|
|
|
bool "OPAL hvsi console"
|
|
|
|
|
depends on HVC_OPAL
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging for the PowerNV platform
|
|
|
|
|
using an "hvsi" console
|
|
|
|
|
|
2013-04-29 18:07:47 +00:00
|
|
|
config PPC_EARLY_DEBUG_MEMCONS
|
|
|
|
|
bool "In memory console"
|
|
|
|
|
help
|
|
|
|
|
Select this to enable early debugging using an in memory console.
|
|
|
|
|
This console provides input and output buffers stored within the
|
|
|
|
|
kernel BSS and should be safe to select on any system. A debugger
|
|
|
|
|
can then be used to read kernel output or send input to the console.
|
2006-01-11 00:54:09 +00:00
|
|
|
endchoice
|
|
|
|
|
|
2013-04-29 18:07:47 +00:00
|
|
|
config PPC_MEMCONS_OUTPUT_SIZE
|
|
|
|
|
int "In memory console output buffer size"
|
|
|
|
|
depends on PPC_EARLY_DEBUG_MEMCONS
|
|
|
|
|
default 4096
|
|
|
|
|
help
|
|
|
|
|
Selects the size of the output buffer (in bytes) of the in memory
|
|
|
|
|
console.
|
|
|
|
|
|
|
|
|
|
config PPC_MEMCONS_INPUT_SIZE
|
|
|
|
|
int "In memory console input buffer size"
|
|
|
|
|
depends on PPC_EARLY_DEBUG_MEMCONS
|
|
|
|
|
default 128
|
|
|
|
|
help
|
|
|
|
|
Selects the size of the input buffer (in bytes) of the in memory
|
|
|
|
|
console.
|
|
|
|
|
|
2011-09-19 17:44:59 +00:00
|
|
|
config PPC_EARLY_DEBUG_OPAL
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on PPC_EARLY_DEBUG_OPAL_RAW || PPC_EARLY_DEBUG_OPAL_HVSI
|
|
|
|
|
|
|
|
|
|
|
powerpc/pseries: Re-implement HVSI as part of hvc_vio
On pseries machines, consoles are provided by the hypervisor using
a low level get_chars/put_chars type interface. However, this is
really just a transport to the service processor which implements
them either as "raw" console (networked consoles, HMC, ...) or as
"hvsi" serial ports.
The later is a simple packet protocol on top of the raw character
interface that is supposed to convey additional "serial port" style
semantics. In practice however, all it does is provide a way to
read the CD line and set/clear our DTR line, that's it.
We currently implement the "raw" protocol as an hvc console backend
(/dev/hvcN) and the "hvsi" protocol using a separate tty driver
(/dev/hvsi0).
However this is quite impractical. The arbitrary difference between
the two type of devices has been a major source of user (and distro)
confusion. Additionally, there's an additional mini -hvsi implementation
in the pseries platform code for our low level debug console and early
boot kernel messages, which means code duplication, though that low
level variant is impractical as it's incapable of doing the initial
protocol negociation to establish the link to the FSP.
This essentially replaces the dedicated hvsi driver and the platform
udbg code completely by extending the existing hvc_vio backend used
in "raw" mode so that:
- It now supports HVSI as well
- We add support for hvc backend providing tiocm{get,set}
- It also provides a udbg interface for early debug and boot console
This is overall less code, though this will only be obvious once we
remove the old "hvsi" driver, which is still available for now. When
the old driver is enabled, the new code still kicks in for the low
level udbg console, replacing the old mini implementation in the platform
code, it just doesn't provide the higher level "hvc" interface.
In addition to producing generally simler code, this has several benefits
over our current situation:
- The user/distro only has to deal with /dev/hvcN for the hypervisor
console, avoiding all sort of confusion that has plagued us in the past
- The tty, kernel and low level debug console all use the same code
base which supports the full protocol establishment process, thus the
console is now available much earlier than it used to be with the
old HVSI driver. The kernel console works much earlier and udbg is
available much earlier too. Hackers can enable a hard coded very-early
debug console as well that works with HVSI (previously that was only
supported for the "raw" mode).
I've tried to keep the same semantics as hvsi relative to how I react
to things like CD changes, with some subtle differences though:
- I clear DTR on close if HUPCL is set
- Current hvsi triggers a hangup if it detects a up->down transition
on CD (you can still open a console with CD down). My new implementation
triggers a hangup if the link to the FSP is severed, and severs it upon
detecting a up->down transition on CD.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
2011-05-12 03:46:38 +00:00
|
|
|
config PPC_EARLY_DEBUG_HVSI_VTERMNO
|
|
|
|
|
hex "vterm number to use with early debug HVSI"
|
|
|
|
|
depends on PPC_EARLY_DEBUG_LPAR_HVSI
|
|
|
|
|
default "0x30000000"
|
|
|
|
|
help
|
|
|
|
|
You probably want 0x30000000 for your first serial port and
|
|
|
|
|
0x30000001 for your second one
|
|
|
|
|
|
2011-09-19 17:44:59 +00:00
|
|
|
config PPC_EARLY_DEBUG_OPAL_VTERMNO
|
|
|
|
|
hex "vterm number to use with OPAL early debug"
|
|
|
|
|
depends on PPC_EARLY_DEBUG_OPAL
|
|
|
|
|
default "0"
|
|
|
|
|
help
|
|
|
|
|
This correspond to which /dev/hvcN you want to use for early
|
|
|
|
|
debug.
|
|
|
|
|
|
|
|
|
|
On OPAL v1 (takeover) this should always be 0
|
|
|
|
|
On OPAL v2, this will be 0 for network console and 1 or 2 for
|
|
|
|
|
the machine built-in serial ports.
|
|
|
|
|
|
2007-05-08 02:59:31 +00:00
|
|
|
config PPC_EARLY_DEBUG_44x_PHYSLOW
|
|
|
|
|
hex "Low 32 bits of early debug UART physical address"
|
2007-09-26 18:02:52 +00:00
|
|
|
depends on PPC_EARLY_DEBUG_44x
|
2007-05-08 02:59:31 +00:00
|
|
|
default "0x40000200"
|
2007-12-21 04:39:28 +00:00
|
|
|
help
|
|
|
|
|
You probably want 0x40000200 for ebony boards and
|
|
|
|
|
0x40000300 for taishan
|
2007-05-08 02:59:31 +00:00
|
|
|
|
|
|
|
|
config PPC_EARLY_DEBUG_44x_PHYSHIGH
|
|
|
|
|
hex "EPRN of early debug UART physical address"
|
2007-09-26 18:02:52 +00:00
|
|
|
depends on PPC_EARLY_DEBUG_44x
|
2007-05-08 02:59:31 +00:00
|
|
|
default "0x1"
|
|
|
|
|
|
2007-12-21 04:39:26 +00:00
|
|
|
config PPC_EARLY_DEBUG_40x_PHYSADDR
|
|
|
|
|
hex "Early debug UART physical address"
|
|
|
|
|
depends on PPC_EARLY_DEBUG_40x
|
|
|
|
|
default "0xef600300"
|
|
|
|
|
|
2007-07-16 16:43:43 +00:00
|
|
|
config PPC_EARLY_DEBUG_CPM_ADDR
|
|
|
|
|
hex "CPM UART early debug transmit descriptor address"
|
|
|
|
|
depends on PPC_EARLY_DEBUG_CPM
|
2007-09-28 19:06:16 +00:00
|
|
|
default "0xfa202008" if PPC_EP88XC
|
2008-04-10 15:01:59 +00:00
|
|
|
default "0xf0001ff8" if CPM2
|
2007-09-28 19:06:16 +00:00
|
|
|
default "0xff002008" if CPM1
|
2007-07-16 16:43:43 +00:00
|
|
|
help
|
|
|
|
|
This specifies the address of the transmit descriptor
|
|
|
|
|
used for early debug output. Because it is needed before
|
|
|
|
|
platform probing is done, all platforms selected must
|
|
|
|
|
share the same address.
|
|
|
|
|
|
2011-08-30 09:19:17 +00:00
|
|
|
config STRICT_DEVMEM
|
|
|
|
|
def_bool y
|
|
|
|
|
prompt "Filter access to /dev/mem"
|
|
|
|
|
help
|
|
|
|
|
This option restricts access to /dev/mem. If this option is
|
|
|
|
|
disabled, you allow userspace access to all memory, including
|
|
|
|
|
kernel and userspace memory. Accidental memory access is likely
|
|
|
|
|
to be disastrous.
|
|
|
|
|
Memory access is required for experts who want to debug the kernel.
|
|
|
|
|
|
|
|
|
|
If you are unsure, say Y.
|
|
|
|
|
|
2012-06-24 18:26:17 +00:00
|
|
|
config FAIL_IOMMU
|
|
|
|
|
bool "Fault-injection capability for IOMMU"
|
|
|
|
|
depends on FAULT_INJECTION
|
|
|
|
|
help
|
|
|
|
|
Provide fault-injection capability for IOMMU. Each device can
|
|
|
|
|
be selectively enabled via the fail_iommu property.
|
|
|
|
|
|
|
|
|
|
If you are unsure, say N.
|
|
|
|
|
|
2005-09-26 06:04:21 +00:00
|
|
|
endmenu
|
