User:ZyMOS/Howto configure the linux kernel/arch/powerpc

User:ZyMOS/Howto configure the linux kernel / arch / powerpc


 * For a description of the syntax of this configuration file,
 * see Documentation/kbuild/kconfig-language.txt.

"Linux/PowerPC Kernel Configuration"


 * Option: PPC64
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "64-bit kernel"
 * default n
 * This option selects whether a 32-bit or a 64-bit kernel will be built.


 * Option: PPC32
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y if !PPC64


 * Option: 64BIT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y if PPC64

_bool y
 * Option: PPC_MERGE
 * Kernel Versions: 2.6.15.6 ...


 * Option: MMU
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y


 * Option: UID16
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)


 * Option: GENERIC_HARDIRQS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y


 * Option: RWSEM_GENERIC_SPINLOCK
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)


 * Option: RWSEM_XCHGADD_ALGORITHM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y


 * Option: GENERIC_CALIBRATE_DELAY
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y


 * Option: PPC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y


 * Option: EARLY_PRINTK
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y if PPC64


 * Option: COMPAT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y if PPC64


 * Option: SYSVIPC_COMPAT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on COMPAT && SYSVIPC
 * default y


 * All PPC32s use generic nvram driver through ppc_md


 * Option: GENERIC_NVRAM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y if PPC32


 * Option: SCHED_NO_NO_OMIT_FRAME_POINTER
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y


 * Option: ARCH_MAY_HAVE_PC_FDC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y

Processor support
"Processor Type"
 * depends on PPC32
 * default 6xx


 * Option: 6xx
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "6xx/7xx/74xx"
 * select PPC_FPU
 * There are four families of PowerPC chips supported. The more common types (601, 603, 604, 740, 750, 7400), the Motorola embedded versions (821, 823, 850, 855, 860, 52xx, 82xx, 83xx), the AMCC embedded versions (403 and 405) and the high end 64 bit Power processors (POWER 3, POWER4, and IBM PPC970 also known as G5).  Unless you are building a kernel for one of the embedded processor systems, 64 bit IBM RS/6000 or an Apple G5, choose 6xx. Note that the kernel runs in 32-bit mode even on 64-bit chips.


 * Option: PPC_52xx
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Freescale 52xx"


 * Option: PPC_82xx
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Freescale 82xx"


 * Option: PPC_83xx
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Freescale 83xx"


 * Option: 40x
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "AMCC 40x"


 * Option: 44x
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "AMCC 44x"


 * Option: 8xx
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Freescale 8xx"


 * Option: E200
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Freescale e200"


 * Option: E500
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Freescale e500"


 * Option: POWER4_ONLY
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Optimize for POWER4"
 * depends on PPC64
 * default n
 * Cause the compiler to optimize for POWER4/POWER5/PPC970 processors. The resulting binary will not work on POWER3 or RS64 processors when compiled with binutils 2.15 or later.


 * Option: POWER3
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on PPC64
 * default y if !POWER4_ONLY

_bool y
 * Option: POWER4
 * Kernel Versions: 2.6.15.6 ...
 * depends on PPC64


 * Option: PPC_FPU
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y if PPC64


 * Option: BOOKE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on E200 || E500
 * default y


 * Option: FSL_BOOKE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on E200 || E500
 * default y


 * Option: PTE_64BIT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on 44x || E500
 * default y if 44x
 * default y if E500 && PHYS_64BIT


 * Option: PHYS_64BIT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) 'Large physical address support' if E500
 * depends on 44x || E500
 * default y if 44x
 * This option enables kernel support for larger than 32-bit physical addresses. This features is not be available on all e500 cores.
 * If in doubt, say N here.


 * Option: ALTIVEC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "AltiVec Support"
 * depends on 6xx || POWER4
 * 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.


 * Option: SPE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "SPE Support"
 * depends on E200 || E500
 * 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.


 * Option: PPC_STD_MMU
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on 6xx || POWER3 || POWER4 || PPC64
 * default y

_bool y
 * Option: PPC_STD_MMU_32
 * Kernel Versions: 2.6.15.6 ...
 * depends on PPC_STD_MMU && PPC32


 * Option: SMP
 * Kernel Versions: 2.6.15.6 ...
 * depends on PPC_STD_MMU
 * (on/off) "Symmetric multi-processing support"
 * 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.

"Maximum number of CPUs (2-128)" 2 128
 * Option: NR_CPUS
 * Kernel Versions: 2.6.15.6 ...
 * depends on SMP
 * default "32" if PPC64
 * default "4"


 * Option: NOT_COHERENT_CACHE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on 4xx || 8xx || E200
 * default y


 * Option: User:ZyMOS/Howto configure the linux kernel/init

Platform support

 * depends on PPC64 || 6xx

"Machine type"
 * default PPC_MULTIPLATFORM


 * Option: PPC_MULTIPLATFORM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Generic desktop/server/laptop"
 * Select this option if configuring for an IBM pSeries or RS/6000 machine, an Apple machine, or a PReP, CHRP, Maple or Cell-based machine.


 * Option: PPC_ISERIES
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "IBM Legacy iSeries"
 * depends on PPC64


 * Option: EMBEDDED6xx
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Embedded 6xx/7xx/7xxx-based board"
 * depends on PPC32 && BROKEN


 * Option: APUS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Amiga-APUS"
 * depends on PPC32 && BROKEN
 * Select APUS if configuring for a PowerUP Amiga. More information is available at: .


 * Option: PPC_PSERIES
 * Kernel Versions: 2.6.15.6 ...
 * depends on PPC_MULTIPLATFORM && PPC64
 * (on/off) "  IBM pSeries & new (POWER5-based) iSeries"
 * select PPC_I8259
 * select PPC_RTAS
 * select RTAS_ERROR_LOGGING
 * default y


 * Option: PPC_CHRP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "  Common Hardware Reference Platform (CHRP) based machines"
 * depends on PPC_MULTIPLATFORM && PPC32
 * select PPC_I8259
 * select PPC_INDIRECT_PCI
 * select PPC_RTAS
 * select PPC_MPC106
 * default y


 * Option: PPC_PMAC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "  Apple PowerMac based machines"
 * depends on PPC_MULTIPLATFORM
 * select PPC_INDIRECT_PCI if PPC32
 * select PPC_MPC106 if PPC32
 * default y


 * Option: PPC_PMAC64
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on PPC_PMAC && POWER4
 * select U3_DART
 * select GENERIC_TBSYNC
 * default y


 * Option: PPC_PREP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "  PowerPC Reference Platform (PReP) based machines"
 * depends on PPC_MULTIPLATFORM && PPC32 && BROKEN
 * select PPC_I8259
 * select PPC_INDIRECT_PCI
 * default y


 * Option: PPC_MAPLE
 * Kernel Versions: 2.6.15.6 ...
 * depends on PPC_MULTIPLATFORM && PPC64
 * (on/off) "  Maple 970FX Evaluation Board"
 * select U3_DART
 * select MPIC_BROKEN_U3
 * select GENERIC_TBSYNC
 * default n
 * This option enables support for the Maple 970FX Evaluation Board. For more informations, refer to 


 * Option: PPC_CELL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "  Cell Broadband Processor Architecture"
 * depends on PPC_MULTIPLATFORM && PPC64
 * select PPC_RTAS
 * select MMIO_NVRAM


 * Option: PPC_OF
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on PPC_MULTIPLATFORM# for now
 * default y


 * Option: XICS
 * Kernel Versions: 2.6.15.6 ...
 * depends on PPC_PSERIES
 * (on/off)
 * default y


 * Option: U3_DART
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on PPC_MULTIPLATFORM && PPC64
 * default n


 * Option: MPIC
 * Kernel Versions: 2.6.15.6 ...
 * depends on PPC_PSERIES || PPC_PMAC || PPC_MAPLE || PPC_CHRP
 * (on/off)
 * default y


 * Option: PPC_RTAS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default n


 * Option: RTAS_ERROR_LOGGING
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on PPC_RTAS
 * default n


 * Option: RTAS_PROC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Proc interface to RTAS"
 * depends on PPC_RTAS
 * default y


 * Option: RTAS_FLASH
 * Kernel Versions: 2.6.15.6 ...
 * (on/off/module) "Firmware flash interface"
 * depends on PPC64 && RTAS_PROC


 * Option: MMIO_NVRAM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default n


 * Option: MPIC_BROKEN_U3
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on PPC_MAPLE
 * default y


 * Option: CELL_IIC
 * Kernel Versions: 2.6.15.6 ...
 * depends on PPC_CELL
 * (on/off)
 * default y


 * Option: IBMVIO
 * Kernel Versions: 2.6.15.6 ...
 * depends on PPC_PSERIES || PPC_ISERIES
 * (on/off)
 * default y


 * Option: PPC_MPC106
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default n


 * Option: GENERIC_TBSYNC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y if CONFIG_PPC32 && CONFIG_SMP
 * default n


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/cpufreq


 * Option: CPU_FREQ_PMAC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Support for Apple PowerBooks"
 * depends on CPU_FREQ && ADB_PMU && PPC32
 * select CPU_FREQ_TABLE
 * This adds support for frequency switching on Apple PowerBooks, this currently includes some models of iBook & Titanium PowerBook.


 * Option: CPU_FREQ_PMAC64
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Support for some Apple G5s"
 * depends on CPU_FREQ && PMAC_SMU && PPC64
 * select CPU_FREQ_TABLE
 * This adds support for frequency switching on Apple iMac G5, and some of the more recent desktop G5 machines as well.


 * Option: PPC601_SYNC_FIX
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Workarounds for PPC601 bugs"
 * depends on 6xx && (PPC_PREP || PPC_PMAC)
 * Some versions of the PPC601 (the first PowerPC chip) have bugs which mean that extra synchronization instructions are required near certain instructions, typically those that make major changes to the CPU state. These extra instructions reduce performance slightly. If you say N here, these extra instructions will not be included, resulting in a kernel which will run faster but may not run at all on some systems with the PPC601 chip.
 * If in doubt, say Y here.


 * Option: TAU
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Thermal Management Support"
 * depends on 6xx
 * G3 and G4 processors have an on-chip temperature sensor called the 'Thermal Assist Unit (TAU)', which, in theory, can measure the on-die temperature within 2-4 degrees Celsius. This option shows the current on-die temperature in /proc/cpuinfo if the cpu supports it.
 * Unfortunately, on some chip revisions, this sensor is very inaccurate and in some cases, does not work at all, so don't assume the cpu temp is actually what /proc/cpuinfo says it is.


 * Option: TAU_INT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Interrupt driven TAU driver (DANGEROUS)"
 * depends on TAU
 * The TAU supports an interrupt driven mode which causes an interrupt whenever the temperature goes out of range. This is the fastest way to get notified the temp has exceeded a range. With this option off, a timer is used to re-check the temperature periodically.
 * However, on some cpus it appears that the TAU interrupt hardware is buggy and can cause a situation which would lead unexplained hard lockups.
 * Unless you are extending the TAU driver, or enjoy kernel/hardware debugging, leave this option off.


 * Option: TAU_AVERAGE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Average high and low temp"
 * depends on TAU
 * The TAU hardware can compare the temperature to an upper and lower bound. The default behavior is to show both the upper and lower bound in /proc/cpuinfo. If the range is large, the temperature is either changing a lot, or the TAU hardware is broken (likely on some G4's). If the range is small (around 4 degrees), the temperature is relatively stable.  If you say Y here, a single temperature value, halfway between the upper and lower bounds, will be reported in /proc/cpuinfo.
 * If in doubt, say N here.


 * Option: User:ZyMOS/Howto configure the linux kernel/arch/powerpc/platforms/embedded6xx


 * Option: User:ZyMOS/Howto configure the linux kernel/arch/powerpc/platforms/4xx


 * Option: User:ZyMOS/Howto configure the linux kernel/arch/powerpc/platforms/85xx


 * Option: User:ZyMOS/Howto configure the linux kernel/arch/powerpc/platforms/8xx

Kernel options

 * Option: HIGHMEM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "High memory support"
 * depends on PPC32


 * Option: User:ZyMOS/Howto configure the linux kernel/kernel.hz


 * Option: User:ZyMOS/Howto configure the linux kernel/kernel.preempt


 * Option: User:ZyMOS/Howto configure the linux kernel/fs.binfmt"


 * We optimistically allocate largepages from the VM, so make the limit
 * large enough (16MB). This badly named config option is actually
 * max order + 1


 * Option: FORCE_MAX_ZONEORDER
 * Kernel Versions: 2.6.15.6 ...


 * depends on PPC64
 * default "9" if PPC_64K_PAGES
 * default "13"


 * Option: MATH_EMULATION
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Math emulation"
 * depends on 4xx || 8xx || E200 || E500
 * Some PowerPC chips designed for embedded applications do not have a floating-point unit and therefore do not implement the floating-point instructions in the PowerPC instruction set. If you say Y here, the kernel will include code to emulate a floating-point unit, which will allow programs that use floating-point instructions to run.


 * Option: IOMMU_VMERGE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Enable IOMMU virtual merging (EXPERIMENTAL)"
 * depends on EXPERIMENTAL && PPC64
 * default n
 * Cause IO segments sent to a device for DMA to be merged virtually by the IOMMU when they happen to have been allocated contiguously. This doesn't add pressure to the IOMMU allocator. However, some drivers don't support getting large merged segments coming back from *_map_sg. Say Y if you know the drivers you are using are properly handling this case.


 * Option: HOTPLUG_CPU
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Support for enabling/disabling CPUs"
 * depends on SMP && HOTPLUG && EXPERIMENTAL && (PPC_PSERIES || PPC_PMAC)
 * Say Y here to be able to disable and re-enable individual CPUs at runtime on SMP machines.
 * Say N if you are unsure.


 * Option: KEXEC
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "kexec system call (EXPERIMENTAL)"
 * depends on PPC_MULTIPLATFORM && EXPERIMENTAL
 * kexec is a system call that implements the ability to shutdown your current kernel, and to start another kernel. It is like a reboot but it is indepedent of the system firmware.   And like a reboot you can start any kernel with it, not just Linux.
 * The name comes from the similiarity to the exec system call.
 * It is an ongoing process to be certain the hardware in a machine is properly shutdown, so do not be surprised if this code does not initially work for you. It may help to enable device hotplugging support.  As of this writing the exact hardware interface is strongly in flux, so no good recommendation can be made.


 * Option: EMBEDDEDBOOT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on 8xx || 8260
 * default y


 * Option: PC_KEYBOARD
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "PC PS/2 style Keyboard"
 * depends on 4xx || CPM2


 * Option: PPCBUG_NVRAM
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Enable reading PPCBUG NVRAM during boot" if PPLUS || LOPEC
 * default y if PPC_PREP


 * Option: IRQ_ALL_CPUS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Distribute interrupts on all CPUs by default"
 * depends on SMP && !MV64360
 * This option gives the kernel permission to distribute IRQs across multiple CPUs. Saying N here will route all IRQs to the first CPU.  Generally saying Y is safe, although some problems have been reported with SMP Power Macintoshes with this option enabled.


 * Option: User:ZyMOS/Howto configure the linux kernel/arch/powerpc/platforms/pseries


 * Option: NUMA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "NUMA support"
 * depends on PPC64
 * default y if SMP && PPC_PSERIES

_bool y
 * Option: ARCH_SELECT_MEMORY_MODEL
 * Kernel Versions: 2.6.15.6 ...
 * depends on PPC64


 * Option: ARCH_FLATMEM_ENABLE
 * Kernel Versions: 2.6.15.6 ...     def_bool y      depends on PPC64 && !NUMA

_bool y
 * Option: ARCH_SPARSEMEM_ENABLE
 * Kernel Versions: 2.6.15.6 ...

_bool y
 * Option: ARCH_SPARSEMEM_DEFAULT
 * Kernel Versions: 2.6.15.6 ...
 * depends on SMP && PPC_PSERIES


 * Option: User:ZyMOS/Howto configure the linux kernel/mm

_bool y
 * Option: HAVE_ARCH_EARLY_PFN_TO_NID
 * Kernel Versions: 2.6.15.6 ...
 * depends on NEED_MULTIPLE_NODES

_bool y
 * Option: ARCH_MEMORY_PROBE
 * Kernel Versions: 2.6.15.6 ...
 * depends on MEMORY_HOTPLUG


 * Option: PPC_64K_PAGES
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "64k page size"
 * depends on PPC64
 * This option changes the kernel logical page size to 64k. On machines        without processor support for 64k pages, the kernel will simulate         them by loading each individual 4k page on demand transparently,         while on hardware with such support, it will be used to map         normal application pages.


 * Option: SCHED_SMT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "SMT (Hyperthreading) scheduler support"
 * depends on PPC64 && SMP
 * default off
 * SMT scheduler support improves the CPU scheduler's decision making when dealing with POWER5 cpus at a cost of slightly increased overhead in some places. If unsure say N here.


 * Option: PROC_DEVICETREE
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Support for device tree in /proc"
 * depends on PROC_FS
 * This option adds a device-tree directory under /proc which contains an image of the device tree that the kernel copies from Open Firmware or other boot firmware. If unsure, say Y here.


 * Option: User:ZyMOS/Howto configure the linux kernel/arch/powerpc/platforms/prep


 * Option: CMDLINE_BOOL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Default bootloader kernel arguments"
 * depends on !PPC_ISERIES

"Initial kernel command string"
 * Option: CMDLINE
 * Kernel Versions: 2.6.15.6 ...
 * depends on CMDLINE_BOOL
 * default "console=ttyS0,9600 console=tty0 root=/dev/sda2"
 * On some platforms, there is currently no way for the boot loader to pass arguments to the kernel. For these platforms, you can supply some command-line options at build time by entering them here. In most cases you will need to specify the root device here.

!44x || BROKEN


 * Option: User:ZyMOS/Howto configure the linux kernel/kernel/power


 * Option: SECCOMP
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Enable seccomp to safely compute untrusted bytecode"
 * depends on PROC_FS
 * default y
 * This kernel feature is useful for number crunching applications that may need to compute untrusted bytecode during their execution. By using pipes or other transports made available to the process as file descriptors supporting the read/write syscalls, it's possible to isolate those applications in their own address space using seccomp. Once seccomp is enabled via /proc/ /seccomp, it cannot be disabled and the task is only allowed to execute a few safe syscalls defined by each seccomp mode.
 * If unsure, say Y. Only embedded should say N here.


 * Option: ISA_DMA_API
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y

Bus options

 * Option: ISA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Support for ISA-bus hardware"
 * depends on PPC_PREP || PPC_CHRP
 * select PPC_I8259
 * Find out whether you have ISA slots on your motherboard. ISA is the name of a bus system, i.e. the way the CPU talks to the other stuff inside your box.  If you have an Apple machine, say N here; if you have an IBM RS/6000 or pSeries machine or a PReP machine, say Y.  If you have an embedded board, consult your board documentation.


 * Option: GENERIC_ISA_DMA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on PPC64 || POWER4 || 6xx && !CPM2
 * default y


 * Option: PPC_I8259
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default y if 85xx
 * default n


 * Option: PPC_INDIRECT_PCI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on PCI
 * default y if 40x || 44x || 85xx || 83xx
 * default n


 * Option: EISA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)


 * Option: SBUS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)


 * Yes MCA RS/6000s exist but Linux-PPC does not currently support any


 * Option: MCA
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)


 * Option: PCI
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "PCI support" if 40x || CPM2 || 83xx || 85xx || PPC_MPC52xx || (EMBEDDED && PPC_ISERIES)
 * default y if !40x && !CPM2 && !8xx && !APUS && !83xx && !85xx
 * default PCI_PERMEDIA if !4xx && !CPM2 && !8xx && APUS
 * default PCI_QSPAN if !4xx && !CPM2 && 8xx
 * Find out whether your system includes a PCI bus. PCI is the name of a bus system, i.e. the way the CPU talks to the other stuff inside your box. If you say Y here, the kernel will include drivers and infrastructure code to support PCI bus devices.


 * Option: PCI_DOMAINS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * default PCI


 * Option: MPC83xx_PCI2
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "  Supprt for 2nd PCI host controller"
 * depends on PCI && MPC834x
 * default y if MPC834x_SYS


 * Option: PCI_QSPAN
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "QSpan PCI"
 * depends on !4xx && !CPM2 && 8xx
 * select PPC_I8259
 * Say Y here if you have a system based on a Motorola 8xx-series embedded processor with a QSPAN PCI interface, otherwise say N.


 * Option: PCI_8260
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on PCI && 8260
 * select PPC_INDIRECT_PCI
 * default y


 * Option: 8260_PCI9
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "  Enable workaround for MPC826x erratum PCI 9"
 * depends on PCI_8260 && !ADS8272
 * default y

" IDMA channel for PCI 9 workaround"
 * depends on 8260_PCI9


 * Option: 8260_PCI9_IDMA1
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "IDMA1"


 * Option: 8260_PCI9_IDMA2
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "IDMA2"


 * Option: 8260_PCI9_IDMA3
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "IDMA3"


 * Option: 8260_PCI9_IDMA4
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "IDMA4"


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/pci


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/pcmcia


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers/pci/hotplug

Advanced setup

 * depends on PPC32


 * Option: ADVANCED_OPTIONS
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Prompt for advanced kernel configuration options"
 * This option will enable prompting for a variety of advanced kernel configuration options. These options can cause the kernel to not work if they are set incorrectly, but can be used to optimize certain aspects of kernel memory management.
 * Unless you know what you are doing, say N here.

"Default settings for advanced configuration options are used"
 * depends on !ADVANCED_OPTIONS


 * Option: HIGHMEM_START_BOOL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Set high memory pool address"
 * depends on ADVANCED_OPTIONS && HIGHMEM
 * This option allows you to set the base address of the kernel virtual area used to map high memory pages. This can be useful in optimizing the layout of kernel virtual memory.
 * Say N here unless you know what you are doing.

"Virtual start address of high memory pool" if HIGHMEM_START_BOOL
 * Option: HIGHMEM_START
 * Kernel Versions: 2.6.15.6 ...
 * default "0xfe000000"


 * Option: LOWMEM_SIZE_BOOL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Set maximum low memory"
 * depends on ADVANCED_OPTIONS
 * This option allows you to set the maximum amount of memory which will be used as "low memory", that is, memory which the kernel can access directly, without having to set up a kernel virtual mapping. This can be useful in optimizing the layout of kernel virtual memory.
 * Say N here unless you know what you are doing.

"Maximum low memory size (in bytes)" if LOWMEM_SIZE_BOOL
 * Option: LOWMEM_SIZE
 * Kernel Versions: 2.6.15.6 ...
 * default "0x30000000"


 * Option: KERNEL_START_BOOL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Set custom kernel base address"
 * depends on ADVANCED_OPTIONS
 * This option allows you to set the kernel virtual address at which the kernel will map low memory (the kernel image will be linked at this address). This can be useful in optimizing the virtual memory layout of the system.
 * Say N here unless you know what you are doing.

"Virtual address of kernel base" if KERNEL_START_BOOL
 * Option: KERNEL_START
 * Kernel Versions: 2.6.15.6 ...
 * default "0xc0000000"


 * Option: TASK_SIZE_BOOL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Set custom user task size"
 * depends on ADVANCED_OPTIONS
 * This option allows you to set the amount of virtual address space allocated to user tasks. This can be useful in optimizing the virtual memory layout of the system.
 * Say N here unless you know what you are doing.

"Size of user task space" if TASK_SIZE_BOOL
 * Option: TASK_SIZE
 * Kernel Versions: 2.6.15.6 ...
 * default "0x80000000"


 * Option: CONSISTENT_START_BOOL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Set custom consistent memory pool address"
 * depends on ADVANCED_OPTIONS && NOT_COHERENT_CACHE
 * This option allows you to set the base virtual address of the the consistent memory pool. This pool of virtual memory is used to make consistent memory allocations.

"Base virtual address of consistent memory pool" if CONSISTENT_START_BOOL
 * Option: CONSISTENT_START
 * Kernel Versions: 2.6.15.6 ...
 * default "0xff100000" if NOT_COHERENT_CACHE


 * Option: CONSISTENT_SIZE_BOOL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Set custom consistent memory pool size"
 * depends on ADVANCED_OPTIONS && NOT_COHERENT_CACHE
 * This option allows you to set the size of the the consistent memory pool. This pool of virtual memory is used to make consistent memory allocations.

"Size of consistent memory pool" if CONSISTENT_SIZE_BOOL
 * Option: CONSISTENT_SIZE
 * Kernel Versions: 2.6.15.6 ...
 * default "0x00200000" if NOT_COHERENT_CACHE


 * Option: BOOT_LOAD_BOOL
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Set the boot link/load address"
 * depends on ADVANCED_OPTIONS && !PPC_MULTIPLATFORM
 * This option allows you to set the initial load address of the zImage or zImage.initrd file. This can be useful if you are on a board which has a small amount of memory.
 * Say N here unless you know what you are doing.

"Link/load address for booting" if BOOT_LOAD_BOOL
 * Option: BOOT_LOAD
 * Kernel Versions: 2.6.15.6 ...
 * default "0x00400000" if 40x || 8xx || 8260
 * default "0x01000000" if 44x
 * default "0x00800000"


 * Option: PIN_TLB
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Pinned Kernel TLBs (860 ONLY)"
 * depends on ADVANCED_OPTIONS && 8xx

PPC64


 * Option: KERNEL_START
 * Kernel Versions: 2.6.15.6 ...


 * default "0xc000000000000000"


 * Option: User:ZyMOS/Howto configure the linux kernel/net


 * Option: User:ZyMOS/Howto configure the linux kernel/drivers


 * Option: User:ZyMOS/Howto configure the linux kernel/fs


 * XXX source "arch/ppc/8xx_io]]


 * XXX source "arch/ppc/8260_io]]


 * Option: User:ZyMOS/Howto configure the linux kernel/arch/powerpc/platforms/iseries


 * Option: User:ZyMOS/Howto configure the linux kernel/lib

Instrumentation Support
depends on EXPERIMENTAL


 * Option: User:ZyMOS/Howto configure the linux kernel/arch/powerpc/oprofile


 * Option: KPROBES
 * Kernel Versions: 2.6.15.6 ...
 * (on/off) "Kprobes (EXPERIMENTAL)"
 * depends on PPC64
 * Kprobes allows you to trap at almost any kernel address and execute a callback function. register_kprobe establishes a probepoint and specifies the callback.  Kprobes is useful for kernel debugging, non-intrusive instrumentation and testing. If in doubt, say "N".


 * Option: User:ZyMOS/Howto configure the linux kernel/arch/powerpc.debug"


 * Option: User:ZyMOS/Howto configure the linux kernel/security


 * Option: KEYS_COMPAT
 * Kernel Versions: 2.6.15.6 ...
 * (on/off)
 * depends on COMPAT && KEYS
 * default y


 * Option: User:ZyMOS/Howto configure the linux kernel/crypto