--- zzzz-none-000/linux-2.4.17/Documentation/Configure.help 2001-12-21 17:41:53.000000000 +0000 +++ sangam-fb-322/linux-2.4.17/Documentation/Configure.help 2004-11-24 13:22:33.000000000 +0000 @@ -112,6 +112,15 @@ like MGA monitors that you are very unlikely to see on today's systems. +Prompt for advanced kernel configuration options +CONFIG_ADVANCED_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 you *should not* enable this option. + Symmetric Multi-Processing support CONFIG_SMP This enables support for systems with more than one CPU. If you have @@ -266,6 +275,63 @@ If you have a system with several CPUs, you do not need to say Y here: the local APIC will be used automatically. +Interrupt Latency Instrumentation +CONFIG_ILATENCY + This option turns on instrumentation in the kernel to measure the interrupt + overhead and interrupt hold off times of the kernel and driver set for + a particular system. The measurement provides interrupt latency data + to gain an understanding of what interrupt latencies look like for that + system. + + The data is collected in /proc/ilatcurve, outlier data, or the maximum + interrupt off offenders are collected in /proc/imaxoff. This file has + the longest interrupt off times and the file and line number of the + interrupt off/on pair. This file is useful for finding and debugging + drivers that have poor interrupt latencies. + + Interrupt Latency Instrumentation should NOT be used in production systems. + It has a failry large overhead to measure and collect the data. It also + should not be used with kernel Preemption. + + Say Y to this option if you are trying to understand the interrupt latency + curve of your board. This should be only used in the design and debug + phase of your product. + +Preemptible Kernel +CONFIG_PREEMPT + This option reduces the latency of the kernel when reacting to + real-time or interactive events by allowing a low priority process to + be preempted even if it is in kernel mode executing a system call. + This allows applications to run more reliably even when the system is + under load due to other, lower priority, processes. + + Say Y here if you are building a kernel for a desktop system, embedded + system or real-time system. Say N if you are building a kernel for a + system where throughput is more important than interactive response, + such as a server system. Say N if you are unsure. + +Break Selected Locks +CONFIG_LOCK_BREAK + This option will break certain locks in high-latency regions + throughout the kernel. It is intended for use in conjunction with + the preemptible kernel (CONFIG_PREEMPT). Since in-kernel preemption + can not occur while locks are held, temporarily releasing and then + reacquiring long-held locks will further improve system response. + + Say Y if you are compiling for a system with strict latency + requirements such as an embedded, real-time, or audio processing + system. Say N otherwise. + +Collect preemption latency times +CONFIG_PREEMPT_TIMES + This option will instruct the preemption code to measure in-kernel + latencies due to various locking primitives. The results for the 20 + worst latency times are accessible via /proc/latencytimes. They are + reset on read. + + Say Y here if you are testing kernel preemption and trying to determine + where high-latency problems lie. Say N if you are unsure. + Kernel math emulation CONFIG_MATH_EMULATION Linux can emulate a math coprocessor (used for floating point @@ -290,6 +356,48 @@ If you are not sure, say Y; apart from resulting in a 66 KB bigger kernel, it won't hurt. +Turn OOM Killer on +CONFIG_OOM_KILLER + + This option turns on the out_of_memory killer. In 2.4 Linux introduced + the out of memory killer as a last resort to being out of memory + and being unable to reclaim any via swapping. This feature causes + problems in small memory, embedded systems that have no swap devices. + + The OOM killer is turned off by default in MVL2.1. + The killer logs the application pid and name in the message buffer with + the following message: + + Out of Memory: Killed process PID no (Process name). + + This option disables the out_of_memory killer and allows small memory + embedded systems, that don't completely exhaust physical memory, to + keep their applications running indefinitely. If all of physical + memory is completely consumed the system will most likely hang, unless + something can run to completion, exit and return memory to the system. + +Real Time Scheduler +CONFIG_RTSCHED + + This option replaces the standard linux scheduler with a real time + scheduler. The real time scheduler provides load independent fast + context switch times for real time tasks where as the standard linux + scheduler slows down with increasing load (i.e. more tasks ready to + run). For non-real time tasks both schedulers context switch times are + load dependent. The real time scheduler also provides a configure + option for real time priorities ranging from 1 to a max of 2047 while + the standard schedulers real time priorities range from 1-99. + Real time tasks are tasks that have a scheduling policy of SCHED_FIFO + or SCHED_RR. Scheduling policy is set by the sched_setscheduler(2) + system call and is inherited thru fork and thread creation. + +Maximum Priority? +CONFIG_MAX_PRI + This option lets you set the number of priorities available to real time + tasks. Priorities 1 thru maximum priority are real time tasks. The + default here is 127. The system will quietly change any thing less than + 99 to 99 and any thing greater than 2047 to 2047. + Timer and CPU usage LEDs CONFIG_LEDS If you say Y here, the LEDs on your machine will be used @@ -3600,6 +3708,11 @@ "Bridge" is the name used for the hardware inside your computer that PCMCIA cards are plugged into. If unsure, say N. +MPC8xx PCMCIA support +CONFIG_PCMCIA_M8XX + Say Y here to include support for the PCMCIA controller in MPC8xx + processors. + System V IPC CONFIG_SYSVIPC Inter Process Communication is a suite of library functions and @@ -3938,6 +4051,13 @@ Say Y to enable support for Permedia2 AGP frame buffer card from 3Dlabs (aka `Graphic Blaster Exxtreme') on the PCI bus. +Permedia3 support (EXPERIMENTAL) +CONFIG_FB_PM3 + This is the frame buffer device driver for the 3DLabs Permedia3 + chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 & + similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000 + and maybe other boards. + Phase5 CVisionPPC/BVisionPPC support CONFIG_FB_PM2_CVPPC Say Y to enable support for the Amiga Phase 5 CVisionPPC BVisionPPC @@ -4048,6 +4168,26 @@ CONFIG_FB_S3TRIO If you have a S3 Trio say Y. Say N for S3 Virge. +RPX LCD display support +CONFIG_FB_RPX + This driver supports the PowerPC MPC823's on-chip LCD controller. If + you have an MPC823 (such as is present in the Embedded Planet RPX + Lite boards), say Y. + + The driver is also available as a module ( = code which can be + inserted and removed from the running kernel whenever you want). The + module will be called rpxfb.o. If you want to compile it as a + module, say M here and read . + + If unsure, say N. + +Debug RPX frame buffer +CONFIG_FB_RPX_DEBUG + If you want the RPX frame buffer driver to display debugging + information, say Y. + + If unsure, say N. + 3Dfx Banshee/Voodoo3 display support CONFIG_FB_3DFX This driver supports graphics boards with the 3Dfx Banshee/Voodoo3 @@ -6429,7 +6569,7 @@ CONFIG_PPPOATM Support PPP (Point to Point Protocol) encapsulated in ATM frames. This implementation does not yet comply with section 8 of RFC2364, - which can lead to bad results idf the ATM peer loses state and + which can lead to bad results if the ATM peer loses state and changes its encapsulation unilaterally. Fusion MPT device support @@ -8650,6 +8790,17 @@ to compile it as a module and remove the module after configuration. +Cisco/Aironet 340/350/4500/4800 +CONFIG_AIRO + Provides support for ISA/PCI/PCMCIA 802.11b ethernet cards from + Cisco. Before being acquired by Cisco they were Aironet cards. + Supports wireless extensions. + +Cisco/Aironet 340/350/4500/4800 PCMCIA Card Service +CONFIG_AIRO_CS + Provides support for PCMCIA 802.11b ethernet cards. This is just + glue to the core airo driver. + LAPB over Ethernet driver CONFIG_LAPBETHER This is a driver for a pseudo device (typically called /dev/lapb0) @@ -8748,6 +8899,19 @@ a module, say M here and read . If unsure, say N. +Asix AX88190 PCMCIA support +CONFIG_PCMCIA_AXNET + Say Y here if you intend to attach an Asix AX88190-based PCMCIA + (PC-card) Fast Ethernet card to your computer. These cards are + nearly NE2000 compatible but need a separate driver due to a few + misfeatures. + + This driver is also available as a module ( = code which can be + inserted in and removed from the running kernel whenever you want). + The module will be called axnet_cs.o. If you want to compile it as + a module, say M here and read . If + unsure, say N. + New Media PCMCIA support CONFIG_PCMCIA_NMCLAN Say Y here if you intend to attach a New Media Ethernet or LiveWire @@ -9279,7 +9443,7 @@ whenever you want). If you want to compile it as a module, say M here and read . -CSZ packet scheduler +CSZ packet scheduler (experimental) CONFIG_NET_SCH_CSZ Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet scheduling algorithm for some of your network devices. At the @@ -10180,6 +10344,12 @@ instead of an internal one. Disabling this option will save some memory by making the code size smaller. If unsure, say Y. +Support for Dreamcast Broad Band Adaptor +CONFIG_8139TOO_DREAMCAST + This enables support for the SEGA Broad Band Adaptor for Dreamcast. + It uses 16KB buffer and doesn't support mapping main memory to DMA. + If unsure, say N. + SiS 900/7016 PCI Fast Ethernet Adapter support CONFIG_SIS900 This is a driver for the Fast Ethernet PCI network cards based on @@ -10347,6 +10517,20 @@ is a 10Mbit/sec Ethernet controller. Product overview and specs at . +CPU Cache and PCI Bus Coherency +CONFIG_SH_PCIDMA_NONCOHERENT + This option indicates that the use of external PCI mastering devices + requires software to ensure consistency between PCI-visible memory + (on the bus) and CPU-visible memory (which may be in cache). If you + answer Y, kernel functions pci_{map,dma_sync}_{single,sg} will flush + the writeback cache as necessary to provide consistency; otherwise + they take no action (other than checking the direction argument.) + + If your hardware ensures coherency or has no external PCI master + devices, or you know that your drivers have other means of ensuring + consistency, you can answer N to avoid the overhead of unnecessary + cache flushing. Otherwise, it is safest to answer Y. + If unsure, say N. 3COM cards @@ -11316,6 +11500,17 @@ The module will be called tmspci.o. If you want to compile it as a module, say M here and read . +Altera ether00 support +CONFIG_ETHER00 + This is the driver for Altera's ether00 ethernet mac IP core. Say + Y here if you want to build support for this into the kernel. It + is also available as a module (say M here) that can be inserted/ + removed from the kernel at the same time as the PLD is configured. + If this driver is running on an epxa10 development board then it + will generate a suitable hw address based on the board serial + number (MTD support is required for this). Otherwise you will + need to set a suitable hw address using ifconfig. + Generic TMS380 ISA support CONFIG_TMSISA This tms380 module supports generic TMS380-based ISA cards. @@ -11348,6 +11543,7 @@ The module will be called madgemc.o. If you want to compile it as a module, say M here and read . + SMC ISA/MCA Token Ring adapter support CONFIG_SMCTR This is support for the ISA and MCA SMC Token Ring cards, @@ -12010,6 +12206,11 @@ If you wish to support CFI devices on a physical bus which is 32 bits wide, say 'Y'. +Support 64-bit buswidth +CONFIG_MTD_CFI_B8 + If you wish to support CFI devices on a physical bus which is + 64 bits wide, say 'Y'. + Support 1-chip flash interleave CONFIG_MTD_CFI_I1 If your flash chips are not interleaved - i.e. you only have one @@ -12269,6 +12470,17 @@ you probably want to enable this mapping driver. More info is at . +Flash chip mapping on Motorola Falcon/Hawk-based PowerPlus boards +CONFIG_MTD_POWERPLUS + This is a mapping driver for Motorola Computer Group + Falcon/Hawk-based PowerPlus boards. It detects the size of Flash + bank A and divides it into 2 equal MTD partitions. Flash Bank B + (1MB) is ignored in order to preserve the PPCBUG firmware. + + If the 'Specific CFI Flash geometry selection' option is selected, + then it is necessary to enable the 'Support 64-bit buswidth' and + 'Support 4-chip flash interleave' options for this mapping to work. + JEDEC Flash device mapped on Octagon 5066 SBC CONFIG_MTD_OCTAGON This provides a 'mapping' driver which supports the way in which @@ -12283,6 +12495,25 @@ Board Computer. More information on the board is available at . +Flash mapped as on Hitachi SuperH Solution Engine +CONFIG_MTD_SOLUTIONENGINE + Provides a mapping driver for FLASH and PROM on the Solution Engine + and similar boards. Assumes 4M FLASH and PROM at 0x00000000 and + 0x010000000, or vice versa based on probing. Will look for RedBoot + partition table if CONFIG_MTD_REDBOOT_PARTS is on (non-modular); + else (or if no table is found) will partition a FLASH into read-only + and writable portions based on CONFIG_MTD_SUPERH_RESERVE. + +Size of read-only FLASH partition +CONFIG_MTD_SUPERH_RESERVE + Specifies the (hex) size of an initial portion of flash, mapped into + a separate read-only partition. Used if CONFIG_MTD_REDBOOT_PARTS is + not configured, or if a RedBoot partition table is not found. To + get a single writable partition for all flash, specify 0. + + May leave a gap between the read-only and writable partitions due to + alignment constraints on writable partitions. + Support for NAND flash devices CONFIG_MTD_NAND This enables support for accessing all type of NAND flash @@ -12449,7 +12680,7 @@ CFI Flash device mapping on the Flaga Digital Module CONFIG_MTD_CFI_FLAGADM - Mapping for the Flaga digital module. If you don´t have one, ignore + Mapping for the Flaga digital module. If you don³t have one, ignore this setting. Momenco Ocelot boot flash device @@ -12886,6 +13117,16 @@ support" be compiled as a module for this driver to be used properly. +Altera's uart00 serial driver +CONFIG_SERIAL_UART00 + Say Y here if you want to use the hard logic uart on Excalibur. This + driver also supports soft logic implentations of this uart core. + +Serial console on uart00 +CONFIG_SERIAL_UART00_CONSOLE + Say Y here if you want to support a serial console on an Excalibur + hard logic uart or uart00 IP core. + USB ConnectTech WhiteHEAT Serial Driver CONFIG_USB_SERIAL_WHITEHEAT Say Y here if you want to use a ConnectTech WhiteHEAT 4 port @@ -13489,6 +13730,16 @@ The module will be called dsbr100.o. If you want to compile it as a module, say M here and read . +MPC850/823 USB HCI support +CONFIG_USB_MPC8xx + Say Y here to include a driver for the MPC850/MPC823 CPM USB device + operating as a Host Controller Interface. + +MPC850/823 USB Function (Client) support +CONFIG_USB_CLIENT_MPC8xx + Say Y here to include a driver for the MPC850/MPC823 CPM USB device + operating as a USB client. + Always do synchronous disk IO for UBD CONFIG_BLK_DEV_UBD_SYNC The User-Mode Linux port includes a driver called UBD which will let @@ -15531,32 +15782,66 @@ Use MDIO for PHY configuration CONFIG_USE_MDIO - On some boards the hardware configuration of the ethernet PHY can be - used without any software interaction over the MDIO interface, so - all MII code can be omitted. Say N here if unsure or if you don't - need link status reports. + The MDIO interface is used to communicate with the external PHY + attached to the MPC8xx Fast Ethernet Controller. MDIO + communication is required for reliable Ethernet operation, but + some configurations may work without it. -860T FEC Ethernet -CONFIG_FEC_ENET - Enable Ethernet support via the Fast Ethernet Controller (FCC) on - the Motorola MPC8260. + If unsure, say Y. -Ethernet on FCC1 -CONFIG_FCC1_ENET - Use MPC8260 fast Ethernet controller 1 to drive Ethernet (default). +LXT970 PHY Support +CONFIG_FEC_LXT970 + Include support in the MPC8xx Fast Ethernet driver for the + Level One LXT970 PHY. -Ethernet on FCC2 -CONFIG_FCC2_ENET - Use MPC8260 fast Ethernet controller 2 to drive Ethernet. + If unsure, say Y. -Ethernet on FCC3 -CONFIG_FCC3_ENET - Use MPC8260 fast Ethernet controller 3 to drive Ethernet. +LXT971/LXT972 PHY Support +CONFIG_FEC_LXT971 + Include support in the MPC8xx Fast Ethernet driver for the + Level One LXT971/LXT972 PHY. + + If unsure, say Y. + +QS6612 PHY Support +CONFIG_FEC_QS6612 + Include support in the MPC8xx Fast Ethernet driver for the + Quality Semiconductor QS6612 PHY. + + If unsure, say Y. + +AM79C874 PHY Support +CONFIG_FEC_AM79C874 + Include support in the MPC8xx Fast Ethernet driver for the + AMD AM79C874 PHY. + + If unsure, say Y. + +BCM5221 PHY Support +CONFIG_FEC_BCM5221 + Include support in the MPC8xx Fast Ethernet driver for the + Broadcom BCM5221 PHY. + + If unsure, say Y. + +Generic PHY Support +CONFIG_FEC_GENERIC_PHY + Include support in the MPC8xx Fast Ethernet driver for a generic + PHY. If enabled, the generic PHY support will only be used as a + fallback in case the driver does not have specific support for the + particular PHY chip detected. + + If unsure, say Y. + +860T FEC Ethernet +CONFIG_FEC_ENET + Enable Ethernet support via the Fast Ethernet Controller (FEC) on + the Motorola MPC8xx processor. CPM SCC Ethernet CONFIG_SCC_ENET Enable Ethernet support via the Motorola MPC8xx serial - commmunications controller. + communications controller. # Choice: scc_ethernet Ethernet on SCC1 @@ -15574,8 +15859,86 @@ Use Big CPM Ethernet Buffers CONFIG_ENET_BIG_BUFFERS - Allocate large buffers for MPC8xx Etherenet. Increases throughput - and decreases the likelihood of dropped packets, but costs memory. + Allocate extra buffer descriptors for MPC8xx Ethernet. This option + applies to both SCC and FEC Ethernet. This may increase throughput, + but costs memory. + + If unsure, say N. + +Use MDIO for PHY configuration +CONFIG_FCC_USE_MDIO + The MDIO interface is used to communicate with the external PHY + attached to the MPC8260 Fast Communication Controller when used for + Ethernet. MDIO communication is required for reliable Ethernet + operation, but some configurations may work without it. + + If unsure, say Y. + +LXT970 PHY Support +CONFIG_FCC_LXT970 + Include support in the MPC8260 Fast Ethernet driver for the + Level One LXT970 PHY. + + If unsure, say Y. + +LXT971/LXT972 PHY Support +CONFIG_FCC_LXT971 + Include support in the MPC8260 Fast Ethernet driver for the + Level One LXT971/LXT972 PHY. + + If unsure, say Y. + +QS6612 PHY Support +CONFIG_FCC_QS6612 + Include support in the MPC8260 Fast Ethernet driver for the + Quality Semiconductor QS6612 PHY. + + If unsure, say Y. + +AM79C874 PHY Support +CONFIG_FCC_AM79C874 + Include support in the MPC8260 Fast Ethernet driver for the + AMD AM79C874 PHY. + + If unsure, say Y. + +BCM5221 PHY Support +CONFIG_FCC_BCM5221 + Include support in the MPC8260 Fast Ethernet driver for the + Broadcom BCM5221 PHY. + + If unsure, say Y. + +Generic PHY Support +CONFIG_FCC_GENERIC_PHY + Include support in the MPC8260 Fast Ethernet driver for a generic + PHY. If enabled, the generic PHY support will only be used as a + fallback in case the driver does not have specific support for the + particular PHY chip detected. + + If unsure, say Y. + +MPC8260 SCC Ethernet +CONFIG_8260_SCC_ENET + Enable Ethernet support via the Motorola MPC8260 Serial + Communications Controller. + +MPC8260 FCC Ethernet +CONFIG_FCC_ENET + Enable Ethernet support via a Fast Communication Controller (FCC) on + the Motorola MPC8260 processor. + +Ethernet on FCC1 +CONFIG_FCC1_ENET + Use MPC8260 Fast Communication Controller 1 to drive Ethernet. + +Ethernet on FCC2 +CONFIG_FCC2_ENET + Use MPC8260 Fast Communication Controller 2 to drive Ethernet. + +Ethernet on FCC3 +CONFIG_FCC3_ENET + Use MPC8260 Fast Communication Controller 3 to drive Ethernet. Apple Desktop Bus (ADB) support CONFIG_ADB @@ -15596,13 +15959,10 @@ Support for PMU-based PowerMacs CONFIG_ADB_PMU - On the PowerBook 3400 and 2400, the PMU is a 6805 microprocessor - core whose primary function is to control battery charging and - system power. The PMU also controls the ADB (Apple Desktop Bus) - which connects to the keyboard and mouse, as well as the - non-volatile RAM and the RTC (real time clock) chip. Say Y to - enable support for this device; you should do so if your machine - is one of these PowerBooks. + This provides support for PMU based Power Macintosh systems. This + includes all PowerBooks and all AGP-based machines. + + If unsure say Y. Include MacIO ADB driver CONFIG_ADB_MACIO @@ -15780,6 +16140,15 @@ If unsure, say N. +Use a non standard baud rate on serial console +CONFIG_SERIAL_CONSOLE_NONSTD + By default the serial console code assumes that all of the registers + for setting up the baud rate are set. In some cases, such as the IBM + Spruce boards, this is not the case. If you answer Y here, you can fill + in the desired baud rate to use at console (eg 9600). + + If unsure, say N. + Support for PowerMac serial ports CONFIG_MAC_SERIAL If you have Macintosh style serial ports (8 pin mini-DIN), say Y @@ -16225,6 +16594,24 @@ If you have a Cobalt Networks system, you should say Y here, unless you are absolutely sure. +UltraSPARC-III bootbus i2c controller driver +CONFIG_BBC_I2C + The BBC devices on the UltraSPARC III have two I2C controllers. The + first I2C controller connects mainly to configuration PROMs (NVRAM, + CPU configuration, DIMM types, etc.). The second I2C controller + connects to environmental control devices such as fans and + temperature sensors. The second controller also connects to the + smartcard reader, if present. Say Y to enable support for these. + +I2C /proc support +CONFIG_I2C_PROC + This provides support for i2c device entries in the /proc filesystem. + The entries will be found in /proc/sys/dev/sensors. + + This code is also available as a module. If you want to compile + it as a module, say M here and read . + The module will be called i2c-proc.o. + I2C support CONFIG_I2C I2C (pronounce: I-square-C) is a slow serial bus protocol used in @@ -16249,15 +16636,6 @@ . The module will be called i2c-core.o. -UltraSPARC-III bootbus i2c controller driver -CONFIG_BBC_I2C - The BBC devices on the UltraSPARC III have two I2C controllers. The - first I2C controller connects mainly to configuration PROMs (NVRAM, - CPU configuration, DIMM types, etc.). The second I2C controller - connects to environmental control devices such as fans and - temperature sensors. The second controller also connects to the - smartcard reader, if present. Say Y to enable support for these. - I2C bit-banging interfaces CONFIG_I2C_ALGOBIT This allows you to use a range of I2C adapters called bit-banging @@ -16344,6 +16722,15 @@ it as a module, say M here and read . The module will be called i2c-proc.o. +MPC8xx CPM I2C Interface +CONFIG_I2C_ALGO8XX + Say Y here to include a driver for the I2C device in the MPC8xx CPM. + +MPC8260 CPM I2C Interface +CONFIG_I2C_ALGO8260 + Say Y here to include a driver for the I2C device in the MPC8260 + CPM. + Bus Mouse Support CONFIG_BUSMOUSE Say Y here if your machine has a bus mouse as opposed to a serial @@ -16480,6 +16867,12 @@ If you are unsure, say N and read the HOWTO nevertheless: it will tell you what you have. +Redwood IR mouse support +CONFIG_RWMOUSE + Enable this if you are using the IR device on either + the redwood 4 or redwood 5 IBM PPC4xx evaluation board + and want mouse support. The module is called rw4mouse.o + QIC-02 tape support CONFIG_QIC02_TAPE If you have a non-SCSI tape drive like that, say Y. Or, if you want @@ -17348,6 +17741,17 @@ . The module will be called softdog.o. +SA1100 Internal Watchdog +CONFIG_SA1100_WATCHDOG + Watchdog timer embedded into SA11x0 chips. This will reboot your + system when timeout is reached. + NOTE, that once enabled, this timer cannot be disabled. + + This driver is also available as a module ( = code which can be + inserted in and removed from the running kernel whenever you want). + If you want to compile it as a module, say M here and read + Documentation/modules.txt. The module will be called sa1100_wdt.o. + Berkshire Products PC Watchdog CONFIG_PCWATCHDOG This is the driver for the Berkshire Products PC Watchdog card. @@ -18802,6 +19206,30 @@ Say Y or M if you have a Hammerfall, Hammerfall light or Hammerfall DSP card from RME. +Assabet audio (UDA1341) support +CONFIG_SOUND_ASSABET_UDA1341 + Say Y or M if you have an Intel Assabet evaluation board and want to + use the Philips UDA 1341 audio chip (the one that drives the stereo + audio output) on the SA1100 SSP port. + +Compaq iPAQ audio support +CONFIG_SOUND_H3600_UDA1341 + Say Y or M if you have a Compaq iPaq handheld computer and want to + use its Philips UDA 1341 audio chip. + +Audio support for SA1111/UDA1341 +CONFIG_SOUND_SA1111_UDA1341 + Say Y or M if you have an SA11x0 system with a Philips UDA 1341 + connected to the SA11x1. An example of such a system is the Intel + Assabet evaluation board connected to a Neponset expansion board. + +Generic DAC on the SA11x0 SSP port +CONFIG_SOUND_SA1100SSP + Say Y or M if you have an SA-11x0 system with a DAC on the SSP port. + The LART has an Burr-Brown PCM 1710 digital to analog convertor on + the SSP port, so you want to say Y or M for the LART. It might work + on other SA-1100 platforms, too, but this is not tested. + Are you using a crosscompiler CONFIG_CROSSCOMPILE Say Y here if you are compiling the kernel on a different @@ -18935,6 +19363,90 @@ keys are documented in . Don't say Y unless you really know what this hack does. +Include kgdb kernel debugger +CONFIG_KGDB + If you say Y here, the system will be compiled with the debug option + (-g) and a debugging stub will be included in the kernel. This stub + communicates with gdb on another (host) computer via a serial port. + The host computer should have access to the kernel binary file + (vmlinux) and a serial port that is connected to the target machine. + Gdb can be made to configure the serial port or you can use stty and + setserial to do this. See the 'target' command in gdb. This option also + configures in the ability to request a breakpoint early in + the boot process. To request the breakpoint just include 'kgdb' as a + boot option when booting the target machine. The system will then + break as soon as it looks at the boot options. This option also + installs a breakpoint in panic and sends any kernel faults to the + debugger. For more information see the Documentation/i386/kgdb.txt file. + + +Debug serial port BAUD +CONFIG_KGDB_9600BAUD + Gdb and the kernel stub need to agree on the baud rate to be used. + Some systems (x86 family at this writing) allow this to be configured. + +hex I/O port address of the debug serial port +CONFIG_KGDB_PORT + Some systems (x86 family at this writing) allow the port address to be + configured. The number entered is assumed to be hex, don't put 0x in + front of it. The standard address are: COM1 3f8 , irq 4 and + COM2 2f8 irq 3. Setserial /dev/ttySx will tell you what you have. + It is good to test the serial connection with a live system before trying + to debug. + +Kgdb event macros +CONFIG_KGDB_TS + Kgdb event macros allow you to instrument your code with calls to the + kgdb event recording function. The event log may be examined with gdb + at a break point. Turning on this capability also allows you to choose + how many events to keep. Kgdb always keeps the lastest events. + +Stack overflow test (part of kgdb option) +CONFIG_STACK_OVERFLOW_TEST + This option enables code in the front line interrupt handlers to check + for kernel stack overflow on interrupts and system calls. This is part + of the kgdb code on x86 systems. + + +IRQ of the debug serial port +CONFIG_KGDB_IRQ + This is the irq for the debug port. If everything is working correctly + and the kernel has interrupts on a control C to the port should cause a + break into the kernel debug stub. + +Enable compile options +CONFIG_KGDB_MORE + Saying yes here turns on the ability to enter additional compile options. + +Additional compile options +CONFIG_KGDB_OPTIONS + This option allows you enter additional compile options for the whole + kernel compile. Each platform will have a default that seems right + for it. For example on PPC "-ggdb -O1", and for i386 "-O1". Note that + by configuring KGDB "-g" is already turned on. In addition, on i386 + and SH platforms "-fomit-frame-pointer" is deleted from the standard + compile options. + +SysRq Gdb command +CONFIG_KGDB_SYSRQ + This option includes an option in the SysRq code that allows you to enter + SysRq G which generates a breakpoint to the KGDB stub. This will work if + the keyboard is alive and can interrupt the system. Because of constraints + on when the serial port interrupt can be enabled, this code may allow you + to interrupt the system before the serial port control C is available. + Just say yes here. + +KGDB console +CONFIG_KGDB_CONSOLE + This option enables the command line "console=kgdb" option. When the + system is booted with this option in the command line all kernel printk + output is sent to gdb (as well as to other consoles). For this to work + gdb must be connected. For this reason, this command line option will + generate a breakpoint if gdb has not yet connected. After the gdb + continue command is given all pent up console output will be printed + by gdb on the host machine. Neither this option, nor KGDB require the + serial driver to be configured. + ISDN support CONFIG_ISDN ISDN ("Integrated Services Digital Networks", called RNIS in France) @@ -19794,6 +20306,44 @@ "Area6" will work for most boards. For ADX, select "Area5". +Kernel events tracing support +CONFIG_TRACE + It is possible for the kernel to log important events to a tracing + driver. Doing so, enables the use of the generated traces in order + to reconstruct the dynamic behavior of the kernel, and hence the + whole system. + + The tracing process contains 4 parts : + 1) The logging of events by key parts of the kernel. + 2) The trace driver that keeps the events in a data buffer. + 3) A trace daemon that opens the trace driver and is notified + every time there is a certain quantity of data to read + from the trace driver (using SIG_IO). + 4) A trace event data decoder that reads the accumulated data + and formats it in a human-readable format. + + If you say Y or M here, the first part of the tracing process will + always take place. That is, critical parts of the kernel will call + upon the kernel tracing function. The data generated doesn't go + any further until a trace driver registers himself as such with the + kernel. Therefore, if you answer Y, then the driver will be part of + the kernel and the events will always proceed onto the driver and + if you say M, then the events will only proceed onto the driver when + it's module is loaded. Note that event's aren't logged in the driver + until the profiling daemon opens the device, configures it and + issues the "start" command through ioctl(). + + The impact of a fully functionnal system (kernel event logging + + driver event copying + active trace daemon) is of 2.5% for core events. + This means that for a task that took 100 seconds on a normal system, it + will take 102.5 seconds on a traced system. This is very low compared + to other profiling or tracing methods. + + For more information on kernel tracing, the trace daemon or the event + decoder, please check the following address : + http://www.opersys.com/LTT + + # # m68k-specific kernel options # Documented by Chris Lawrence et al. @@ -20409,7 +20959,7 @@ . PowerMac DMA sound support -CONFIG_DMASOUND_AWACS +CONFIG_DMASOUND_PMAC If you want to use the internal audio of your PowerMac in Linux, answer Y to this question. This will provide a Sun-like /dev/audio, compatible with the Linux/i386 sound system. Otherwise, say N. @@ -20522,7 +21072,7 @@ Reference" on Motorola's website. This option also incurs a performance hit. - If in doubt, say N here. + If in doubt, say Y here. MPC8xx direct IDE support on PCMCIA port CONFIG_BLK_DEV_MPC8xx_IDE @@ -20569,10 +21119,24 @@ Enable SCC2 and SCC3 for UART CONFIG_USE_SCC_IO If your MPC8xx board has other SCC ports that you would like to use - for for a serial port, say Y here. + for a serial port, say Y here. If in doubt, say N here. +Embedded Planet HIOX Audio +CONFIG_HTDMSOUND + Say Y here to include a driver for the audio device on an Embedded + Planet HIOX board. + +Embedded Planet HIOX Touch Panel +CONFIG_RPXTOUCH + Say Y here to include a driver for the touch panel interface on an + Embedded Planet HIOX board. + +Enable SCC Console +CONFIG_8260_SCC_CONSOLE + Say Y here to use SCC1 as the serial console instead of SMC1. + # Choice: ppc6xxtype Machine Type CONFIG_ALL_PPC @@ -20606,6 +21170,155 @@ More information is available at: . +IBM Spruce Baud Clock Support +CONFIG_SPRUCE_BAUD_33M + IBM Spruce reference platforms are equipped with either a 30Mhz or + 33Mhz CPC700 input oscillator. Enable this option only if you + have the 33Mhz oscillator. + +Embedded 8xx Board Type +CONFIG_RPXLITE + RPX-Lite: + Embedded Planet RPX Lite + + RPX-Classic: + Embedded Planet RPX Classic Low-fat. + + BSE-IP: + Bright Star Engineering ip-Engine. + + FADS: Motorola FADS Board + + TQM823L: + TQM850L: + TQM855L: + TQM860L: + MPC8xx based family of mini modules, half credit card size, + up to 64 MB of RAM, 8 MB Flash, (Fast) Ethernet, 2 x serial ports, + 2 x CAN bus interface, ... + Manufacturer: TQ Components, www.tq-group.de + Date of Release: October (?) 1999 + End of Life: not yet :-) + URL: + - module: http://www.denx.de/PDF/TQM8xxLHWM201.pdf + - starter kit: http://www.denx.de/PDF/STK8xxLHWM201.pdf + - images: http://www.denx.de/embedded-ppc-en.html + + FPS850L: + FingerPrint Sensor System (based on TQM850L) + Manufacturer: IKENDI AG, http://www.ikendi.com/ + Date of Release: November 1999 + End of life: end 2000 ? + URL: see TQM850L + + SPD823TS: + MPC823 based board used in the "Tele Server" product + Manufacturer: Speech Design, http://www.speech-design.de/ + Date of Release: Mid 2000 (?) + End of life: - + URL: http://www.speech-design.de/ + select "English", then "Teleteam Solutions", then "TeleServer" + + IVMS8: + MPC860 based board used in the "Integrated Voice Mail System", + Small Version (8 voice channels) + Manufacturer: Speech Design, http://www.speech-design.de/ + Date of Release: December 2000 (?) + End of life: - + URL: http://www.speech-design.de/ + + IVML24: + MPC860 based board used in the "Integrated Voice Mail System", + Large Version (24 voice channels) + Manufacturer: Speech Design, http://www.speech-design.de/ + Date of Release: March 2001 (?) + End of life: - + URL: http://www.speech-design.de/ + + SM850: + Service Module (based on TQM850L) + Manufacturer: Dependable Computer Systems, http://www.decomsys.com/ + Date of Release: end 2000 (?) + End of life: mid 2001 (?) + URL: http://www.tz-mikroelektronik.de/ServiceModule/index.html + + HERMES_PRO: + Hermes-Pro ISDN/LAN router with integrated 8 x hub + Manufacturer: Multidata Gesellschaft f’r Datentechnik und Informatik + http://www.multidata.de/ + Date of Release: 2000 (?) + End of life: - + URL: http://www.multidata.de/english/products/hpro.htm + + IP860: + VMEBus IP (Industry Pack) carrier board with MPC860 + Manufacturer: MicroSys GmbH, http://www.microsys.de/ + Date of Release: ? + End of life: - + URL: http://www.microsys.de/html/ip860.html + + LWMON: + Monitor Controller for Mobile Cranes + Manufacturer: Liebherr Werke Ehingen + Date of Release: ? + End of life: - + URL: http://www.liebherr.com/us/ ==> Products ==> Mobile Cranes + + PCU_E: + Peripheral Controller Unit, Extended + Manufacturer: Siemens AG, ICN (Information and Communication Networks) + http://www.siemens.de/page/1,3771,224315-1-999_2_226207-0,00.html + Date of Release: April 2001 + End of life: August 2001 + URL: n. a. + + CCM: + Card Controller Module + Manufacturer: Siemens AG, ICN (Information and Communication Networks) + http://www.siemens.de/page/1,3771,224315-1-999_2_226207-0,00.html + Date of Release: August 2001 + End of life: - + URL: n. a. + + LANTEC: + Automaton Controller + Manufacturer: Lantec AG + Date of Release: ? + End of life: - + URL: http://www.lantec.de/html/english/start.html + + MBX: Motorola MBX8xx board + + WinCept: sorry, no description yet + +Embedded 82xx Board Type +CONFIG_EST8260 + EST8260: Wind River System, Inc. EST SBC8260 + + TQM8260: + MPC8260 based module, little larger than credit card, + up to 128 MB global + 64 MB local RAM, 32 MB Flash, + 32 kB EEPROM, 256 kB L@ Cache, 10baseT + 100baseT Ethernet, + 2 x serial ports, ... + Manufacturer: TQ Components, www.tq-group.de + Date of Release: June 2001 + End of Life: not yet :-) + URL: http://www.denx.de/PDF/TQM82xx_SPEC_Rev005.pdf + + PM826: + Modular system with MPC8260 CPU + Manufacturer: MicroSys GmbH, http://www.microsys.de/ + Date of Release: mid 2001 + End of life: - + URL: http://www.microsys.de/html/pm826.html + + CU824: + VMEBus Board with PCI extension with MPC8240 CPU + Manufacturer: MicroSys GmbH, http://www.microsys.de/ + Date of Release: early 2001 (?) + End of life: - + URL: http://www.microsys.de/html/cu824.html + AltiVec kernel support CONFIG_ALTIVEC This option enables kernel support for the Altivec extensions to the @@ -20653,6 +21366,12 @@ 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. +MVME5100 configured with an IPMC761 +CONFIG_MVME5100_IPMC761_PRESENT + The MVME5100 supports a special IPMC761 PMC module in PMC site 1. + This option enables the use of the onboard i8259 PIC and ISA I/O + to support the legacy peripherals on the module. + Power management support for PowerBooks CONFIG_PMAC_PBOOK This provides support for putting a PowerBook to sleep; it also @@ -20669,6 +21388,14 @@ have it autoloaded. The act of removing the module shuts down the sound hardware for more power savings. +APM emulation +CONFIG_PMAC_APM_EMU + This driver provides an emulated /dev/apm_bios and /proc/apm. The + first one is mostly intended for XFree to sleep & wakeup properly, + the second ones provides some battery informations to allow existing + APM utilities to work. It provides less useful informations than + tools specifically designed for PowerBooks or /proc/pmu/battery_x + Backlight control for LCD screens CONFIG_PMAC_BACKLIGHT Say Y here to build in code to manage the LCD backlight on a @@ -20749,7 +21476,7 @@ HERMES: Hermes-Pro ISDN/LAN router with integrated 8 x hub - Manufacturer: Multidata Gesellschaft für Datentechnik und Informatik + Manufacturer: Multidata Gesellschaft f’r Datentechnik und Informatik Date of Release: 2000 (?) End of life: - @@ -20961,12 +21688,20 @@ If unsure, say Y here. -I2C/SPI Microcode Patch +I2C/SPI (or USB) Microcode Patch CONFIG_UCODE_PATCH - Motorola releases microcode updates for their 8xx CPM modules. The - microcode update file has updates for IIC, SMC and USB. Currently only - the USB update is available by default, if the MPC8xx USB option is - enabled. If in doubt, say 'N' here. + There are two patches for the MPC8xx CPM microcode that may be + required to support certain hardware configurations. At most one + of these patches can be installed by the kernel when the CPM is + initialized. If the microcode patch is enabled and the MPC8xx + Host Controller Interface USB driver is also enabled, then the + USB microcode patch will be installed. Otherwise, if the + microcode patch is enabled then the I2C/SPI microcode patch will + be installed. The I2C/SPI microcode patch is required if SCC1 + is used for Ethernet and the CPM I2C device is enabled, or if SCC2 + is used for Ethernet and the CPM SPI device is enabled. Consult + Motorola documentation on the microcode patches for more + information. Mouse button 2+3 emulation support CONFIG_MAC_EMUMOUSEBTN @@ -20978,6 +21713,38 @@ /proc/sys/dev/mac_hid/mouse_button2_keycode /proc/sys/dev/mac_hid/mouse_button3_keycode +Set high memory pool address +CONFIG_HIGHMEM_START_BOOL + Unless you know what you are doing you *should not* set this option. + + It can be used to override the default PKMAP_BASE address which + is the location of the high memory pool. This can be useful in + optimizing virtual memory usage in a system. + +Set maximum low memory +CONFIG_LOWMEM_SIZE_BOOL + Unless you know what you are doing you *should not* set this option. + + It can be used to override the standard calculated value of + MAX_LOW_MEM. This can be useful in optimizing virtual memory usage + in a system. + +Set custom kernel base address +CONFIG_KERNEL_START_BOOL + Unless you know what you are doing you *should not* set this option. + + It can be used to override the standard PAGE_OFFSET/KERNELBASE + value used by the kernel. This can be useful in controlling + amount of virtual address space available to the kernel. + +Set custom user task size +CONFIG_TASK_SIZE_BOOL + Unless you know what you are doing you *should not* set this option. + + It can be used to override the standard TASK_SIZE value used + by the kernel. This can be useful in controlling amount of + virtual address space available to user tasks. + Enhanced Real Time Clock Support (/dev/rtc) CONFIG_PPC_RTC If you say Y here and create a character special file /dev/rtc with @@ -21550,7 +22317,7 @@ otherwise say N. This driver is also available as a module (w9966.o). - Check out and + Check out and for more information. CPiA Video For Linux @@ -21906,6 +22673,20 @@ Saying N will reduce the size of the Footbridge kernel. +IQ80310 +CONFIG_ARCH_IQ80310 + Say Y here if you want to run your kernel on the Intel IQ80310 + evaluation kit for the IOP310 chipset. + +Run IQ80310 @ 733MHz +CONFIG_IQ80310_TURBO_CHARGE + Say Y here if you want to run your IQ80310 a 733MHz kernel. + Note that if you do so, you are doing at your own risk and + cannot hold anyone else liable for any hardware failures this + might cause. Having said that, this should not cause any + hardware failures as many people have been running their IQ80310 + boards at that speed for months. + LinkUp Systems L7200 SDB CONFIG_ARCH_L7200 Say Y here if you intend to run this kernel on a LinkUp Systems @@ -22060,6 +22841,13 @@ Say Y if configuring for a Pangolin. Say N otherwise. +Shannon +CONFIG_SA1100_SHANNON + The Shannon (also known as a Tuxscreen, and also as a IS2630) was a + limited edition webphone produced by Philips. The Shannon is a SA1100 + platform with a 640x480 LCD, touchscreen, CIR keyboard, PCMCIA slots, + and a telco interface. + Victor CONFIG_SA1100_VICTOR Say Y here if you are using a Visu Aide Intel(R) StrongARM(R) @@ -22134,6 +22922,36 @@ Say Y if you want support for the ARM920T processor. Otherwise, say N. +Support ARM922T processor +CONFIG_CPU_ARM922T + The ARM922T is a version of the ARM920T, but with smaller + instruction and data caches. It is used in Altera's + Excalibur XA device family. + + Say Y if you want support for the ARM922T processor. + Otherwise, say N. + +Support low power wait for interrupt +CONFIG_CPU_ARM922_CPU_IDLE + Saying Y here will allow the processor to enter a low power + mode whilst waiting for an interrupt in idle. If you're unsure + say Y. + +Enable ARM922T instruction cache +CONFIG_CPU_ARM922_I_CACHE_ON + Say Y here to enable the processor instruction cache. Unless + you have a reason not to, say Y. + +Enable ARM922T data cache +CONFIG_CPU_ARM922_D_CACHE_ON + Say Y here to enable the processor data cache. Unless + you have a reason not to, say Y. + +Use data cache in writethrough mode +CONFIG_CPU_ARM922_WRITETHROUGH + Say Y here to use the data cache in writethough mode. Unless you + specifically require this, say N. + Support ARM1020 processor CONFIG_CPU_ARM1020 The ARM1020 is the cached version of the ARM10 processor, @@ -22154,7 +22972,7 @@ Tulsa CONFIG_SA1100_PFS168 - The Radisys Corp. PFS-168 (aka Tulsa) is an Intel® StrongArm® SA-1110 based + The Radisys Corp. PFS-168 (aka Tulsa) is an Intel« StrongArm« SA-1110 based computer which includes the SA-1111 Microprocessor Companion Chip and other custom I/O designed to add connectivity and multimedia features for vending and business machine applications. Say Y here if you require support for @@ -23766,6 +24584,46 @@ To use this option, you have to check that the "/proc file system support" (CONFIG_PROC_FS) is enabled, too. +Blue Logic DMA +CONFIG_405_DMA + Select this to use the 405's built-in DMA features. + +ttyS0 device +CONFIG_UART0_TTYS0 + This option reverses the mapping between the hardware UART and software + device. Selecting UART0 gives the normal mapping of UART0=ttyS0 and + UART1=ttyS1. Selecting UART1 gives the reverse mapping of UART0=ttyS1 + and UART1=ttyS0. Most people will use UART0. + +PowerPC 405 on-chip ethernet +CONFIG_PPC405_ENET + If you want to use the 405 built-in ethernet select this. + +CONFIG_PPC405_ENET_ERROR_MSG + Enable this option to print verbose debug messages for troubleshooting. + +PowerPC 405 on-chip ethernet -- Number of receive buffers +CONFIG_PPC405_ENET_RX_BUFF + Number of ethernet receive (read) buffers. Unless you know what you + are doing the default should be fine. + +PowerPC 405 on-chip ethernet -- Number of transmit buffers +CONFIG_PPC405_ENET_TX_BUFF + Number of ethernet transmit (write) buffers. Unless you know what + you are doing the default should be fine. + +PPC 405 I2C Algorithm +CONFIG_PPC405_I2C_ALGO + Enable this option to use the built-in I2C on your 405. + +PPC 405 I2C Adapter +CONFIG_PPC405_I2C_ADAP + Enable this option to use the built-in I2C on your 405. + +BM PPC 405 Watchdog Timer +CONFIG_PPC405_WDT + Enable this option to use the built-in watch dog timer on your 405. + Kernel support for IA-32 emulation CONFIG_IA32_SUPPORT IA64 processors can run IA32 (that is, x86) binaries by emulating @@ -23888,6 +24746,23 @@ Include in-kernel hooks for the xmon kernel monitor/debugger supported by the PPC port. +Include BDI2000 debugger support +CONFIG_BDI_SWITCH + Include in-kernel support for the Abatron BDI2000 debugger. + +Add additional CFLAGS to the kernel build +CONFIG_MORE_COMPILE_OPTIONS + If you want to add additional CFLAGS to the kernel build, such as + -g for KGDB, XMON or the BDI2000, enable this option and then + enter what you would like to add in the next question. + +Add additional CFLAGS to the kernel build +CONFIG_KGDB_MORE_COMPILE_OPTIONS + If you want to add additional CFLAGS to the kernel build, such as + -ggdb or -O1, enable this option and then enter what you would + like to add in the next question. Otherwise only -g will be added. + Note, if you enable this, you will need to specify the use of -g. + Include kgdb kernel debugger CONFIG_KWDB Include in-kernel hooks for kdb, the source level debugger for the @@ -24231,12 +25106,426 @@ remotely using gdb. This is only useful for kernel hackers. If unsure, say N. +Include KGDB kernel debugger +CONFIG_SH_KGDB + If you say Y here, the system will be compiled with the debug option + (-g) and a debugging stub will be included in the kernel, making it + possible to debug remotely debug the SH kernel using GDB. This will + enlarge your kernel image disk size by several megabytes. To use + this feature you will need to perform some basic setup described + briefly in Documentation/sh/kgdb.txt; please refer to that file for + more information. + + This is only useful for kernel hackers. If unsure, say N. + +Include KGDB thread support +CONFIG_KGDB_THREAD + With thread analysis enabled, GDB can communicate with the kernel to + list threads and to get a stack trace for a thread. (Note that while + threads can be listed and their registers examined, only the thread + which entered KGDB can be executed -- i.e. continued or stepped.) + +Console messages through GDB +CONFIG_SH_KGDB_CONSOLE + If you say Y here, console messages will appear through GDB. + Other consoles will continue to work as usual. + + (Note: even without this option, if the console and KGDB are using + the same SCI/F [ttySCn] then console messages will be encapsulated + for GDB when the system is in GDB mode.) + +Include KGDB kernel asserts +CONFIG_KGDB_KERNEL_ASSERTS + This option enables kernel asserts. A kernel assert is a condition, + which, if false during an execution path, results in a call to KGDB. + + Kernel assertions help in modifying the kernel or writing drivers + - bugs can be traced sooner with kernel asserts because invalid + conditions are checked at various places. Kernel asserts add the + overhead of checking asserted conditions - you can disable this + option if you do not want the overhead. Kernel asserts are defined + in kgdb.h. + +Enter KGDB on NMI +CONFIG_KGDB_NMI + This option allows an NMI to be used to enter KGDB, as used on the + Hitachi Solution Engine boards. + +Default KGDB port setup +CONFIG_KGDB_DEFPORT + These options allow you to configure attributes of the KGDB serial + port; only ports ttySCn (e.g. ttySC0, ttySC1) can be selected here. + The kgdb option can be used on the command line to override these + settings, e.g. "kgdb=ttySC1,115200E7". + Console output to GDB CONFIG_GDB_CONSOLE If you are using GDB for remote debugging over a serial port and would like kernel messages to be formatted into GDB $O packets so that GDB prints them as program output, say 'Y'. +I2C mainboard interfaces +CONFIG_I2C_MAINBOARD + Many modern mainboards have some kind of I2C interface integrated. This + is often in the form of a SMBus, or System Management Bus, which is + basically the same as I2C but which uses only a subset of the I2C + protocol. + + You will also want the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Acer Labs ALI 1535 +CONFIG_I2C_ALI1535 + If you say yes to this option, support will be included for the Acer + Labs ALI 1535 mainboard I2C interface. This can also be + built as a module. + +Acer Labs ALI 1533 and 1543C +CONFIG_I2C_ALI15X3 + If you say yes to this option, support will be included for the Acer + Labs ALI 1533 and 1543C mainboard I2C interfaces. This can also be + built as a module which can be inserted and removed while the kernel + is running. + +AMD 756/766 +CONFIG_I2C_AMD756 + If you say yes to this option, support will be included for the AMD + 756/766 mainboard I2C interfaces. This can also be + built as a module which can be inserted and removed while the kernel + is running. + +Apple Hydra Mac I/O +CONFIG_I2C_HYDRA + If you say yes to this option, support will be included for the + Hydra mainboard I2C interface. This can also be built as a module + which can be inserted and removed while the kernel is running. + +Intel I801 +CONFIG_I2C_I801 + If you say yes to this option, support will be included for the + Intel I801 mainboard I2C interfaces. "I810" mainboard sensor chips are + generally located on the I801's I2C bus. This can also be + built as a module which can be inserted and removed while the kernel + is running. + +Intel I810/I815 +CONFIG_I2C_I810 + If you say yes to this option, support will be included for the + Intel I810/I815 mainboard I2C interfaces. The I2C busses these chips + are generally used only for video devices. For "810" mainboard sensor + chips, use the I801 I2C driver instead. This can also be + built as a module which can be inserted and removed while the kernel + is running. + +Intel 82371AB PIIX4(E) / ServerWorks OSB4 and CSB5 +CONFIG_I2C_PIIX4 + If you say yes to this option, support will be included for the + Intel PIIX4 and PIIX4E and Serverworks OSB4/CSB5 mainboard + I2C interfaces. This can also be + built as a module which can be inserted and removed while the kernel + is running. + +Silicon Integrated Systems Corp. SiS5595 +CONFIG_I2C_SIS5595 + If you say yes to this option, support will be included for the + SiS5595 mainboard I2C interfaces. For integrated sensors on the + Sis5595, use CONFIG_SENSORS_SIS5595. This can also be + built as a module which can be inserted and removed while the kernel + is running. + +VIA Technologies, Inc. VT82C586B +CONFIG_I2C_VIA + If you say yes to this option, support will be included for the VIA + Technologies I2C adapter found on some motherboards. This can also + be built as a module which can be inserted and removed while the + kernel is running. + +VIA Technologies, Inc. VT82C596, 596B, 686A/B +CONFIG_I2C_VIAPRO + If you say yes to this option, support will be included for the VIA + Technologies I2C adapter on these chips. For integrated sensors on the + Via 686A/B, use CONFIG_SENSORS_VIA686A. This can also be + be built as a module which can be inserted and removed while the + kernel is running. + +3DFX Banshee / Voodoo3 +CONFIG_I2C_VOODOO3 + If you say yes to this option, support will be included for the + 3DFX Banshee and Voodoo3 I2C interfaces. The I2C busses on the these + chips are generally used only for video devices. + This can also be + built as a module which can be inserted and removed while the kernel + is running. + +DEC Tsunami 21272 +CONFIG_I2C_TSUNAMI + If you say yes to this option, support will be included for the DEC + Tsunami chipset I2C adapter. Requires the Alpha architecture; + do not enable otherwise. This can also be built as a module which + can be inserted and removed while the kernel is running. + +Pseudo ISA adapter (for hardware sensors modules) +CONFIG_I2C_ISA + This provides support for accessing some hardware sensor chips over + the ISA bus rather than the I2C or SMBus. If you want to do this, + say yes here. This feature can also be built as a module which can + be inserted and removed while the kernel is running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Analog Devices ADM1021 and compatibles +CONFIG_SENSORS_ADM1021 + If you say yes here you get support for Analog Devices ADM1021 + and ADM1023 sensor chips and clones: Maxim MAX1617 and MAX1617A, + Genesys Logic GL523SM, National Semi LM84, TI THMC10, + and the XEON processor built-in sensor. This can also + be built as a module which can be inserted and removed while the + kernel is running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Analog Devices ADM1024 +CONFIG_SENSORS_ADM1024 + If you say yes here you get support for Analog Devices ADM1024 sensor + chips. This can also be built as a module. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Analog Devices ADM1025 +CONFIG_SENSORS_ADM1025 + If you say yes here you get support for Analog Devices ADM1025 sensor + chips. This can also be built as a module which can be inserted and + removed while the kernel is running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Analog Devices ADM9240 and compatibles +CONFIG_SENSORS_ADM9240 + If you say yes here you get support for Analog Devices ADM9240 + sensor chips and clones: the Dallas Semiconductor DS1780 and + the National Semiconductor LM81. This can also be built as a + module which can be inserted and removed while the kernel is + running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Dallas DS1621 and DS1625 +CONFIG_SENSORS_DS1621 + If you say yes here you get support for the Dallas DS1621 and DS1625x + sensor chips. This can also be built as a module. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Fujitsu-Siemens Poseidon +CONFIG_SENSORS_FSCPOS + If you say yes here you get support for the Fujitsu-Siemens Poseidon + sensor chip. This can also be built as a module. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Genesys Logic GL518SM +CONFIG_SENSORS_GL518SM + If you say yes here you get support for Genesys Logic GL518SM sensor + chips. This can also be built as a module which can be inserted and + removed while the kernel is running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Genesys Logic GL520SM +CONFIG_SENSORS_GL520SM + If you say yes here you get support for Genesys Logic GL518SM sensor + chips. This can also be built as a module which can be inserted and + removed while the kernel is running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +HP Maxilife +CONFIG_SENSORS_MAXILIFE + If you say yes here you get support for the HP Maxilife + sensor chip. This can also be built as a module. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +ITE 8705, 8712, Sis950 +CONFIG_SENSORS_IT87 + If you say yes here you get support for the ITE 8705 and 8712 and + SiS950 sensor chips. This can also be built as a module. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Myson MTP008 +CONFIG_SENSORS_MTP008 + If you say yes here you get support for the Myson MTP008 + sensor chip. This can also be built as a module. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +National Semiconductor LM75 and compatibles +CONFIG_SENSORS_LM75 + If you say yes here you get support for National Semiconductor LM75 + sensor chips and clones: Dallas Semi DS75 and DS1775, TelCon + TCN75, and National Semi LM77. This can also be built as a module which + can be inserted and removed while the kernel is running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +National Semiconductor LM78 +CONFIG_SENSORS_LM78 + If you say yes here you get support for National Semiconductor LM78 + sensor chips family: the LM78-J and LM79. Many clone chips will + also work at least somewhat with this driver. This can also be built + as a module which can be inserted and removed while the kernel is + running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +National Semiconductor LM80 +CONFIG_SENSORS_LM80 + If you say yes here you get support for National Semiconductor LM80 + sensor chips. This can also be built as a module which can be + inserted and removed while the kernel is running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +National Semiconductor LM87 +CONFIG_SENSORS_LM87 + If you say yes here you get support for National Semiconductor LM87 + sensor chips. This can also be built as a module which can be + inserted and removed while the kernel is running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Silicon Integrated Systems Corp. SiS5595 +CONFIG_SENSORS_SIS5595 + If you say yes here you get support for the integrated sensors in + SiS5595 South Bridges. This can also be built as a module + which can be inserted and removed while the kernel is running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Texas Instruments THMC50 / Analog Devices ADM1022 +CONFIG_SENSORS_THMC50 + If you say yes here you get support for Texas Instruments THMC50 + sensor chips and clones: the Analog Devices ADM1022. + This can also be built as a module which + can be inserted and removed while the kernel is running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Via VT82C686A/B +CONFIG_SENSORS_VIA686A + If you say yes here you get support for the integrated sensors in + Via 686A/B South Bridges. This can also be built as a module + which can be inserted and removed while the kernel is running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +Winbond W83781D, W83782D, W83783S, W83627HF, AS99127F +CONFIG_SENSORS_W83781D + If you say yes here you get support for the Winbond W8378x series + of sensor chips: the W83781D, W83782D, W83783S and W83682HF, + and the similar Asus AS99127F. This + can also be built as a module which can be inserted and removed + while the kernel is running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + +EEprom (DIMM) reader +CONFIG_SENSORS_EEPROM + If you say yes here you get read-only access to the EEPROM data + available on modern memory DIMMs, and which could theoretically + also be available on other devices. This can also be built as a + module which can be inserted and removed while the kernel is + running. + + You will also need the latest user-space utilties: you can find them + in the lm_sensors package, which you can download at + http://www.lm-sensors.nu + + +MontaVista(tm) Net CompactPCI Backplane Networking +CONFIG_HHNET + MontaVista(tm) Net is a PCI backplane networking system which allows + selected PCI devices to use the PCI backpanel as a virtual network. + It presents a standard network device to the kernel (pci0), which + may be used and managed in a manner similar to a real Ethernet + interface. Support is currently limited to target devices that use a + Dec/Intel 21554 bridge as their interface with the PCI bus. For + additional details and configuration information, see the hhnet.txt + file in the Linux networking documentation directory. + + +MontaVista(tm) Net DMA Support +CONFIG_HHNET_DMA + MontaVista(tm) Net includes a driver for the DMA engine contained in the + MPC8240 and the MPC107 bridge. This driver increases performance but + can introduce some additional latency. + + This option is currently available only for the MEN-F1 and the Force + 680. If building for the MEN-F1 or the Force 680 and MontaVista(tm) Net + DMA support is desired, answer Y. The MPC106 used on the Force 6750 + does not have a DMA engine. If building for the Force 6750, answer + N. + + +Work-around Mips __init bug +CONFIG_REMOTE_DEBUG_NO_INIT + There is a versioning issue between the mips kernel and tool chain. + This bug causes the gdb to fail to map symbols to address correctly + for .text.init (__init) and similar init sections. + + This fix eliminates the init sections and thus the kernel uses more + memory because nothing will be freed by "free_initmem()". + + This option is NOT needed in the following cases: 1) You are not + debugging any __init code. 2) You have limited memory and __init + is required. You will still be able to debug, but will not be able + to use symbols (you will need to use addresses only). + + If unsure set this option any time CONFIG_REMOTE_DEBUG is set. + + # # A couple of things I keep forgetting: # capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet, @@ -24552,7 +25841,8 @@ # LocalWords: CramFs Cramfs uid cramfs AVM's kernelcapi PCIV cdrdao Cdparanoia # LocalWords: DMX Domex dmx wellington ftdi sio Accton Billington Corega FEter # LocalWords: MELCO LUA PNA Linksys SNC chkdsk AWACS Webcam RAMFS Ramfs ramfs -# LocalWords: ramfiles MAKEDEV pty WDTPCI APA apa +# LocalWords: ramfiles MAKEDEV pty WDTPCI APA apa keypress kgdb stty ggdb +# LocalWords: fomit printk # # The following sets edit modes for GNU EMACS # Local Variables: