# Maintained by: # Eric S. Raymond # Steven Cole # # Version 3.01: current with 2.4.19+ # # Translations of this file available on the WWW: # # - Japanese, maintained by the JF Project , at # # - Russian, by , at # # - French, by Pierre Tane , at # # - Polish, by Dominik Mierzejewski , at # # - German, by SuSE, at . This patch # also includes infrastructure to support different languages. # - Catalan, by Antoni Bella , at # # # To access a document on the WWW, you need to have a direct Internet # connection and a browser program such as netscape or lynx. If you # only have email access, you can still use FTP and WWW servers: send # an email to with the text # send usenet/news.answers/internet-services/access-via-email # in the body of the message. # # Information about what a kernel is, what it does, how to patch and # compile it and much more is contained in the Kernel-HOWTO, available # at . Before you start # compiling, make sure that you have the necessary versions of all # programs and libraries required to compile and run this kernel; they # are listed in the . Make sure to read the # toplevel kernel README file as well. # # Format of this file: descriptionvariablehelp text. # The help texts may contain empty lines, but every non-empty line must # be indented two positions. Order of the help texts does not matter, # however, no variable should be documented twice: if it is, only the # first occurrence will be used. We try to keep the help texts of related # variables close together. Lines starting with `#' are ignored. To be # nice to menuconfig, limit your line length to 70 characters. Use emacs' # kfill.el to edit and ispell.el to spell check this file or you lose. # # Comments of the form "# Choice:" followed by a menu name are used # internally by the maintainers' consistency-checking tools. # # If you add a help text to this file, please try to be as gentle as # possible. Don't use unexplained acronyms and generally write for the # hypothetical ignorant but intelligent user who has just bought a PC, # removed Windows, installed Linux and is now recompiling the kernel # for the first time. Tell them what to do if they're unsure. Technical # information should go in a README in the Documentation directory. # # Mention all the relevant READMEs and HOWTOs in the help text. # Make them file URLs relative to the top level of the source tree so # that help browsers can turn them into hotlinks. All URLs should be # surrounded by <>. # # Repetitions are fine since the help texts are not meant to be read # in sequence. It is good style to include URLs pointing to more # detailed technical information, pictures of the hardware, etc. # # The most important thing to include in a help entry is *motivation*. # Explain why someone configuring a kernel might want to select your # option. # # All this was shamelessly stolen from numerous different sources. Many # thanks to all the contributors. Feel free to use these help texts in # your own kernel configuration tools. The texts are copyrighted (c) # 1995-2000 by Axel Boldt and many others and are governed by the GNU # General Public License. Prompt for development and/or incomplete code/drivers CONFIG_EXPERIMENTAL Some of the various things that Linux supports (such as network drivers, file systems, network protocols, etc.) can be in a state of development where the functionality, stability, or the level of testing is not yet high enough for general use. This is usually known as the "alpha-test" phase among developers. If a feature is currently in alpha-test, then the developers usually discourage uninformed widespread use of this feature by the general public to avoid "Why doesn't this work?" type mail messages. However, active testing and use of these systems is welcomed. Just be aware that it may not meet the normal level of reliability or it may fail to work in some special cases. Detailed bug reports from people familiar with the kernel internals are usually welcomed by the developers (before submitting bug reports, please read the documents , , , , and in the kernel source). This option will also make obsoleted drivers available. These are drivers that have been replaced by something else, and/or are scheduled to be removed in a future kernel release. Unless you intend to help test and develop a feature or driver that falls into this category, or you have a situation that requires using these features, you should probably say N here, which will cause the configurator to present you with fewer choices. If you say Y here, you will be offered the choice of using features or drivers that are currently considered to be in the alpha-test phase. Prompt for drivers for obsolete features and hardware CONFIG_OBSOLETE Obsolete drivers have usually been replaced by more recent software that can talk to the same hardware. Obsolete hardware is things like MGA monitors that you are very unlikely to see on today's systems. Symmetric Multi-Processing support CONFIG_SMP This enables support for systems with more than one CPU. If you have a system with only one CPU, like most personal computers, say N. If you have a system with more than one CPU, say Y. 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 many, but not all, single machines. On a singleprocessor machine, the kernel will run faster if you say N here. Note that if you say Y here and choose architecture "586" or "Pentium" under "Processor family", the kernel will not work on 486 architectures. Similarly, multiprocessor kernels for the "PPro" architecture may not work on all Pentium based boards. People using multiprocessor machines who say Y here should also say Y to "Enhanced Real Time Clock Support", below. The "Advanced Power Management" code will be disabled if you say Y here. See also the , , , and the SMP-HOWTO available at . If you don't know what to do here, say N. Intel or compatible 80x86 processor CONFIG_X86 This is Linux's home port. Linux was originally native to the Intel 386, and runs on all the later x86 processors including the Intel 486, 586, Pentiums, and various instruction-set-compatible chips by AMD, Cyrix, and others. Alpha processor CONFIG_ALPHA The Alpha is a 64-bit general-purpose processor designed and marketed by the Digital Equipment Corporation of blessed memory, now Compaq. Alpha Linux dates from 1995-1996 and was the first non-x86 port. The Alpha Linux project has a home page at . 32-bit Sun Sparc CONFIG_SPARC32 SPARC is a family of RISC microprocessors designed and marketed by Sun Microsystems, incorporated. They are very widely found in Sun workstations and clones. This port covers the original 32-bit SPARC; it is old and stable and usually considered one of the "big three" along with the Intel and Alpha ports. The UltraLinux project maintains both the SPARC32 and SPARC64 ports; its web page is available at . 64-bit Sun Sparc CONFIG_SPARC64 SPARC is a family of RISC microprocessors designed and marketed by Sun Microsystems, incorporated. This port covers the newer 64-bit UltraSPARC. The UltraLinux project maintains both the SPARC32 and SPARC64 ports; its web page is available at . Power PC processor CONFIG_PPC The PowerPC is a very capable 32-bit RISC processor from Motorola, the successor to their 68000 and 88000 series. It powers recent Macintoshes and also a widely-used series of single-board computers from Motorola. The Linux PowerPC port has a home page at . Motorola 68K processors CONFIG_M68K The Motorola 68K microprocessors are now obsolete, having been superseded by the PowerPC line also from Motorola. But they powered the first wave of workstation hardware in the 1980s, including Sun workstations; they were also the basis of the original Amiga and later Atari personal computers. A lot of this hardware is still around. The m68k project has a home page at . ARM processors CONFIG_ARM The ARM series is a line of low-power-consumption RISC chip designs licensed by ARM ltd and targeted at embedded applications and handhelds such as the Compaq IPAQ. ARM-based PCs are no longer manufactured, but legacy ARM-based PC hardware remains popular in Europe. There is an ARM Linux project with a web page at . SuperH processors CONFIG_SUPERH The SuperH is a RISC processor targeted for use in embedded systems and consumer electronics; it was also used in the Sega Dreamcast gaming console. The SuperH port has a home page at . IA64 processors, including Intel Itanium CONFIG_IA64 The Itanium is Intel's 64-bit successor to the 32-bit X86 line. As of early 2001 it is not yet in widespread production use. The Linux IA-64 project has a home page at . HP PA-RISC processor CONFIG_PARISC The PA-RISC microprocessor is a RISC chip designed by Hewlett-Packard and used in their line of workstations. The PA-RISC Linux project has a home page at . IBM System/390 CONFIG_S390 Linux now runs on the venerable System/390 mainframe from IBM, in a guest partition under VM. In fact, over 40,000 simultaneous Linux images have been run on a single mainframe! The S390 Linux project has a home page at . Axis Communications ETRAX 100LX embedded network CPU CONFIG_CRIS Linux has been ported to run on the Axis Communications ETRAX 100LX CPU and the single-board computers built around it, targeted for network and embedded applications. For more information see the Axis Communication site, . Unsynced TSC support CONFIG_X86_TSC_DISABLE This option is used for getting Linux to run on a NUMA multi-node boxes, laptops and other systems suffering from unsynced TSCs or TSC drift, which can cause gettimeofday to return non-monotonic values. Choosing this option will disable the CONFIG_X86_TSC optimization, and allows you to then specify "notsc" as a boot option regardless of which processor you have compiled for. NOTE: If your system hangs when init should run, you are probably using a i686 compiled glibc which reads the TSC without checking for availability. Boot without "notsc" and install a i386 compiled glibc to solve the problem. If unsure, say N. Multiquad support for NUMA systems CONFIG_MULTIQUAD This option is used for getting Linux to run on a (IBM/Sequent) NUMA multiquad box. This changes the way that processors are bootstrapped, and uses Clustered Logical APIC addressing mode instead of Flat Logical. You will need a new lynxer.elf file to flash your firmware with - send email to Martin.Bligh@us.ibm.com IO-APIC support on uniprocessors CONFIG_X86_UP_IOAPIC An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an SMP-capable replacement for PC-style interrupt controllers. Most SMP systems and a small number of uniprocessor systems have one. If you have a single-CPU system with an IO-APIC, you can say Y here to use it. If you say Y here even though your machine doesn't have an IO-APIC, then the kernel will still run with no slowdown at all. If you have a system with several CPUs, you do not need to say Y here: the IO-APIC will be used automatically. Local APIC Support on Uniprocessors CONFIG_X86_UP_APIC A local APIC (Advanced Programmable Interrupt Controller) is an integrated interrupt controller in the CPU. If you have a single-CPU system which has a processor with a local APIC, you can say Y here to enable and use it. If you say Y here even though your machine doesn't have a local APIC, then the kernel will still run with no slowdown at all. The local APIC supports CPU-generated self-interrupts (timer, performance counters), and the NMI watchdog which detects hard lockups. If you have a system with several CPUs, you do not need to say Y here: the local APIC will be used automatically. Kernel math emulation CONFIG_MATH_EMULATION Linux can emulate a math coprocessor (used for floating point operations) if you don't have one. 486DX and Pentium processors have a math coprocessor built in, 486SX and 386 do not, unless you added a 487DX or 387, respectively. (The messages during boot time can give you some hints here ["man dmesg"].) Everyone needs either a coprocessor or this emulation. If you don't have a math coprocessor, you need to say Y here; if you say Y here even though you have a coprocessor, the coprocessor will be used nevertheless. (This behaviour can be changed with the kernel command line option "no387", which comes handy if your coprocessor is broken. Try "man bootparam" or see the documentation of your boot loader (lilo or loadlin) about how to pass options to the kernel at boot time.) This means that it is a good idea to say Y here if you intend to use this kernel on different machines. More information about the internals of the Linux math coprocessor emulation can be found in . If you are not sure, say Y; apart from resulting in a 66 KB bigger kernel, it won't hurt. Timer and CPU usage LEDs CONFIG_LEDS If you say Y here, the LEDs on your machine will be used to provide useful information about your current system status. If you are compiling a kernel for a NetWinder or EBSA-285, you will be able to select which LEDs are active using the options below. If you are compiling a kernel for the EBSA-110 or the LART however, the red LED will simply flash regularly to indicate that the system is still functional. It is safe to say Y here if you have a CATS system, but the driver will do nothing. Timer LED CONFIG_LEDS_TIMER If you say Y here, one of the system LEDs (the green one on the NetWinder, the amber one on the EBSA285, or the red one on the LART) will flash regularly to indicate that the system is still operational. This is mainly useful to kernel hackers who are debugging unstable kernels. The LART uses the same LED for both Timer LED and CPU usage LED functions. You may choose to use both, but the Timer LED function will overrule the CPU usage LED. CPU usage LED CONFIG_LEDS_CPU If you say Y here, the red LED will be used to give a good real time indication of CPU usage, by lighting whenever the idle task is not currently executing. The LART uses the same LED for both Timer LED and CPU usage LED functions. You may choose to use both, but the Timer LED function will overrule the CPU usage LED. Kernel FP software completion CONFIG_MATHEMU This option is required for IEEE compliant floating point arithmetic on the Alpha. The only time you would ever not say Y is to say M in order to debug the code. Say Y unless you know what you are doing. # Choice: himem High Memory support CONFIG_NOHIGHMEM Linux can use up to 64 Gigabytes of physical memory on x86 systems. However, the address space of 32-bit x86 processors is only 4 Gigabytes large. That means that, if you have a large amount of physical memory, not all of it can be "permanently mapped" by the kernel. The physical memory that's not permanently mapped is called "high memory". If you are compiling a kernel which will never run on a machine with more than 960 megabytes of total physical RAM, answer "off" here (default choice and suitable for most users). This will result in a "3GB/1GB" split: 3GB are mapped so that each process sees a 3GB virtual memory space and the remaining part of the 4GB virtual memory space is used by the kernel to permanently map as much physical memory as possible. If the machine has between 1 and 4 Gigabytes physical RAM, then answer "4GB" here. If more than 4 Gigabytes is used then answer "64GB" here. This selection turns Intel PAE (Physical Address Extension) mode on. PAE implements 3-level paging on IA32 processors. PAE is fully supported by Linux, PAE mode is implemented on all recent Intel processors (Pentium Pro and better). NOTE: If you say "64GB" here, then the kernel will not boot on CPUs that don't support PAE! The actual amount of total physical memory will either be auto detected or can be forced by using a kernel command line option such as "mem=256M". (Try "man bootparam" or see the documentation of your boot loader (grub, lilo or loadlin) about how to pass options to the kernel at boot time.) If unsure, say "off". 4GB CONFIG_HIGHMEM4G Select this if you have a 32-bit processor and between 1 and 4 gigabytes of physical RAM. 64GB CONFIG_HIGHMEM64G Select this if you have a 32-bit processor and more than 4 gigabytes of physical RAM. HIGHMEM I/O support CONFIG_HIGHIO If you want to be able to do I/O to high memory pages, say Y. Otherwise low memory pages are used as bounce buffers causing a degrade in performance. Normal floppy disk support CONFIG_BLK_DEV_FD If you want to use the floppy disk drive(s) of your PC under Linux, say Y. Information about this driver, especially important for IBM Thinkpad users, is contained in . That file also contains the location of the Floppy driver FAQ as well as location of the fdutils package used to configure additional parameters of the driver at run time. 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 floppy.o. If you want to compile it as a module, say M here and read . iSeries Virtual I/O Disk Support CONFIG_VIODASD If you are running on an iSeries system and you want to use virtual disks created and managed by OS/400, say Y. iSeries Virtual I/O Disk IDE Emulation CONFIG_VIODASD_IDE This causes the iSeries virtual disks to look like IDE disks. If you have programs or utilities that only support certain kinds of disks, this option will cause iSeries virtual disks to pretend to be IDE disks, which may satisfy the program. Support for PowerMac floppy CONFIG_MAC_FLOPPY If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple) floppy controller, say Y here. Most commonly found in PowerMacs. RAM disk support CONFIG_BLK_DEV_RAM Saying Y here will allow you to use a portion of your RAM memory as a block device, so that you can make file systems on it, read and write to it and do all the other things that you can do with normal block devices (such as hard drives). It is usually used to load and store a copy of a minimal root file system off of a floppy into RAM during the initial install of Linux. Note that the kernel command line option "ramdisk=XX" is now obsolete. For details, read . If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M and read . The module will be called rd.o. Most normal users won't need the RAM disk functionality, and can thus say N here. Default RAM disk size CONFIG_BLK_DEV_RAM_SIZE The default value is 4096. Only change this if you know what are you doing. If you are using IBM S/390, then set this to 8192. Initial RAM disk (initrd) support CONFIG_BLK_DEV_INITRD The initial RAM disk is a RAM disk that is loaded by the boot loader (loadlin or lilo) and that is mounted as root before the normal boot procedure. It is typically used to load modules needed to mount the "real" root file system, etc. See for details. Embed root filesystem ramdisk into the kernel CONFIG_EMBEDDED_RAMDISK Select this option if you want to build the ramdisk image into the the final kernel binary. Filename of gziped ramdisk image CONFIG_EMBEDDED_RAMDISK_IMAGE This is the filename of the ramdisk image to be built into the kernel. Relative pathnames are relative to arch/mips/ramdisk/. The ramdisk image is not part of the kernel distribution; you must provide one yourself. Loopback device support CONFIG_BLK_DEV_LOOP Saying Y here will allow you to use a regular file as a block device; you can then create a file system on that block device and mount it just as you would mount other block devices such as hard drive partitions, CD-ROM drives or floppy drives. The loop devices are block special device files with major number 7 and typically called /dev/loop0, /dev/loop1 etc. This is useful if you want to check an ISO 9660 file system before burning the CD, or if you want to use floppy images without first writing them to floppy. Furthermore, some Linux distributions avoid the need for a dedicated Linux partition by keeping their complete root file system inside a DOS FAT file using this loop device driver. The loop device driver can also be used to "hide" a file system in a disk partition, floppy, or regular file, either using encryption (scrambling the data) or steganography (hiding the data in the low bits of, say, a sound file). This is also safe if the file resides on a remote file server. If you want to do this, you will first have to acquire and install a kernel patch from , and then you need to say Y to this option. Note that alternative ways to use encrypted file systems are provided by the cfs package, which can be gotten from , and the newer tcfs package, available at . You do not need to say Y here if you want to use one of these. However, using cfs requires saying Y to "NFS file system support" below while using tcfs requires applying a kernel patch. An alternative steganography solution is provided by StegFS, also available from . To use the loop device, you need the losetup utility and a recent version of the mount program, both contained in the util-linux package. The location and current version number of util-linux is contained in the file . Note that this loop device has nothing to do with the loopback device used for network connections from the machine to itself. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called loop.o. Most users will answer N here. Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL) CONFIG_BLK_DEV_UMEM Saying Y here will include support for the MM5415 family of battery backed (Non-volatile) RAM cards. The cards appear as block devices that can be partitioned into as many as 15 partitions. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called umem.o. The umem driver has been allocated block major number 116. See Documentation/devices.txt for recommended device naming. Network block device support CONFIG_BLK_DEV_NBD Saying Y here will allow your computer to be a client for network block devices, i.e. it will be able to use block devices exported by servers (mount file systems on them etc.). Communication between client and server works over TCP/IP networking, but to the client program this is hidden: it looks like a regular local file access to a block device special file such as /dev/nd0. Network block devices also allows you to run a block-device in userland (making server and client physically the same computer, communicating using the loopback network device). Read for more information, especially about where to find the server code, which runs in user space and does not need special kernel support. Note that this has nothing to do with the network file systems NFS or Coda; you can say N here even if you intend to use NFS or Coda. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called nbd.o. If unsure, say N. Per partition statistics in /proc/partitions CONFIG_BLK_STATS If you say yes here, your kernel will keep statistical information for every partition. The information includes things as numbers of read and write accesses, the number of merged requests etc. This is required for the full functionality of sar(8) and interesting if you want to do performance tuning, by tweaking the elevator, e.g. If unsure, say N. ATA/IDE/MFM/RLL support CONFIG_IDE If you say Y here, your kernel will be able to manage low cost mass storage units such as ATA/(E)IDE and ATAPI units. The most common cases are IDE hard drives and ATAPI CD-ROM drives. If your system is pure SCSI and doesn't use these interfaces, you can say N here. Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard for mass storage units such as hard disks. It was designed by Western Digital and Compaq Computer in 1984. It was then named ST506. Quite a number of disks use the IDE interface. AT Attachment (ATA) is the superset of the IDE specifications. ST506 was also called ATA-1. Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is ATA-3. It provides support for larger disks (up to 8.4GB by means of the LBA standard), more disks (4 instead of 2) and for other mass storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is ATA-4 and provides faster (and more CPU friendly) transfer modes than previous PIO (Programmed processor Input/Output) from previous ATA/IDE standards by means of fast DMA controllers. ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and CD-ROM drives, similar in many respects to the SCSI protocol. SMART IDE (Self Monitoring, Analysis and Reporting Technology) was designed in order to prevent data corruption and disk crash by detecting pre hardware failure conditions (heat, access time, and the like...). Disks built since June 1995 may follow this standard. The kernel itself don't manage this; however there are quite a number of user programs such as smart that can query the status of SMART parameters disk. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ide.o. For further information, please read . If unsure, say Y. Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support CONFIG_BLK_DEV_IDE If you say Y here, you will use the full-featured IDE driver to control up to ten ATA/IDE interfaces, each being able to serve a "master" and a "slave" device, for a total of up to twenty ATA/IDE disk/cdrom/tape/floppy drives. Useful information about large (>540 MB) IDE disks, multiple interfaces, what to do if ATA/IDE devices are not automatically detected, sound card ATA/IDE ports, module support, and other topics, is contained in . For detailed information about hard drives, consult the Disk-HOWTO and the Multi-Disk-HOWTO, available from . To fine-tune ATA/IDE drive/interface parameters for improved performance, look for the hdparm package at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read and . The module will be called ide-mod.o. Do not compile this driver as a module if your root file system (the one containing the directory /) is located on an IDE device. If you have one or more IDE drives, say Y or M here. If your system has no IDE drives, or if memory requirements are really tight, you could say N here, and select the "Old hard disk driver" below instead to save about 13 KB of memory in the kernel. Old hard disk (MFM/RLL/IDE) driver CONFIG_BLK_DEV_HD_ONLY There are two drivers for MFM/RLL/IDE hard disks. Most people use the newer enhanced driver, but this old one is still around for two reasons. Some older systems have strange timing problems and seem to work only with the old driver (which itself does not work with some newer systems). The other reason is that the old driver is smaller, since it lacks the enhanced functionality of the new one. This makes it a good choice for systems with very tight memory restrictions, or for systems with only older MFM/RLL/ESDI drives. Choosing the old driver can save 13 KB or so of kernel memory. If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver instead of this one. For more detailed information, read the Disk-HOWTO, available from . Use old disk-only driver on primary interface CONFIG_BLK_DEV_HD_IDE There are two drivers for MFM/RLL/IDE disks. Most people use just the new enhanced driver by itself. This option however installs the old hard disk driver to control the primary IDE/disk interface in the system, leaving the new enhanced IDE driver to take care of only the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from having an IDE/ATAPI CD-ROM or tape drive connected to the primary IDE interface. Choosing this option may be useful for older systems which have MFM/RLL/ESDI controller+drives at the primary port address (0x1f0), along with IDE drives at the secondary/3rd/4th port addresses. Normally, just say N here; you will then use the new driver for all 4 interfaces. Include IDE/ATA-2 DISK support CONFIG_BLK_DEV_IDEDISK This will include enhanced support for MFM/RLL/IDE hard disks. If you have a MFM/RLL/IDE disk, and there is no special reason to use the old hard disk driver instead, say Y. If you have an SCSI-only system, you can say N here. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ide-disk.o. Do not compile this driver as a module if your root file system (the one containing the directory /) is located on the IDE disk. If unsure, say Y. Use multi-mode by default CONFIG_IDEDISK_MULTI_MODE If you get this error, try to say Y here: hda: set_multmode: status=0x51 { DriveReady SeekComplete Error } hda: set_multmode: error=0x04 { DriveStatusError } If in doubt, say N. PCMCIA IDE support CONFIG_BLK_DEV_IDECS Support for outboard IDE disks, tape drives, and CD-ROM drives connected through a PCMCIA card. 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 . The module will be called ide-cs.o Include IDE/ATAPI CD-ROM support CONFIG_BLK_DEV_IDECD If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is a newer protocol used by IDE CD-ROM and TAPE drives, similar to the SCSI protocol. Most new CD-ROM drives use ATAPI, including the NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI double(2X) or better speed drives. If you say Y here, the CD-ROM drive will be identified at boot time along with other IDE devices, as "hdb" or "hdc", or something similar (check the boot messages with dmesg). If this is your only CD-ROM drive, you can say N to all other CD-ROM options, but be sure to say Y or M to "ISO 9660 CD-ROM file system support". Note that older versions of LILO (LInux LOader) cannot properly deal with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from . If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ide-cd.o. Include IDE/ATAPI TAPE support CONFIG_BLK_DEV_IDETAPE If you have an IDE tape drive using the ATAPI protocol, say Y. ATAPI is a newer protocol used by IDE tape and CD-ROM drives, similar to the SCSI protocol. If you have an SCSI tape drive however, you can say N here. You should also say Y if you have an OnStream DI-30 tape drive; this will not work with the SCSI protocol, until there is support for the SC-30 and SC-50 versions. If you say Y here, the tape drive will be identified at boot time along with other IDE devices, as "hdb" or "hdc", or something similar, and will be mapped to a character device such as "ht0" (check the boot messages with dmesg). Be sure to consult the and files for usage information. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ide-tape.o. Include IDE/ATAPI FLOPPY support CONFIG_BLK_DEV_IDEFLOPPY If you have an IDE floppy drive which uses the ATAPI protocol, answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy drives, similar to the SCSI protocol. The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by this driver. For information about jumper settings and the question of when a ZIP drive uses a partition table, see . (ATAPI PD-CD/CDR drives are not supported by this driver; support for PD-CD/CDR drives is available if you answer Y to "SCSI emulation support", below). If you say Y here, the FLOPPY drive will be identified along with other IDE devices, as "hdb" or "hdc", or something similar (check the boot messages with dmesg). If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ide-floppy.o. AWARD Bios Work-Around CONFIG_IDEDISK_STROKE Should you have a system w/ an AWARD Bios and your drives are larger than 32GB and it will not boot, one is required to perform a few OEM operations first. The option is called "STROKE" because it allows one to "soft clip" the drive to work around a barrier limit. For Maxtor drives it is called "jumpon.exe". Please search Maxtor's web-site for "JUMPON.EXE". IBM has a similar tool at: . If you are unsure, say N here. Raw Access to Media CONFIG_IDE_TASK_IOCTL This is a direct raw access to the media. It is a complex but elegant solution to test and validate the domain of the hardware and perform below the driver data recover if needed. This is the most basic form of media-forensics. If you are unsure, say N here. Use Taskfile I/O CONFIG_IDE_TASKFILE_IO This is the "Jewel" of the patch. It will go away and become the new driver core. Since all the chipsets/host side hardware deal w/ their exceptions in "their local code" currently, adoption of a standardized data-transport is the only logical solution. Additionally we packetize the requests and gain rapid performance and a reduction in system latency. Additionally by using a memory struct for the commands we can redirect to a MMIO host hardware in the next generation of controllers, specifically second generation Ultra133 and Serial ATA. Since this is a major transition, it was deemed necessary to make the driver paths buildable in separate models. Therefore if using this option fails for your arch then we need to address the needs for that arch. If you want to test this functionality, say Y here. Force DMA CONFIG_BLK_DEV_IDEDMA_FORCED This is an old piece of lost code from Linux 2.0 Kernels. Generally say N here. DMA Only on Disks CONFIG_IDEDMA_ONLYDISK This is used if you know your ATAPI Devices are going to fail DMA Transfers. Generally say N here. SCSI emulation support CONFIG_BLK_DEV_IDESCSI This will provide SCSI host adapter emulation for IDE ATAPI devices, and will allow you to use a SCSI device driver instead of a native ATAPI driver. This is useful if you have an ATAPI device for which no native driver has been written (for example, an ATAPI PD-CD or CDR drive); you can then use this emulation together with an appropriate SCSI device driver. In order to do this, say Y here and to "SCSI support" and "SCSI generic support", below. You must then provide the kernel command line "hdx=scsi" (try "man bootparam" or see the documentation of your boot loader (lilo or loadlin) about how to pass options to the kernel at boot time) for devices if you want the native EIDE sub-drivers to skip over the native support, so that this SCSI emulation can be used instead. This is required for use of CD-RW's. Note that this option does NOT allow you to attach SCSI devices to a box that doesn't have a SCSI host adapter installed. If both this SCSI emulation and native ATAPI support are compiled into the kernel, the native support will be used. 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 . The module will be called ide-scsi.o Use the NOOP Elevator (WARNING) CONFIG_BLK_DEV_ELEVATOR_NOOP If you are using a raid class top-level driver above the ATA/IDE core, one may find a performance boost by preventing a merging and re-sorting of the new requests. If unsure, say N. ISA-PNP EIDE support CONFIG_BLK_DEV_ISAPNP If you have an ISA EIDE card that is PnP (Plug and Play) and requires setup first before scanning for devices, say Y here. If unsure, say N. CMD640 chipset bugfix/support CONFIG_BLK_DEV_CMD640 The CMD-Technologies CMD640 IDE chip is used on many common 486 and Pentium motherboards, usually in combination with a "Neptune" or "SiS" chipset. Unfortunately, it has a number of rather nasty design flaws that can cause severe data corruption under many common conditions. Say Y here to include code which tries to automatically detect and correct the problems under Linux. This option also enables access to the secondary IDE ports in some CMD640 based systems. This driver will work automatically in PCI based systems (most new systems have PCI slots). But if your system uses VESA local bus (VLB) instead of PCI, you must also supply a kernel boot parameter to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man bootparam" or see the documentation of your boot loader about how to pass options to the kernel.) The CMD640 chip is also used on add-in cards by Acculogic, and on the "CSA-6400E PCI to IDE controller" that some people have. For details, read . CMD640 enhanced support CONFIG_BLK_DEV_CMD640_ENHANCED This option includes support for setting/autotuning PIO modes and prefetch on CMD640 IDE interfaces. For details, read . If you have a CMD640 IDE interface and your BIOS does not already do this for you, then say Y here. Otherwise say N. RZ1000 chipset bugfix/support CONFIG_BLK_DEV_RZ1000 The PC-Technologies RZ1000 IDE chip is used on many common 486 and Pentium motherboards, usually along with the "Neptune" chipset. Unfortunately, it has a rather nasty design flaw that can cause severe data corruption under many conditions. Say Y here to include code which automatically detects and corrects the problem under Linux. This may slow disk throughput by a few percent, but at least things will operate 100% reliably. Generic PCI IDE chipset support CONFIG_BLK_DEV_IDEPCI Say Y here for PCI systems which use IDE drive(s). This option helps the IDE driver to automatically detect and configure all PCI-based IDE interfaces in your system. Support for sharing PCI IDE interrupts CONFIG_IDEPCI_SHARE_IRQ Some ATA/IDE chipsets have hardware support which allows for sharing a single IRQ with other cards. To enable support for this in the ATA/IDE driver, say Y here. It is safe to say Y to this question, in most cases. If unsure, say N. Generic PCI bus-master DMA support CONFIG_BLK_DEV_IDEDMA_PCI If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and is capable of bus-master DMA operation (most Pentium PCI systems), you will want to say Y here to reduce CPU overhead. You can then use the "hdparm" utility to enable DMA for drives for which it was not enabled automatically. By default, DMA is not enabled automatically for these drives, but you can change that by saying Y to the following question "Use DMA by default when available". You can get the latest version of the hdparm utility from . Read the comments at the beginning of and the file for more information. It is safe to say Y to this question. Good-Bad DMA Model-Firmware (WIP) CONFIG_IDEDMA_NEW_DRIVE_LISTINGS If you say Y here, the model and firmware revision of your drive will be compared against a blacklist of buggy drives that claim to be (U)DMA capable but aren't. This is a blanket on/off test with no speed limit options. Straight GNU GCC 2.7.3/2.8.X compilers are known to be safe; whereas, many versions of EGCS have a problem and miscompile if you say Y here. If in doubt, say N. Attempt to HACK around Chipsets that TIMEOUT (WIP) CONFIG_BLK_DEV_IDEDMA_TIMEOUT If you say Y here, this is a NASTY UGLY HACK! We have to issue an abort and requeue the request DMA engine got turned off by a goofy ASIC, and we have to clean up the mess, and here is as good as any. Do it globally for all chipsets. If in doubt, say N. Boot off-board chipsets first support CONFIG_BLK_DEV_OFFBOARD Normally, IDE controllers built into the motherboard (on-board controllers) are assigned to ide0 and ide1 while those on add-in PCI cards (off-board controllers) are relegated to ide2 and ide3. Answering Y here will allow you to reverse the situation, with off-board controllers on ide0/1 and on-board controllers on ide2/3. This can improve the usability of some boot managers such as lilo when booting from a drive on an off-board controller. If you say Y here, and you actually want to reverse the device scan order as explained above, you also need to issue the kernel command line option "ide=reverse". (Try "man bootparam" or see the documentation of your boot loader (lilo or loadlin) about how to pass options to the kernel at boot time.) Note that, if you do this, the order of the hd* devices will be rearranged which may require modification of fstab and other files. If in doubt, say N. Use PCI DMA by default when available CONFIG_IDEDMA_PCI_AUTO Prior to kernel version 2.1.112, Linux used to automatically use DMA for IDE drives and chipsets which support it. Due to concerns about a couple of cases where buggy hardware may have caused damage, the default is now to NOT use DMA automatically. To revert to the previous behaviour, say Y to this question. If you suspect your hardware is at all flakey, say N here. Do NOT email the IDE kernel people regarding this issue! It is normally safe to answer Y to this question unless your motherboard uses a VIA VP2 chipset, in which case you should say N. IGNORE word93 Validation BITS CONFIG_IDEDMA_IVB There are unclear terms in ATA-4 and ATA-5 standards how certain hardware (an 80c ribbon) should be detected. Different interpretations of the standards have been released in hardware. This causes problems: for example, a host with Ultra Mode 4 (or higher) will not run in that mode with an 80c ribbon. If you are experiencing compatibility or performance problems, you MAY try to answering Y here. However, it does not necessarily solve any of your problems, it could even cause more of them. It is normally safe to answer Y; however, the default is N. ATA Work(s) In Progress (EXPERIMENTAL) CONFIG_IDEDMA_PCI_WIP If you enable this you will be able to use and test highly developmental projects. If you say N, the configurator will simply skip those options. It is SAFEST to say N to this question. Asynchronous DMA support (EXPERIMENTAL) CONFIG_BLK_DEV_ADMA Please read the comments at the top of . Pacific Digital A-DMA support (EXPERIMENTAL) CONFIG_BLK_DEV_PDC_ADMA Please read the comments at the top of . 3ware Hardware ATA-RAID support CONFIG_BLK_DEV_3W_XXXX_RAID 3ware is the only hardware ATA-Raid product in Linux to date. This card is 2,4, or 8 channel master mode support only. SCSI support required!!! Please read the comments at the top of . If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called 3w-xxxx.o. AEC62XX chipset support CONFIG_BLK_DEV_AEC62XX This driver adds up to 4 more EIDE devices sharing a single interrupt. This add-on card is a bootable PCI UDMA controller. In order to get this card to initialize correctly in some cases, you should say Y here, and preferably also to "Use DMA by default when available". The ATP850U/UF is an UltraDMA 33 chipset base. The ATP860 is an UltraDMA 66 chipset base. The ATP860M(acintosh) version is an UltraDMA 66 chipset base. Please read the comments at the top of . If you say Y here, then say Y to "Use DMA by default when available" as well. AEC62XX Tuning support CONFIG_AEC62XX_TUNING Please read the comments at the top of . If unsure, say N. ALI M15x3 chipset support CONFIG_BLK_DEV_ALI15X3 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C onboard chipsets. It also tests for Simplex mode and enables normal dual channel support. If you say Y here, you also need to say Y to "Use DMA by default when available", above. Please read the comments at the top of . If unsure, say N. ALI M15x3 WDC support (DANGEROUS) CONFIG_WDC_ALI15X3 This allows for UltraDMA support for WDC drives that ignore CRC checking. You are a fool for enabling this option, but there have been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF YOU ENABLE THIS! No one will listen, just laugh for ignoring this SERIOUS WARNING. Using this option can allow WDC drives to run at ATA-4/5 transfer rates with only an ATA-2 support structure. SAY N! AMD Viper (7401/7409/7411) chipset support CONFIG_BLK_DEV_AMD74XX This driver ensures (U)DMA support for the AMD756/760 Viper chipsets. If you say Y here, you also need to say Y to "Use DMA by default when available", above. Please read the comments at the top of . If unsure, say N. AMD Viper ATA-66 Override support (WIP) CONFIG_AMD74XX_OVERRIDE This option auto-forces the ata66 flag. This effect can be also invoked by calling "idex=ata66" If unsure, say N. CMD64X and CMD680 chipset support CONFIG_BLK_DEV_CMD64X Say Y here if you have an IDE controller which uses any of these chipsets: CMD643, CMD646, CMD648, CMD649 or CMD680. CY82C693 chipset support CONFIG_BLK_DEV_CY82C693 This driver adds detection and support for the CY82C693 chipset used on Digital's PC-Alpha 164SX boards. If you say Y here, you need to say Y to "Use DMA by default when available" as well. Cyrix CS5530 MediaGX chipset support CONFIG_BLK_DEV_CS5530 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This will automatically be detected and configured if found. It is safe to say Y to this question. People with SCSI-only systems should say N here. If unsure, say Y. HPT34X chipset support CONFIG_BLK_DEV_HPT34X This driver adds up to 4 more EIDE devices sharing a single interrupt. The HPT343 chipset in its current form is a non-bootable controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX) PCI UDMA controllers. This driver requires dynamic tuning of the chipset during the ide-probe at boot time. It is reported to support DVD II drives, by the manufacturer. HPT34X AUTODMA support (WIP) CONFIG_HPT34X_AUTODMA This is a dangerous thing to attempt currently! Please read the comments at the top of . If you say Y here, then say Y to "Use DMA by default when available" as well. If unsure, say N. HPT366/368/370 chipset support CONFIG_BLK_DEV_HPT366 HPT366 is an Ultra DMA chipset for ATA-66. HPT368 is an Ultra DMA chipset for ATA-66 RAID Based. HPT370 is an Ultra DMA chipset for ATA-100. This driver adds up to 4 more EIDE devices sharing a single interrupt. The HPT366 chipset in its current form is bootable. One solution for this problem are special LILO commands for redirecting the reference to device 0x80. The other solution is to say Y to "Boot off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless your mother board has the chipset natively mounted. Regardless one should use the fore mentioned option and call at LILO or include "ide=reverse" in LILO's append-line. This driver requires dynamic tuning of the chipset during the ide-probe at boot. It is reported to support DVD II drives, by the manufacturer. NS87415 chipset support (EXPERIMENTAL) CONFIG_BLK_DEV_NS87415 This driver adds detection and support for the NS87415 chip (used in SPARC64, among others). Please read the comments at the top of . OPTi 82C621 chipset enhanced support (EXPERIMENTAL) CONFIG_BLK_DEV_OPTI621 This is a driver for the OPTi 82C621 EIDE controller. Please read the comments at the top of . ServerWorks OSB4/CSB5 chipset support CONFIG_BLK_DEV_SVWKS This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5 chipsets. Intel PIIXn chipsets support CONFIG_BLK_DEV_PIIX This driver adds PIO mode setting and tuning for all PIIX IDE controllers by Intel. Since the BIOS can sometimes improperly tune PIO 0-4 mode settings, this allows dynamic tuning of the chipset via the standard end-user tool 'hdparm'. Please read the comments at the top of . If you say Y here, you should also say Y to "PIIXn Tuning support", below. If unsure, say N. PIIXn Tuning support CONFIG_PIIX_TUNING This driver extension adds DMA mode setting and tuning for all PIIX IDE controllers by Intel. Since the BIOS can sometimes improperly set up the device/adapter combination and speed limits, it has become a necessity to back/forward speed devices as needed. Case 430HX/440FX PIIX3 need speed limits to reduce UDMA to DMA mode 2 if the BIOS can not perform this task at initialization. If unsure, say N. PROMISE PDC20246/PDC20262/PDC20265/PDC20267/PDC20268 support CONFIG_BLK_DEV_PDC202XX Promise Ultra33 or PDC20246 Promise Ultra66 or PDC20262 Promise Ultra100 or PDC20265/PDC20267/PDC20268 This driver adds up to 4 more EIDE devices sharing a single interrupt. This add-on card is a bootable PCI UDMA controller. Since multiple cards can be installed and there are BIOS ROM problems that happen if the BIOS revisions of all installed cards (three-max) do not match, the driver attempts to do dynamic tuning of the chipset at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required for more than one card. This card may require that you say Y to "Special UDMA Feature". If you say Y here, you need to say Y to "Use DMA by default when available" as well. Please read the comments at the top of . If unsure, say N. Special UDMA Feature CONFIG_PDC202XX_BURST This option causes the pdc202xx driver to enable UDMA modes on the PDC202xx even when the PDC202xx BIOS has not done so. It was originally designed for the PDC20246/Ultra33, whose BIOS will only setup UDMA on the first two PDC20246 cards. It has also been used successfully on a PDC20265/Ultra100, allowing use of UDMA modes when the PDC20265 BIOS has been disabled (for faster boot up). Please read the comments at the top of . If unsure, say N. Special FastTrak Feature CONFIG_PDC202XX_FORCE For FastTrak enable overriding BIOS. SiS5513 chipset support CONFIG_BLK_DEV_SIS5513 This driver ensures (U)DMA support for SIS5513 chipset family based mainboards. The following chipsets are supported: ATA16: SiS5511, SiS5513 ATA33: SiS5591, SiS5597, SiS5598, SiS5600 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740, SiS745, SiS750 If you say Y here, you need to say Y to "Use DMA by default when available" as well. Please read the comments at the top of . SLC90E66 chipset support CONFIG_BLK_DEV_SLC90E66 This driver ensures (U)DMA support for Victroy66 SouthBridges for SMsC with Intel NorthBridges. This is an Ultra66 based chipset. The nice thing about it is that you can mix Ultra/DMA/PIO devices and it will handle timing cycles. Since this is an improved look-a-like to the PIIX4 it should be a nice addition. If you say Y here, you need to say Y to "Use DMA by default when available" as well. Please read the comments at the top of . Winbond SL82c105 support CONFIG_BLK_DEV_SL82C105 If you have a Winbond SL82c105 IDE controller, say Y here to enable special configuration for this chip. This is common on various CHRP motherboards, but could be used elsewhere. If in doubt, say Y. Tekram TRM290 chipset support CONFIG_BLK_DEV_TRM290 This driver adds support for bus master DMA transfers using the Tekram TRM290 PCI IDE chip. Volunteers are needed for further tweaking and development. Please read the comments at the top of . VIA82CXXX chipset support CONFIG_BLK_DEV_VIA82CXXX This allows you to configure your chipset for a better use while running PIO/(U)DMA, it will allow you to enable efficiently the second channel dma usage, as it may not be set by BIOS. It will try to set fifo configuration at its best. It will allow you to get information from /proc/ide/via provided you enabled "/proc file system" support. Please read the comments at the top of . If you say Y here, then say Y to "Use DMA by default when available" as well. If unsure, say N. RapIDE interface support CONFIG_BLK_DEV_IDE_RAPIDE Say Y here if you want to support the Yellowstone RapIDE controller manufactured for use with Acorn computers. Other IDE chipset support CONFIG_IDE_CHIPSETS Say Y here if you want to include enhanced support for various IDE interface chipsets used on motherboards and add-on cards. You can then pick your particular IDE chip from among the following options. This enhanced support may be necessary for Linux to be able to access the 3rd/4th drives in some systems. It may also enable setting of higher speed I/O rates to improve system performance with these chipsets. Most of these also require special kernel boot parameters to actually turn on the support at runtime; you can find a list of these in the file . People with SCSI-only systems can say N here. Generic 4 drives/port support CONFIG_BLK_DEV_4DRIVES Certain older chipsets, including the Tekram 690CD, use a single set of I/O ports at 0x1f0 to control up to four drives, instead of the customary two drives per port. Support for this can be enabled at runtime using the "ide0=four" kernel boot parameter if you say Y here. ALI M14xx support CONFIG_BLK_DEV_ALI14XX This driver is enabled at runtime using the "ide0=ali14xx" kernel boot parameter. It enables support for the secondary IDE interface of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster I/O speeds to be set as well. See the files and for more info. DTC-2278 support CONFIG_BLK_DEV_DTC2278 This driver is enabled at runtime using the "ide0=dtc2278" kernel boot parameter. It enables support for the secondary IDE interface of the DTC-2278 card, and permits faster I/O speeds to be set as well. See the and files for more info. Holtek HT6560B support CONFIG_BLK_DEV_HT6560B This driver is enabled at runtime using the "ide0=ht6560b" kernel boot parameter. It enables support for the secondary IDE interface of the Holtek card, and permits faster I/O speeds to be set as well. See the and files for more info. PROMISE DC4030 support (EXPERIMENTAL) CONFIG_BLK_DEV_PDC4030 This driver provides support for the secondary IDE interface and cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver is known to incur timeouts/retries during heavy I/O to drives attached to the secondary interface. CD-ROM and TAPE devices are not supported yet. This driver is enabled at runtime using the "ide0=dc4030" kernel boot parameter. See the and files for more info. QDI QD65XX support CONFIG_BLK_DEV_QD65XX This driver is enabled at runtime using the "ide0=qd65xx" kernel boot parameter. It permits faster I/O speeds to be set. See the and for more info. UMC 8672 support CONFIG_BLK_DEV_UMC8672 This driver is enabled at runtime using the "ide0=umc8672" kernel boot parameter. It enables support for the secondary IDE interface of the UMC-8672, and permits faster I/O speeds to be set as well. See the files and for more info. Amiga Gayle IDE interface support CONFIG_BLK_DEV_GAYLE This is the IDE driver for the builtin IDE interface on some Amiga models. It supports both the `A1200 style' (used in A600 and A1200) and `A4000 style' (used in A4000 and A4000T) of the Gayle IDE interface. Say Y if you have such an Amiga model and want to use IDE devices (hard disks, CD-ROM drives, etc.) that are connected to the builtin IDE interface. Falcon IDE interface support CONFIG_BLK_DEV_FALCON_IDE This is the IDE driver for the builtin IDE interface on the Atari Falcon. Say Y if you have a Falcon and want to use IDE devices (hard disks, CD-ROM drives, etc.) that are connected to the builtin IDE interface. Amiga Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL) CONFIG_BLK_DEV_BUDDHA This is the IDE driver for the IDE interfaces on the Buddha, Catweasel and X-Surf expansion boards. It supports up to two interfaces on the Buddha, three on the Catweasel and two on the X-Surf. Say Y if you have a Buddha or Catweasel expansion board and want to use IDE devices (hard disks, CD-ROM drives, etc.) that are connected to one of its IDE interfaces. Amiga IDE Doubler support (EXPERIMENTAL) CONFIG_BLK_DEV_IDEDOUBLER This driver provides support for the so-called `IDE doublers' (made by various manufacturers, e.g. Eyetech) that can be connected to the builtin IDE interface of some Amiga models. Using such an IDE doubler, you can connect up to four instead of two IDE devices on the Amiga's builtin IDE interface. Note that the normal Amiga Gayle IDE driver may not work correctly if you have an IDE doubler and don't enable this driver! Say Y if you have an IDE doubler. The driver is enabled at kernel runtime using the "ide=doubler" kernel boot parameter. WarpEngine SCSI support CONFIG_WARPENGINE_SCSI Support for MacroSystem Development's WarpEngine Amiga SCSI-2 controller. Info at . Builtin PowerMac IDE support CONFIG_BLK_DEV_IDE_PMAC This driver provides support for the built-in IDE controller on most of the recent Apple Power Macintoshes and PowerBooks. If unsure, say Y. PowerMac IDE DMA support CONFIG_BLK_DEV_IDEDMA_PMAC This option allows the driver for the built-in IDE controller on Power Macintoshes and PowerBooks to use DMA (direct memory access) to transfer data to and from memory. Saying Y is safe and improves performance. Use DMA by default CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO This option allows the driver for the built-in IDE controller on Power Macintoshes and PowerBooks to use DMA automatically, without it having to be explicitly enabled. This option is provided because of concerns about a couple of cases where using DMA on buggy PC hardware may have caused damage. Saying Y should be safe on all Apple machines. Macintosh Quadra/Powerbook IDE interface support CONFIG_BLK_DEV_MAC_IDE This is the IDE driver for the builtin IDE interface on some m68k Macintosh models. It supports both the `Quadra style' (used in Quadra/ Centris 630 and Performa 588 models) and `Powerbook style' (used in the Powerbook 150 and 190 models) IDE interface. Say Y if you have such an Macintosh model and want to use IDE devices (hard disks, CD-ROM drives, etc.) that are connected to the builtin IDE interface. ICS IDE interface support CONFIG_BLK_DEV_IDE_ICSIDE On Acorn systems, say Y here if you wish to use the ICS IDE interface card. This is not required for ICS partition support. If you are unsure, say N to this. ICS DMA support CONFIG_BLK_DEV_IDEDMA_ICS Say Y here if you want to add DMA (Direct Memory Access) support to the ICS IDE driver. Use ICS DMA by default CONFIG_IDEDMA_ICS_AUTO Prior to kernel version 2.1.112, Linux used to automatically use DMA for IDE drives and chipsets which support it. Due to concerns about a couple of cases where buggy hardware may have caused damage, the default is now to NOT use DMA automatically. To revert to the previous behaviour, say Y to this question. If you suspect your hardware is at all flakey, say N here. Do NOT email the IDE kernel people regarding this issue! XT hard disk support CONFIG_BLK_DEV_XD Very old 8 bit hard disk controllers used in the IBM XT computer will be supported if you say Y here. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called xd.o. It's pretty unlikely that you have one of these: say N. PS/2 ESDI hard disk support CONFIG_BLK_DEV_PS2 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI hard disk. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ps2esdi.o. Mylex DAC960/DAC1100 PCI RAID Controller support CONFIG_BLK_DEV_DAC960 This driver adds support for the Mylex DAC960, AcceleRAID, and eXtremeRAID PCI RAID controllers. See the file for further information about this driver. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called DAC960.o. Parallel port IDE device support CONFIG_PARIDE There are many external CD-ROM and disk devices that connect through your computer's parallel port. Most of them are actually IDE devices using a parallel port IDE adapter. This option enables the PARIDE subsystem which contains drivers for many of these external drives. Read for more information. If you have said Y to the "Parallel-port support" configuration option, you may share a single port between your printer and other parallel port devices. Answer Y to build PARIDE support into your kernel, or M if you would like to build it as a loadable module. If your parallel port support is in a loadable module, you must build PARIDE as a module. If you built PARIDE support into your kernel, you may still build the individual protocol modules and high-level drivers as loadable modules. If you build this support as a module, it will be called paride.o. To use the PARIDE support, you must say Y or M here and also to at least one high-level driver (e.g. "Parallel port IDE disks", "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and to at least one protocol driver (e.g. "ATEN EH-100 protocol", "MicroSolutions backpack protocol", "DataStor Commuter protocol" etc.). Parallel port IDE disks CONFIG_PARIDE_PD This option enables the high-level driver for IDE-type disk devices connected through a parallel port. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the parallel port IDE driver, otherwise you should answer M to build it as a loadable module. The module will be called pd.o. You must also have at least one parallel port protocol driver in your system. Among the devices supported by this driver are the SyQuest EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack hard drives from MicroSolutions. Parallel port ATAPI CD-ROMs CONFIG_PARIDE_PCD This option enables the high-level driver for ATAPI CD-ROM devices connected through a parallel port. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the parallel port ATAPI CD-ROM driver, otherwise you should answer M to build it as a loadable module. The module will be called pcd.o. You must also have at least one parallel port protocol driver in your system. Among the devices supported by this driver are the MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If you have such a CD-ROM drive, you should also say Y or M to "ISO 9660 CD-ROM file system support" below, because that's the file system used on CD-ROMs. Parallel port ATAPI disks CONFIG_PARIDE_PF This option enables the high-level driver for ATAPI disk devices connected through a parallel port. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the parallel port ATAPI disk driver, otherwise you should answer M to build it as a loadable module. The module will be called pf.o. You must also have at least one parallel port protocol driver in your system. Among the devices supported by this driver are the MicroSolutions backpack PD/CD drive and the Imation Superdisk LS-120 drive. Parallel port ATAPI tapes CONFIG_PARIDE_PT This option enables the high-level driver for ATAPI tape devices connected through a parallel port. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the parallel port ATAPI disk driver, otherwise you should answer M to build it as a loadable module. The module will be called pt.o. You must also have at least one parallel port protocol driver in your system. Among the devices supported by this driver is the parallel port version of the HP 5GB drive. Parallel port generic ATAPI devices CONFIG_PARIDE_PG This option enables a special high-level driver for generic ATAPI devices connected through a parallel port. The driver allows user programs, such as cdrtools, to send ATAPI commands directly to a device. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the parallel port generic ATAPI driver, otherwise you should answer M to build it as a loadable module. The module will be called pg.o. You must also have at least one parallel port protocol driver in your system. This driver implements an API loosely related to the generic SCSI driver. See . for details. You can obtain the most recent version of cdrtools from . Versions 1.6.1a3 and later fully support this driver. ATEN EH-100 protocol CONFIG_PARIDE_ATEN This option enables support for the ATEN EH-100 parallel port IDE protocol. This protocol is used in some inexpensive low performance parallel port kits made in Hong Kong. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called aten.o. You must also have a high-level driver for the type of device that you want to support. Micro Solutions BACKPACK Series 5 protocol CONFIG_PARIDE_BPCK This option enables support for the Micro Solutions BACKPACK parallel port Series 5 IDE protocol. (Most BACKPACK drives made before 1999 were Series 5) Series 5 drives will NOT always have the Series noted on the bottom of the drive. Series 6 drivers will. In other words, if your BACKPACK drive dosen't say "Series 6" on the bottom, enable this option. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called bpck.o. You must also have a high-level driver for the type of device that you want to support. Micro Solutions BACKPACK Series 6 protocol CONFIG_PARIDE_BPCK6 This option enables support for the Micro Solutions BACKPACK parallel port Series 6 IDE protocol. (Most BACKPACK drives made after 1999 were Series 6) Series 6 drives will have the Series noted on the bottom of the drive. Series 5 drivers don't always have it noted. In other words, if your BACKPACK drive says "Series 6" on the bottom, enable this option. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called bpck6.o. You must also have a high-level driver for the type of device that you want to support. DataStor Commuter protocol CONFIG_PARIDE_COMM This option enables support for the Commuter parallel port IDE protocol from DataStor. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called comm.o. You must also have a high-level driver for the type of device that you want to support. DataStor EP-2000 protocol CONFIG_PARIDE_DSTR This option enables support for the EP-2000 parallel port IDE protocol from DataStor. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called dstr.o. You must also have a high-level driver for the type of device that you want to support. Shuttle EPAT/EPEZ protocol CONFIG_PARIDE_EPAT This option enables support for the EPAT parallel port IDE protocol. EPAT is a parallel port IDE adapter manufactured by Shuttle Technology and widely used in devices from major vendors such as Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called epat.o. You must also have a high-level driver for the type of device that you want to support. Shuttle EPAT c7/c8 extension CONFIG_PARIDE_EPATC8 This option enables support for the newer Shuttle EP1284 (aka c7 and c8) chip. You need this if you are using any recent Imation SuperDisk (LS-120) drive. Shuttle EPIA protocol CONFIG_PARIDE_EPIA This option enables support for the (obsolete) EPIA parallel port IDE protocol from Shuttle Technology. This adapter can still be found in some no-name kits. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called epia.o. You must also have a high-level driver for the type of device that you want to support. FIT TD-2000 protocol CONFIG_PARIDE_FIT2 This option enables support for the TD-2000 parallel port IDE protocol from Fidelity International Technology. This is a simple (low speed) adapter that is used in some portable hard drives. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called fit2.o. You must also have a high-level driver for the type of device that you want to support. FIT TD-3000 protocol CONFIG_PARIDE_FIT3 This option enables support for the TD-3000 parallel port IDE protocol from Fidelity International Technology. This protocol is used in newer models of their portable disk, CD-ROM and PD/CD devices. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called fit3.o. You must also have a high-level driver for the type of device that you want to support. Freecom IQ ASIC-2 protocol CONFIG_PARIDE_FRIQ This option enables support for version 2 of the Freecom IQ parallel port IDE adapter. This adapter is used by the Maxell Superdisk drive. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called friq.o. You must also have a high-level driver for the type of device that you want to support. FreeCom power protocol CONFIG_PARIDE_FRPW This option enables support for the Freecom power parallel port IDE protocol. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called frpw.o. You must also have a high-level driver for the type of device that you want to support. KingByte KBIC-951A/971A protocols CONFIG_PARIDE_KBIC This option enables support for the KBIC-951A and KBIC-971A parallel port IDE protocols from KingByte Information Corp. KingByte's adapters appear in many no-name portable disk and CD-ROM products, especially in Europe. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called kbic.o. You must also have a high-level driver for the type of device that you want to support. KT PHd protocol CONFIG_PARIDE_KTTI This option enables support for the "PHd" parallel port IDE protocol from KT Technology. This is a simple (low speed) adapter that is used in some 2.5" portable hard drives. If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called ktti.o. You must also have a high-level driver for the type of device that you want to support. OnSpec 90c20 protocol CONFIG_PARIDE_ON20 This option enables support for the (obsolete) 90c20 parallel port IDE protocol from OnSpec (often marketed under the ValuStore brand name). If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called on20.o. You must also have a high-level driver for the type of device that you want to support. OnSpec 90c26 protocol CONFIG_PARIDE_ON26 This option enables support for the 90c26 parallel port IDE protocol from OnSpec Electronics (often marketed under the ValuStore brand name). If you chose to build PARIDE support into your kernel, you may answer Y here to build in the protocol driver, otherwise you should answer M to build it as a loadable module. The module will be called on26.o. You must also have a high-level driver for the type of device that you want to support. Logical Volume Manager (LVM) support CONFIG_BLK_DEV_LVM This driver lets you combine several hard disks, hard disk partitions, multiple devices or even loop devices (for evaluation purposes) into a volume group. Imagine a volume group as a kind of virtual disk. Logical volumes, which can be thought of as virtual partitions, can be created in the volume group. You can resize volume groups and logical volumes after creation time, corresponding to new capacity needs. Logical volumes are accessed as block devices named /dev/VolumeGroupName/LogicalVolumeName. For details see . You will need supporting user space software; location is in . If you want to compile this support as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called lvm-mod.o. Multiple devices driver support (RAID and LVM) CONFIG_MD Support multiple physical spindles through a single logical device. Required for RAID and logical volume management (LVM). Multiple devices driver support CONFIG_BLK_DEV_MD This driver lets you combine several hard disk partitions into one logical block device. This can be used to simply append one partition to another one or to combine several redundant hard disks into a RAID1/4/5 device so as to provide protection against hard disk failures. This is called "Software RAID" since the combining of the partitions is done by the kernel. "Hardware RAID" means that the combining is done by a dedicated controller; if you have such a controller, you do not need to say Y here. More information about Software RAID on Linux is contained in the Software RAID mini-HOWTO, available from . There you will also learn where to get the supporting user space utilities raidtools. 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 . The module will be called md.o If unsure, say N. Linear (append) mode CONFIG_MD_LINEAR If you say Y here, then your multiple devices driver will be able to use the so-called linear mode, i.e. it will combine the hard disk partitions by simply appending one to the other. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called linear.o. If unsure, say Y. RAID-0 (striping) mode CONFIG_MD_RAID0 If you say Y here, then your multiple devices driver will be able to use the so-called raid0 mode, i.e. it will combine the hard disk partitions into one logical device in such a fashion as to fill them up evenly, one chunk here and one chunk there. This will increase the throughput rate if the partitions reside on distinct disks. Information about Software RAID on Linux is contained in the Software-RAID mini-HOWTO, available from . There you will also learn where to get the supporting user space utilities raidtools. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called raid0.o. If unsure, say Y. RAID-1 (mirroring) mode CONFIG_MD_RAID1 A RAID-1 set consists of several disk drives which are exact copies of each other. In the event of a mirror failure, the RAID driver will continue to use the operational mirrors in the set, providing an error free MD (multiple device) to the higher levels of the kernel. In a set with N drives, the available space is the capacity of a single drive, and the set protects against a failure of (N - 1) drives. Information about Software RAID on Linux is contained in the Software-RAID mini-HOWTO, available from . There you will also learn where to get the supporting user space utilities raidtools. If you want to use such a RAID-1 set, say Y. This code is also available as a module called raid1.o ( = 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 . If unsure, say Y. RAID-4/RAID-5 mode CONFIG_MD_RAID5 A RAID-5 set of N drives with a capacity of C MB per drive provides the capacity of C * (N - 1) MB, and protects against a failure of a single drive. For a given sector (row) number, (N - 1) drives contain data sectors, and one drive contains the parity protection. For a RAID-4 set, the parity blocks are present on a single drive, while a RAID-5 set distributes the parity across the drives in one of the available parity distribution methods. Information about Software RAID on Linux is contained in the Software-RAID mini-HOWTO, available from . There you will also learn where to get the supporting user space utilities raidtools. If you want to use such a RAID-4/RAID-5 set, say Y. This code is also available as a module called raid5.o ( = 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 . If unsure, say Y. Multipath I/O support CONFIG_MD_MULTIPATH Multipath-IO is the ability of certain devices to address the same physical disk over multiple 'IO paths'. The code ensures that such paths can be defined and handled at runtime, and ensures that a transparent failover to the backup path(s) happens if a IO errors arrives on the primary path. 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 . The module will be called multipath.o If unsure, say N. Support for IDE Raid controllers CONFIG_BLK_DEV_ATARAID Say Y or M if you have an IDE Raid controller and want linux to use its softwareraid feature. You must also select an appropriate for your board low-level driver below. Note, that Linux does not use the Raid implementation in BIOS, and the main purpose for this feature is to retain compatibility and data integrity with other OS-es, using the same disk array. Linux has its own Raid drivers, which you should use if you need better performance. 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 . The module will be called ataraid.o Support Promise software RAID (Fasttrak(tm)) CONFIG_BLK_DEV_ATARAID_PDC Say Y or M if you have a Promise Fasttrak (tm) Raid controller and want linux to use the softwareraid feature of this card. This driver uses /dev/ataraid/dXpY (X and Y numbers) as device names. If you choose to compile this as a module, the module will be called pdcraid.o. Highpoint 370 software RAID CONFIG_BLK_DEV_ATARAID_HPT Say Y or M if you have a Highpoint HPT 370 Raid controller and want linux to use the softwareraid feature of this card. This driver uses /dev/ataraid/dXpY (X and Y numbers) as device names. If you choose to compile this as a module, the module will be called hptraid.o. Support for Acer PICA 1 chipset CONFIG_ACER_PICA_61 This is a machine with a R4400 133/150 MHz CPU. To compile a Linux kernel that runs on these, say Y here. For details about Linux on the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at . Support for Algorithmics P4032 (EXPERIMENTAL) CONFIG_ALGOR_P4032 This is an evaluation board of the British company Algorithmics. The board uses the R4300 and a R5230 CPUs. For more information about this board see . Support for BAGET MIPS series CONFIG_BAGET_MIPS This enables support for the Baget, a Russian embedded system. For more details about the Baget see the Linux/MIPS FAQ on . Baget AMD LANCE support CONFIG_BAGETLANCE Say Y to enable kernel support for AMD Lance Ethernet cards on the MIPS-32-based Baget embedded system. This chipset is better known via the NE2100 cards. Support for DECstations CONFIG_DECSTATION This enables support for DEC's MIPS based workstations. For details see the Linux/MIPS FAQ on and the DECstation porting pages on . If you have one of the following DECstation Models you definitely want to choose R4xx0 for the CPU Type: DECstation 5000/50 DECstation 5000/150 DECstation 5000/260 DECsystem 5900/260 otherwise choose R3000. Support for Cobalt Micro Server CONFIG_COBALT_MICRO_SERVER Support for MIPS-based Cobalt boxes (they have been bought by Sun and are now the "Server Appliance Business Unit") including the 2700 series -- versions 1 of the Qube and Raq. To compile a Linux kernel for this hardware, say Y here. Support for Cobalt 2800 CONFIG_COBALT_28 Support for the second generation of MIPS-based Cobalt boxes (they have been bought by Sun and are now the "Server Appliance Business Unit") including the 2800 series -- versions 2 of the Qube and Raq. To compile a Linux kernel for this hardware, say Y here. Support for the Momentum Computer Ocelot SBC CONFIG_MOMENCO_OCELOT The Ocelot is a MIPS-based Single Board Computer (SBC) made by Momentum Computer . Support for NEC DDB Vrc-5074 CONFIG_DDB5074 This enables support for the VR5000-based NEC DDB Vrc-5074 evaluation board. Support for NEC DDB Vrc-5476 CONFIG_DDB5476 This enables support for the R5432-based NEC DDB Vrc-5476 evaluation board. Features : kernel debugging, serial terminal, NFS root fs, on-board ether port (Need an additional patch at ), USB, AC97, PCI, PCI VGA card & framebuffer console, IDE controller, PS2 keyboard, PS2 mouse, etc. Support for NEC DDB Vrc-5477 CONFIG_DDB5477 This enables support for the R5432-based NEC DDB Vrc-5477 evaluation board. Features : kernel debugging, serial terminal, NFS root fs, on-board ether port (Need an additional patch at ), USB, AC97, PCI, etc. Support for MIPS Atlas board CONFIG_MIPS_ATLAS This enables support for the QED R5231-based MIPS Atlas evaluation board. Support for MIPS Malta board CONFIG_MIPS_MALTA This enables support for the VR5000-based MIPS Malta evaluation board. # Choice: bcmboard Support for Broadcom SiByte boards CONFIG_SIBYTE_SWARM Enable support for boards based on the Broadcom SiByte family: BCM91250A-SWARM BCM1250 ATX size Eval Board (BCM91250A-SWARM) BCM91250E-Sentosa BCM1250 PCI card Eval Board (BCM91250E-Sentosa) BCM91125E-Rhone BCM1125 PCI card Eval Board (BCM91125E-Rhone) Other Non-Broadcom SiByte-based platform # Choice: bcmsoc Support for Broadcom BCM1xxx SOCs CONFIG_SIBYTE_SB1250 BCM1250 Dual-CPU SB1 with PCI and HyperTransport. BCM1120 Uniprocessor SB1. BCM1125 Uniprocessor SB1 with PCI (and HyperTransport for 1125H). BCM1250 Pass CONFIG_CPU_SB1_PASS_1 Which pass of the SOC is supported (see the "system_revision" register in the User Manual for more discussion of revisions): Pass1 1250 "Pass 1" A3-A10 1250 "Pass 2" B0-B3 1250 "Pass 2.2" BCM1xxx Pass CONFIG_CPU_SB1_PASS_2 Which pass of the SOC is supported (see the "system_revision" register in the User Manual for more discussion of revisions): Hybrid 1250 "Pass 2" A1-A2 112x A1-A2 Booting from CFE CONFIG_SIBYTE_CFE Make use of the CFE API for enumerating available memory, controlling secondary CPUs, and possibly console output. Use firmware console CONFIG_SIBYTE_CFE_CONSOLE Use the CFE API's console write routines during boot. Other console options (VT console, sb1250 duart console, etc.) should not be configured. Support SWARM (BCM912500A) peripherals CONFIG_SIBYTE_SWARM Indicates that the target is a SWARM board. Most devices (IDE, video decoder, audio codec, etc) still require additional configuration options under the appropriate sections. Corelis Debugger CONFIG_SB1XXX_CORELIS Select compile flags that produce code that can be processed by the Corelis mksym utility and UDB Emulator. Support for Galileo Evaluation board or CoSine Orion CONFIG_ORION Say Y if configuring for the Galileo evaluation board or CoSine Orion. More information is available at . Otherwise, say N. Support for Mips Magnum 4000 CONFIG_MIPS_MAGNUM_4000 This is a machine with a R4000 100 MHz CPU. To compile a Linux kernel that runs on these, say Y here. For details about Linux on the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at . Enable Qtronix 990P Keyboard Support CONFIG_QTRONIX_KEYBOARD Images of Qtronix keyboards are at . Support for Olivetti M700 CONFIG_OLIVETTI_M700 This is a machine with a R4000 100 MHz CPU. To compile a Linux kernel that runs on these, say Y here. For details about Linux on the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at . Support for SNI RM200 PCI CONFIG_SNI_RM200_PCI The SNI RM200 PCI was a MIPS-based platform manufactured by Siemens Nixdorf Informationssysteme (SNI), parent company of Pyramid Technology and now in turn merged with Fujitsu. Say Y here to support this machine type. Support for SGI-IP22 (Indy/Indigo2) CONFIG_SGI_IP22 This are the SGI Indy, Challenge S and Indigo2, as well as certain OEM variants like the Tandem CMN B006S. To compile a Linux kernel that runs on these, say Y here. Support for SGI IP27 (Origin200/2000) CONFIG_SGI_IP27 This are the SGI Origin 200, Origin 2000 and Onyx 2 Graphics workstations. To compile a Linux kernel that runs on these, say Y here. IP27 N-Mode CONFIG_SGI_SN0_N_MODE The nodes of Origin 200, Origin 2000 and Onyx 2 systems can be configured in either N-Modes which allows for more nodes or M-Mode which allows for more memory. Your system is most probably running in M-Mode, so you should say N here. Lasi Ethernet CONFIG_LASI_82596 Say Y here to support the on-board Intel 82596 ethernet controller built into Hewlett-Packard PA-RISC machines. MIPS JAZZ onboard SONIC Ethernet support CONFIG_MIPS_JAZZ_SONIC This is the driver for the onboard card of MIPS Magnum 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM systems. MIPS JAZZ FAS216 SCSI support CONFIG_JAZZ_ESP This is the driver for the onboard SCSI host adapter of MIPS Magnum 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM systems. MIPS GT96100 support CONFIG_MIPS_GT96100 Say Y here to support the Galileo Technology GT96100 communications controller card. There is a web page at . MIPS GT96100 Ethernet support CONFIG_MIPS_GT96100ETH Say Y here to support the Ethernet subsystem on your GT96100 card. Zalon SCSI support CONFIG_SCSI_ZALON The Zalon is an interface chip that sits between the PA-RISC processor and the NCR 53c720 SCSI controller on K-series PA-RISC boards (these are used, among other places, on some HP 780 workstations). Say Y here to make sure it gets initialized correctly before the Linux kernel tries to talk to the controller. SGI PROM Console Support CONFIG_SGI_PROM_CONSOLE Say Y here to set up the boot console on serial port 0. DECstation serial support CONFIG_SERIAL_DEC This selects whether you want to be asked about drivers for DECstation serial ports. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about DECstation serial ports. If unsure, say Y. Support for console on a DECstation serial port CONFIG_SERIAL_DEC_CONSOLE If you say Y here, it will be possible to use a serial port as the system console (the system console is the device which receives all kernel messages and warnings and which allows logins in single user mode). Note that the firmware uses ttyS0 as the serial console on the Maxine and ttyS2 on the others. If unsure, say Y. DZ11 Serial Support CONFIG_DZ DZ11-family serial controllers for VAXstations, including the DC7085, M7814, and M7819. TURBOchannel support CONFIG_TC TurboChannel is a DEC (now Compaq) bus for Alpha and MIPS processors. Documentation on writing device drivers for TurboChannel is available at: . # Choice: galileo_clock 75 CONFIG_SYSCLK_75 Configure the kernel for clock speed of your Galileo board. The choices are 75MHz, 83.3MHz, and 100MHz. 83.3 CONFIG_SYSCLK_83 Configure the Galileo kernel for a clock speed of 83.3 MHz. 100 CONFIG_SYSCLK_100 Configure the Galileo kernel for a clock speed of 100 MHz. Z85C30 Serial Support CONFIG_ZS Documentation on the Zilog 85C350 serial communications controller is downloadable at . PCMCIA SCSI adapter support CONFIG_SCSI_PCMCIA Say Y here if you intend to attach a PCMCIA or CardBus card to your computer which acts as a SCSI host adapter. These are credit card size devices often used with laptops. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions PCMCIA SCSI host adapters. Adaptec APA1480 CardBus support CONFIG_PCMCIA_APA1480 Say Y here if you intend to attach this type of CardBus SCSI host adapter to your computer. This driver is also available as a module called apa1480_cb.o ( = 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 . NinjaSCSI-3 / NinjaSCSI-32Bi (16bit) PCMCIA support CONFIG_PCMCIA_NINJA_SCSI If you intend to attach this type of PCMCIA SCSI host adapter to your computer, say Y here and read . This driver is also available as a module called nsp_cs.o ( = 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 . Adaptec AHA152X PCMCIA support CONFIG_PCMCIA_AHA152X Say Y here if you intend to attach this type of PCMCIA SCSI host adapter to your computer. This driver is also available as a module called aha152x_cs.o ( = 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 . Qlogic PCMCIA support CONFIG_PCMCIA_QLOGIC Say Y here if you intend to attach this type of PCMCIA SCSI host adapter to your computer. This driver is also available as a module called qlogic_cs.o ( = 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 . Future Domain PCMCIA support CONFIG_PCMCIA_FDOMAIN Say Y here if you intend to attach this type of PCMCIA SCSI host adapter to your computer. This driver is also available as a module called fdomain_cs.o ( = 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 . # Choice: mipstype CPU type CONFIG_CPU_R3000 Please make sure to pick the right CPU type. Linux/MIPS is not designed to be generic, i.e. Kernels compiled for R3000 CPUs will *not* work on R4000 machines and vice versa. However, since most of the supported machines have an R4000 (or similar) CPU, R4x00 might be a safe bet. If the resulting kernel does not work, try to recompile with R3000. R3000 MIPS Technologies R3000-series processors, including the 3041, 3051, and 3081. R6000 MIPS Technologies R6000-series processors, including the 64474, 64475, 64574 and 64575. R4300 MIPS Technologies R4300-series processors. R4x00 MIPS Technologies R4000-series processors other than 4300, including the 4640, 4650, and 4700. R5000 MIPS Technologies R5000-series processors other than the Nevada. R52xx MIPS Technologies R52xx-series ("Nevada") processors. R10000 MIPS Technologies R10000-series processors. SB1 Broadcom SiByte SB1 processor. R6000 CONFIG_CPU_R6000 MIPS Technologies R6000-series processors, including the 64474, 64475, 64574 and 64575. R4300 CONFIG_CPU_R4300 MIPS Technologies R4300-series processors. R4x00 CONFIG_CPU_R4X00 MIPS Technologies R4000-series processors other than 4300, including the 4640, 4650, and 4700. R5000 CONFIG_CPU_R5000 MIPS Technologies R5000-series processors other than the Nevada. R52x0 CONFIG_CPU_NEVADA MIPS Technologies R52x0-series ("Nevada") processors. R8000 CONFIG_CPU_R8000 MIPS Technologies R8000-series processors. R10000 CONFIG_CPU_R10000 MIPS Technologies R10000-series processors. SB1 CONFIG_CPU_SB1 Broadcom SiByte SB1 processor. Discontiguous Memory Support CONFIG_DISCONTIGMEM Say Y to support efficient handling of discontiguous physical memory, for architectures which are either NUMA (Non-Uniform Memory Access) or have huge holes in the physical address space for other reasons. See for more. Mapped kernel support CONFIG_MAPPED_KERNEL Change the way a Linux kernel is loaded unto memory on a MIPS64 machine. This is required in order to support text replication and NUMA. If you need to understand it, read the source code. Kernel text replication support CONFIG_REPLICATE_KTEXT Say Y here to enable replicating the kernel text across multiple nodes in a NUMA cluster. This trades memory for speed. Exception handler replication support CONFIG_REPLICATE_EXHANDLERS Say Y here to enable replicating the kernel exception handlers across multiple nodes in a NUMA cluster. This trades memory for speed. NUMA support? CONFIG_NUMA Say Y to compile the kernel to support NUMA (Non-Uniform Memory Access). This option is for configuring high-end multiprocessor server machines. If in doubt, say N. R41xx CONFIG_CPU_VR41XX The options selects support for the NEC VR41xx series of processors. Only choose this option if you have one of these processors as a kernel built with this option will not run on any other type of processor or vice versa. CPU feature configuration CONFIG_CPU_ADVANCED Saying yes here allows you to select support for various features your CPU may or may not have. Most people should say N here. ll and sc instructions available CONFIG_CPU_HAS_LLSC MIPS R4000 series and later provide the Load Linked (ll) and Store Conditional (sc) instructions. More information is available at . Say Y here if your CPU has the ll and sc instructions. Say Y here for better performance, N if you don't know. You must say Y here for multiprocessor machines. lld and scd instructions available CONFIG_CPU_HAS_LLDSCD Say Y here if your CPU has the lld and scd instructions, the 64-bit equivalents of ll and sc. Say Y here for better performance, N if you don't know. You must say Y here for multiprocessor machines. Writeback Buffer available CONFIG_CPU_HAS_WB Say N here for slightly better performance. You must say Y here for machines which require flushing of write buffers in software. Saying Y is the safe option; N may result in kernel malfunction and crashes. Support for large 64-bit configurations CONFIG_MIPS_INSANE_LARGE MIPS R10000 does support a 44 bit / 16TB address space as opposed to previous 64-bit processors which only supported 40 bit / 1TB. If you need processes of more than 1TB virtual address space, say Y here. This will result in additional memory usage, so it is not recommended for normal users. Generate little endian code CONFIG_CPU_LITTLE_ENDIAN Some MIPS machines can be configured for either little or big endian byte order. These modes require different kernels. Say Y if your machine is little endian, N if it's a big endian machine. Use power LED as a heartbeat CONFIG_HEARTBEAT Use the power-on LED on your machine as a load meter. The exact behaviour is platform-dependent, but normally the flash frequency is a hyperbolic function of the 5-minute load average. Networking support CONFIG_NET Unless you really know what you are doing, you should say Y here. The reason is that some programs need kernel networking support even when running on a stand-alone machine that isn't connected to any other computer. If you are upgrading from an older kernel, you should consider updating your networking tools too because changes in the kernel and the tools often go hand in hand. The tools are contained in the package net-tools, the location and version number of which are given in . For a general introduction to Linux networking, it is highly recommended to read the NET-HOWTO, available from . Socket filtering CONFIG_FILTER The Linux Socket Filter is derived from the Berkeley Packet Filter. If you say Y here, user-space programs can attach a filter to any socket and thereby tell the kernel that it should allow or disallow certain types of data to get through the socket. Linux Socket Filtering works on all socket types except TCP for now. See the text file for more information. You need to say Y here if you want to use PPP packet filtering (see the CONFIG_PPP_FILTER option below). If unsure, say N. Network packet filtering (replaces ipchains) CONFIG_NETFILTER Netfilter is a framework for filtering and mangling network packets that pass through your Linux box. The most common use of packet filtering is to run your Linux box as a firewall protecting a local network from the Internet. The type of firewall provided by this kernel support is called a "packet filter", which means that it can reject individual network packets based on type, source, destination etc. The other kind of firewall, a "proxy-based" one, is more secure but more intrusive and more bothersome to set up; it inspects the network traffic much more closely, modifies it and has knowledge about the higher level protocols, which a packet filter lacks. Moreover, proxy-based firewalls often require changes to the programs running on the local clients. Proxy-based firewalls don't need support by the kernel, but they are often combined with a packet filter, which only works if you say Y here. You should also say Y here if you intend to use your Linux box as the gateway to the Internet for a local network of machines without globally valid IP addresses. This is called "masquerading": if one of the computers on your local network wants to send something to the outside, your box can "masquerade" as that computer, i.e. it forwards the traffic to the intended outside destination, but modifies the packets to make it look like they came from the firewall box itself. It works both ways: if the outside host replies, the Linux box will silently forward the traffic to the correct local computer. This way, the computers on your local net are completely invisible to the outside world, even though they can reach the outside and can receive replies. It is even possible to run globally visible servers from within a masqueraded local network using a mechanism called portforwarding. Masquerading is also often called NAT (Network Address Translation). Another use of Netfilter is in transparent proxying: if a machine on the local network tries to connect to an outside host, your Linux box can transparently forward the traffic to a local server, typically a caching proxy server. Various modules exist for netfilter which replace the previous masquerading (ipmasqadm), packet filtering (ipchains), transparent proxying, and portforwarding mechanisms. Please see under "iptables" for the location of these packages. Make sure to say N to "Fast switching" below if you intend to say Y here, as Fast switching currently bypasses netfilter. Chances are that you should say Y here if you compile a kernel which will run as a router and N for regular hosts. If unsure, say N. Network packet filtering debugging CONFIG_NETFILTER_DEBUG You can say Y here if you want to get additional messages useful in debugging the netfilter code. Connection tracking (required for masq/NAT) CONFIG_IP_NF_CONNTRACK Connection tracking keeps a record of what packets have passed through your machine, in order to figure out how they are related into connections. This is required to do Masquerading or other kinds of Network Address Translation (except for Fast NAT). It can also be used to enhance packet filtering (see `Connection state match support' below). If you want to compile it as a module, say M here and read . If unsure, say `N'. IRC Send/Chat protocol support CONFIG_IP_NF_IRC There is a commonly-used extension to IRC called Direct Client-to-Client Protocol (DCC). This enables users to send files to each other, and also chat to each other without the need of a server. DCC Sending is used anywhere you send files over IRC, and DCC Chat is most commonly used by Eggdrop bots. If you are using NAT, this extension will enable you to send files and initiate chats. Note that you do NOT need this extension to get files or have others initiate chats, or everything else in IRC. If you want to compile it as a module, say 'M' here and read Documentation/modules.txt. If unsure, say 'N'. FTP protocol support CONFIG_IP_NF_FTP Tracking FTP connections is problematic: special helpers are required for tracking them, and doing masquerading and other forms of Network Address Translation on them. If you want to compile it as a module, say M here and read . If unsure, say `Y'. User space queueing via NETLINK CONFIG_IP_NF_QUEUE Netfilter has the ability to queue packets to user space: the netlink device can be used to access them using this driver. If you want to compile it as a module, say M here and read . If unsure, say `N'. IP tables support (required for filtering/masq/NAT) CONFIG_IP_NF_IPTABLES iptables is a general, extensible packet identification framework. The packet filtering and full NAT (masquerading, port forwarding, etc) subsystems now use this: say 'Y' or 'M' here if you want to use either of those. If you want to compile it as a module, say M here and read . If unsure, say `N'. RTSP protocol support CONFIG_IP_NF_RTSP Support the RTSP protocol. This allows UDP transports to be setup properly, including RTP and RDT. If you want to compile it as a module, say 'M' here and read Documentation/modules.txt. If unsure, say 'Y'. limit match support CONFIG_IP_NF_MATCH_LIMIT limit matching allows you to control the rate at which a rule can be matched: mainly useful in combination with the LOG target ("LOG target support", below) and to avoid some Denial of Service attacks. If you want to compile it as a module, say M here and read . If unsure, say `N'. skb->pkt_type packet match support CONFIG_IP_NF_MATCH_PKTTYPE This patch allows you to match packet in accrodance to its "class", eg. BROADCAST, MULTICAST, ... Typical usage: iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. MAC address match support CONFIG_IP_NF_MATCH_MAC MAC matching allows you to match packets based on the source Ethernet address of the packet. If you want to compile it as a module, say M here and read . If unsure, say `N'. Netfilter MARK match support CONFIG_IP_NF_MATCH_MARK Netfilter mark matching allows you to match packets based on the `nfmark' value in the packet. This can be set by the MARK target (see below). If you want to compile it as a module, say M here and read . If unsure, say `N'. Multiple port match support CONFIG_IP_NF_MATCH_MULTIPORT Multiport matching allows you to match TCP or UDP packets based on a series of source or destination ports: normally a rule can only match a single range of ports. If you want to compile it as a module, say M here and read . If unsure, say `N'. TTL match support CONFIG_IP_NF_MATCH_TTL This adds CONFIG_IP_NF_MATCH_TTL option, which enabled the user to match packets by their TTL value. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. LENGTH match support CONFIG_IP_NF_MATCH_LENGTH This option allows you to match the length of a packet against a specific value or range of values. If you want to compile it as a module, say M here and read . If unsure, say `N'. AH/ESP match support CONFIG_IP_NF_MATCH_AH_ESP These two match extensions (`ah' and `esp') allow you to match a range of SPIs inside AH or ESP headers of IPSec packets. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. DSCP match support CONFIG_IP_NF_MATCH_DSCP This option adds a `DSCP' match, which allows you to match against the IPv4 header DSCP field (DSCP codepoint). The DSCP codepoint can have any value between 0x0 and 0x4f. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. ECN match support CONFIG_IP_NF_MATCH_ECN This option adds a `ECN' match, which allows you to match against the IPv4 and TCP header ECN fields. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. TOS match support CONFIG_IP_NF_MATCH_TOS TOS matching allows you to match packets based on the Type Of Service fields of the IP packet. If you want to compile it as a module, say M here and read . If unsure, say `N'. conntrack match support CONFIG_IP_NF_MATCH_CONNTRACK This is a general conntrack match module, a superset of the state match. It allows matching on additional conntrack information, which is useful in complex configurations, such as NAT gateways with multiple internet links or tunnels. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. Connection state match support CONFIG_IP_NF_MATCH_STATE Connection state matching allows you to match packets based on their relationship to a tracked connection (ie. previous packets). This is a powerful tool for packet classification. If you want to compile it as a module, say M here and read . If unsure, say `N'. Unclean match support CONFIG_IP_NF_MATCH_UNCLEAN Unclean packet matching matches any strange or invalid packets, by looking at a series of fields in the IP, TCP, UDP and ICMP headers. If you want to compile it as a module, say M here and read . If unsure, say `N'. Owner match support CONFIG_IP_NF_MATCH_OWNER Packet owner matching allows you to match locally-generated packets based on who created them: the user, group, process or session. If you want to compile it as a module, say M here and read . If unsure, say `N'. Packet filtering CONFIG_IP_NF_FILTER Packet filtering defines a table `filter', which has a series of rules for simple packet filtering at local input, forwarding and local output. See the man page for iptables(8). If you want to compile it as a module, say M here and read . If unsure, say `N'. REJECT target support CONFIG_IP_NF_TARGET_REJECT The REJECT target allows a filtering rule to specify that an ICMP error should be issued in response to an incoming packet, rather than silently being dropped. If you want to compile it as a module, say M here and read . If unsure, say `N'. MIRROR target support CONFIG_IP_NF_TARGET_MIRROR The MIRROR target allows a filtering rule to specify that an incoming packet should be bounced back to the sender. If you want to compile it as a module, say M here and read . If unsure, say `N'. Local NAT support CONFIG_IP_NF_NAT_LOCAL This option enables support for NAT of locally originated connections. Enable this if you need to use destination NAT on connections originating from local processes on the nat box itself. Please note that you will need a recent version (>= 1.2.6a) of the iptables userspace program in order to use this feature. See for download instructions. If unsure, say 'N'. Full NAT (Network Address Translation) CONFIG_IP_NF_NAT The Full NAT option allows masquerading, port forwarding and other forms of full Network Address Port Translation. It is controlled by the `nat' table in iptables: see the man page for iptables(8). If you want to compile it as a module, say M here and read . If unsure, say `N'. MASQUERADE target support CONFIG_IP_NF_TARGET_MASQUERADE Masquerading is a special case of NAT: all outgoing connections are changed to seem to come from a particular interface's address, and if the interface goes down, those connections are lost. This is only useful for dialup accounts with dynamic IP address (ie. your IP address will be different on next dialup). If you want to compile it as a module, say M here and read . If unsure, say `N'. Basic SNMP-ALG support CONFIG_IP_NF_NAT_SNMP_BASIC This module implements an Application Layer Gateway (ALG) for SNMP payloads. In conjunction with NAT, it allows a network management system to access multiple private networks with conflicting addresses. It works by modifying IP addresses inside SNMP payloads to match IP-layer NAT mapping. This is the "basic" form of SNMP-ALG, as described in RFC 2962 If you want to compile it as a module, say M here and read . If unsure, say `N'. REDIRECT target support CONFIG_IP_NF_TARGET_REDIRECT REDIRECT is a special case of NAT: all incoming connections are mapped onto the incoming interface's address, causing the packets to come to the local machine instead of passing through. This is useful for transparent proxies. If you want to compile it as a module, say M here and read . If unsure, say `N'. Packet mangling CONFIG_IP_NF_MANGLE This option adds a `mangle' table to iptables: see the man page for iptables(8). This table is used for various packet alterations which can effect how the packet is routed. If you want to compile it as a module, say M here and read . If unsure, say `N'. DSCP target support CONFIG_IP_NF_TARGET_DSCP This option adds a `DSCP' target, which allows you to create rules in the iptables mangle table. The selected packet has the DSCP field set to the hex value provided on the command line; unlike the TOS target which will only set the legal values within ip.h. The DSCP field can be set to any value between 0x0 and 0x4f. It does take into account that bits 6 and 7 are used by ECN. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. ECN target support CONFIG_IP_NF_TARGET_ECN This option adds a `ECN' target, which can be used in the iptables mangle table. You can use this target to remove the ECN bits from the IPv4 header of an IP packet. This is particularly useful, if you need to work around existing ECN blackholes on the internet, but don't want to disable ECN support in general. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. TOS target support CONFIG_IP_NF_TARGET_TOS This option adds a `TOS' target, which allows you to create rules in the `mangle' table which alter the Type Of Service field of an IP packet prior to routing. If you want to compile it as a module, say M here and read . If unsure, say `N'. MARK target support CONFIG_IP_NF_TARGET_MARK This option adds a `MARK' target, which allows you to create rules in the `mangle' table which alter the netfilter mark (nfmark) field associated with the packet prior to routing. This can change the routing method (see `Use netfilter MARK value as routing key') and can also be used by other subsystems to change their behaviour. If you want to compile it as a module, say M here and read . If unsure, say `N'. TCPMSS target support CONFIG_IP_NF_TARGET_TCPMSS This option adds a `TCPMSS' target, which allows you to alter the MSS value of TCP SYN packets, to control the maximum size for that connection (usually limiting it to your outgoing interface's MTU minus 40). This is used to overcome criminally braindead ISPs or servers which block ICMP Fragmentation Needed packets. The symptoms of this problem are that everything works fine from your Linux firewall/router, but machines behind it can never exchange large packets: 1) Web browsers connect, then hang with no data received. 2) Small mail works fine, but large emails hang. 3) ssh works fine, but scp hangs after initial handshaking. Workaround: activate this option and add a rule to your firewall configuration like: iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \ -j TCPMSS --clamp-mss-to-pmtu If you want to compile it as a module, say M here and read . If unsure, say `N'. Helper match support CONFIG_IP_NF_MATCH_HELPER Helper matching allows you to match packets in dynamic connections tracked by a conntrack-helper, ie. ip_conntrack_ftp If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `Y'. TCPMSS match support CONFIG_IP_NF_MATCH_TCPMSS This option adds a `tcpmss' match, which allows you to examine the MSS value of TCP SYN packets, which control the maximum packet size for that connection. If you want to compile it as a module, say M here and read . If unsure, say `N'. ULOG target support CONFIG_IP_NF_TARGET_ULOG This option adds a `ULOG' target, which allows you to create rules in any iptables table. The packet is passed to a userspace logging daemon using netlink multicast sockets; unlike the LOG target which can only be viewed through syslog. The appropriate userspace logging daemon (ulogd) may be obtained from If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. LOG target support CONFIG_IP_NF_TARGET_LOG This option adds a `LOG' target, which allows you to create rules in any iptables table which records the packet header to the syslog. If you want to compile it as a module, say M here and read . If unsure, say `N'. ipchains (2.2-style) support CONFIG_IP_NF_COMPAT_IPCHAINS This option places ipchains (with masquerading and redirection support) back into the kernel, using the new netfilter infrastructure. It is not recommended for new installations (see `Packet filtering'). With this enabled, you should be able to use the ipchains tool exactly as in 2.2 kernels. If you want to compile it as a module, say M here and read . If unsure, say `N'. ipfwadm (2.0-style) support CONFIG_IP_NF_COMPAT_IPFWADM This option places ipfwadm (with masquerading and redirection support) back into the kernel, using the new netfilter infrastructure. It is not recommended for new installations (see `Packet filtering'). With this enabled, you should be able to use the ipfwadm tool exactly as in 2.0 kernels. If you want to compile it as a module, say M here and read . If unsure, say `N'. EUI64 address check (EXPERIMENTAL) CONFIG_IP6_NF_MATCH_EUI64 This module performs checking on the IPv6 source address Compares the last 64 bits with the EUI64 (delivered from the MAC address) address If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. MAC address match support CONFIG_IP6_NF_MATCH_MAC mac matching allows you to match packets based on the source Ethernet address of the packet. If you want to compile it as a module, say M here and read . If unsure, say `N'. length match support CONFIG_IP6_NF_MATCH_LENGTH This option allows you to match the length of a packet against a specific value or range of values. If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. Netfilter MARK match support CONFIG_IP6_NF_MATCH_MARK Netfilter mark matching allows you to match packets based on the `nfmark' value in the packet. This can be set by the MARK target (see below). If you want to compile it as a module, say M here and read . If unsure, say `N'. Multiple port match support CONFIG_IP6_NF_MATCH_MULTIPORT Multiport matching allows you to match TCP or UDP packets based on a series of source or destination ports: normally a rule can only match a single range of ports. If you want to compile it as a module, say M here and read . If unsure, say `N'. IPV6 queue handler (EXPERIMENTAL) CONFIG_IP6_NF_QUEUE This option adds a queue handler to the kernel for IPv6 packets which lets us to receive the filtered packets with QUEUE target using libiptc as we can do with the IPv4 now. (C) Fernando Anton 2001 IPv64 Project - Work based in IPv64 draft by Arturo Azcorra. Universidad Carlos III de Madrid Universidad Politecnica de Alcala de Henares email: fanton@it.uc3m.es If you want to compile it as a module, say M here and read Documentation/modules.txt. If unsure, say `N'. Owner match support CONFIG_IP6_NF_MATCH_OWNER Packet owner matching allows you to match locally-generated packets based on who created them: the user, group, process or session. If you want to compile it as a module, say M here and read . If unsure, say `N'. Packet filtering CONFIG_IP6_NF_FILTER Packet filtering defines a table `filter', which has a series of rules for simple packet filtering at local input, forwarding and local output. See the man page for iptables(8). If you want to compile it as a module, say M here and read . If unsure, say `N'. Packet mangling CONFIG_IP6_NF_MANGLE This option adds a `mangle' table to iptables: see the man page for iptables(8). This table is used for various packet alterations which can effect how the packet is routed. If you want to compile it as a module, say M here and read . If unsure, say `N'. MARK target support CONFIG_IP6_NF_TARGET_MARK This option adds a `MARK' target, which allows you to create rules in the `mangle' table which alter the netfilter mark (nfmark) field associated with the packet packet prior to routing. This can change the routing method (see `Use netfilter MARK value as routing key') and can also be used by other subsystems to change their behaviour. If you want to compile it as a module, say M here and read . If unsure, say `N'. TCP Explicit Congestion Notification support CONFIG_INET_ECN Explicit Congestion Notification (ECN) allows routers to notify clients about network congestion, resulting in fewer dropped packets and increased network performance. This option adds ECN support to the Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn) which allows ECN support to be disabled at runtime. Note that, on the Internet, there are many broken firewalls which refuse connections from ECN-enabled machines, and it may be a while before these firewalls are fixed. Until then, to access a site behind such a firewall (some of which are major sites, at the time of this writing) you will have to disable this option, either by saying N now or by using the sysctl. If in doubt, say N. IPv6 tables support (required for filtering/masq/NAT) CONFIG_IP6_NF_IPTABLES ip6tables is a general, extensible packet identification framework. Currently only the packet filtering and packet mangling subsystem for IPv6 use this, but connection tracking is going to follow. Say 'Y' or 'M' here if you want to use either of those. If you want to compile it as a module, say M here and read . If unsure, say `N'. IPv6 limit match support CONFIG_IP6_NF_MATCH_LIMIT limit matching allows you to control the rate at which a rule can be matched: mainly useful in combination with the LOG target ("LOG target support", below) and to avoid some Denial of Service attacks. If you want to compile it as a module, say M here and read . If unsure, say `N'. LOG target support CONFIG_IP6_NF_TARGET_LOG This option adds a `LOG' target, which allows you to create rules in any iptables table which records the packet header to the syslog. If you want to compile it as a module, say M here and read . If unsure, say `N'. SYN flood protection CONFIG_SYN_COOKIES Normal TCP/IP networking is open to an attack known as "SYN flooding". This denial-of-service attack prevents legitimate remote users from being able to connect to your computer during an ongoing attack and requires very little work from the attacker, who can operate from anywhere on the Internet. SYN cookies provide protection against this type of attack. If you say Y here, the TCP/IP stack will use a cryptographic challenge protocol known as "SYN cookies" to enable legitimate users to continue to connect, even when your machine is under attack. There is no need for the legitimate users to change their TCP/IP software; SYN cookies work transparently to them. For technical information about SYN cookies, check out . If you are SYN flooded, the source address reported by the kernel is likely to have been forged by the attacker; it is only reported as an aid in tracing the packets to their actual source and should not be taken as absolute truth. SYN cookies may prevent correct error reporting on clients when the server is really overloaded. If this happens frequently better turn them off. If you say Y here, note that SYN cookies aren't enabled by default; you can enable them by saying Y to "/proc file system support" and "Sysctl support" below and executing the command echo 1 >/proc/sys/net/ipv4/tcp_syncookies at boot time after the /proc file system has been mounted. If unsure, say N. # Choice: alphatype Alpha system type CONFIG_ALPHA_GENERIC This is the system type of your hardware. A "generic" kernel will run on any supported Alpha system. However, if you configure a kernel for your specific system, it will be faster and smaller. To find out what type of Alpha system you have, you may want to check out the Linux/Alpha FAQ, accessible on the WWW from . In summary: Alcor/Alpha-XLT AS 600 Alpha-XL XL-233, XL-266 AlphaBook1 Alpha laptop Avanti AS 200, AS 205, AS 250, AS 255, AS 300, AS 400 Cabriolet AlphaPC64, AlphaPCI64 DP264 DP264 EB164 EB164 21164 evaluation board EB64+ EB64+ 21064 evaluation board EB66 EB66 21066 evaluation board EB66+ EB66+ 21066 evaluation board Jensen DECpc 150, DEC 2000 model 300, DEC 2000 model 500 LX164 AlphaPC164-LX Miata Personal Workstation 433a, 433au, 500a, 500au, 600a, or 600au Mikasa AS 1000 Noname AXPpci33, UDB (Multia) Noritake AS 1000A, AS 600A, AS 800 PC164 AlphaPC164 Rawhide AS 1200, AS 4000, AS 4100 Ruffian RPX164-2, AlphaPC164-UX, AlphaPC164-BX SX164 AlphaPC164-SX Sable AS 2000, AS 2100 Shark DS 20L Takara Takara Titan Privateer Wildfire AlphaServer GS 40/80/160/320 If you don't know what to do, choose "generic". # Most of the information on these variants is from # Alcor/Alpha-XLT CONFIG_ALPHA_ALCOR For systems using the Digital ALCOR chipset: 5 chips (4, 64-bit data slices (Data Switch, DSW) - 208-pin PQFP and 1 control (Control, I/O Address, CIA) - a 383 pin plastic PGA). It provides a DRAM controller (256-bit memory bus) and a PCI interface. It also does all the work required to support an external Bcache and to maintain memory coherence when a PCI device DMAs into (or out of) memory. Alpha-XL CONFIG_ALPHA_XL XL-233 and XL-266-based Alpha systems. AlphaBook1 CONFIG_ALPHA_BOOK1 Dec AlphaBook1/Burns Alpha-based laptops. Avanti CONFIG_ALPHA_AVANTI Avanti AS 200, AS 205, AS 250, AS 255, AS 300, and AS 400-based Alphas. Info at . Cabriolet CONFIG_ALPHA_CABRIOLET Cabriolet AlphaPC64, AlphaPCI64 systems. Derived from EB64+ but now baby-AT with Flash boot ROM, no on-board SCSI or Ethernet. 3 ISA slots, 4 PCI slots (one pair are on a shared slot), uses plug-in Bcache SIMMs. Requires power supply with 3.3V output. DP264 CONFIG_ALPHA_DP264 Various 21264 systems with the tsunami core logic chipset. API Networks: 264DP, UP2000(+), CS20; Compaq: DS10(E,L), XP900, XP1000, DS20(E), ES40. EB164 CONFIG_ALPHA_EB164 EB164 21164 evaluation board from DEC. Uses 21164 and ALCOR. Has ISA and PCI expansion (3 ISA slots, 2 64-bit PCI slots (one is shared with an ISA slot) and 2 32-bit PCI slots. Uses plus-in Bcache SIMMs. I/O sub-system provides SuperI/O (2S, 1P, FD), KBD, MOUSE (PS2 style), RTC/NVRAM. Boot ROM is Flash. PC-AT-sized motherboard. Requires power supply with 3.3V output. EB64+ CONFIG_ALPHA_EB64P Uses 21064 or 21064A and APECs. Has ISA and PCI expansion (3 ISA, 2 PCI, one pair are on a shared slot). Supports 36-bit DRAM SIMs. ISA bus generated by Intel SaturnI/O PCI-ISA bridge. On-board SCSI (NCR 810 on PCI) Ethernet (Digital 21040), KBD, MOUSE (PS2 style), SuperI/O (2S, 1P, FD), RTC/NVRAM. Boot ROM is EPROM. PC-AT size. Runs from standard PC power supply. EB66 CONFIG_ALPHA_EB66 A Digital DS group board. Uses 21066 or 21066A. I/O sub-system is identical to EB64+. Baby PC-AT size. Runs from standard PC power supply. The EB66 schematic was published as a marketing poster advertising the 21066 as "the first microprocessor in the world with embedded PCI". EB66+ CONFIG_ALPHA_EB66P Later variant of the EB66 board. Eiger CONFIG_ALPHA_EIGER Apparently an obscure OEM single-board computer based on the Typhoon/Tsunami chipset family. Information on it is scanty. Jensen CONFIG_ALPHA_JENSEN DEC PC 150 AXP (aka Jensen): This is a very old Digital system - one of the first-generation Alpha systems. A number of these systems seem to be available on the second- hand market. The Jensen is a floor-standing tower system which originally used a 150MHz 21064 It used programmable logic to interface a 486 EISA I/O bridge to the CPU. LX164 CONFIG_ALPHA_LX164 A technical overview of this board is available at . Miata CONFIG_ALPHA_MIATA The Digital PersonalWorkStation (PWS 433a, 433au, 500a, 500au, 600a, or 600au). There is an Installation HOWTO for this hardware at . Mikasa CONFIG_ALPHA_MIKASA AlphaServer 1000-based Alpha systems. Nautilus CONFIG_ALPHA_NAUTILUS Alpha systems based on the AMD 751 & ALI 1543C chipsets. Noname CONFIG_ALPHA_NONAME The AXPpci33 (aka NoName), is based on the EB66 (includes the Multia UDB). This design was produced by Digital's Technical OEM (TOEM) group. It uses the 21066 processor running at 166MHz or 233MHz. It is a baby-AT size, and runs from a standard PC power supply. It has 5 ISA slots and 3 PCI slots (one pair are a shared slot). There are 2 versions, with either PS/2 or large DIN connectors for the keyboard. Noritake CONFIG_ALPHA_NORITAKE AlphaServer 1000A, AlphaServer 600A, and AlphaServer 800-based systems. Rawhide CONFIG_ALPHA_RAWHIDE AlphaServer 1200, AlphaServer 4000 and AlphaServer 4100 machines. See HOWTO at . Ruffian CONFIG_ALPHA_RUFFIAN Samsung APC164UX. There is a page on known problems and workarounds at . Sable CONFIG_ALPHA_SABLE Digital AlphaServer 2000 and 2100-based systems. Takara CONFIG_ALPHA_TAKARA Alpha 11164-based OEM single-board computer. Wildfire CONFIG_ALPHA_WILDFIRE AlphaServer GS 40/80/160/320 SMP based on the EV67 core. EV5 CPU daughtercard (model 5/xxx) CONFIG_ALPHA_PRIMO Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx. EV5 CPU(s) (model 5/xxx) CONFIG_ALPHA_GAMMA Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx. EV67 (or later) CPU (speed > 600MHz)? CONFIG_ALPHA_EV67 Is this a machine based on the EV67 core? If in doubt, select N here and the machine will be treated as an EV6. Use SRM as bootloader CONFIG_ALPHA_SRM There are two different types of booting firmware on Alphas: SRM, which is command line driven, and ARC, which uses menus and arrow keys. Details about the Linux/Alpha booting process are contained in the Linux/Alpha FAQ, accessible on the WWW from . The usual way to load Linux on an Alpha machine is to use MILO (a bootloader that lets you pass command line parameters to the kernel just like lilo does for the x86 architecture) which can be loaded either from ARC or can be installed directly as a permanent firmware replacement from floppy (which requires changing a certain jumper on the motherboard). If you want to do either of these, say N here. If MILO doesn't work on your system (true for Jensen motherboards), you can bypass it altogether and boot Linux directly from an SRM console; say Y here in order to do that. Note that you won't be able to boot from an IDE disk using SRM. If unsure, say N. Legacy kernel start address CONFIG_ALPHA_LEGACY_START_ADDRESS The 2.4 kernel changed the kernel start address from 0x310000 to 0x810000 to make room for the Wildfire's larger SRM console. If you're using aboot 0.7 or later, the bootloader will examine the ELF headers to determine where to transfer control. Unfortunately, most older bootloaders -- APB or MILO -- hardcoded the kernel start address rather than examining the ELF headers, and the result is a hard lockup. Say Y if you have a broken bootloader. Say N if you do not, or if you wish to run on Wildfire. Large VMALLOC support CONFIG_ALPHA_LARGE_VMALLOC Process creation and other aspects of virtual memory management can be streamlined if we restrict the kernel to one PGD for all vmalloc allocations. This equates to about 8GB. Under normal circumstances, this is so far and above what is needed as to be laughable. However, there are certain applications (such as benchmark-grade in-kernel web serving) that can make use of as much vmalloc space as is available. Say N unless you know you need gobs and gobs of vmalloc space. Non-standard serial port support CONFIG_SERIAL_NONSTANDARD Say Y here if you have any non-standard serial boards -- boards which aren't supported using the standard "dumb" serial driver. This includes intelligent serial boards such as Cyclades, Digiboards, etc. These are usually used for systems that need many serial ports because they serve many terminals or dial-in connections. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about non-standard serial boards. Most people can say N here. Extended dumb serial driver options CONFIG_SERIAL_EXTENDED If you wish to use any non-standard features of the standard "dumb" driver, say Y here. This includes HUB6 support, shared serial interrupts, special multiport support, support for more than the four COM 1/2/3/4 boards, etc. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about serial driver options. If unsure, say N. Support more than 4 serial ports CONFIG_SERIAL_MANY_PORTS Say Y here if you have dumb serial boards other than the four standard COM 1/2/3/4 ports. This may happen if you have an AST FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available from ), or other custom serial port hardware which acts similar to standard serial port hardware. If you only use the standard COM 1/2/3/4 ports, you can say N here to save some memory. You can also say Y if you have an "intelligent" multiport card such as Cyclades, Digiboards, etc. Support for sharing serial interrupts CONFIG_SERIAL_SHARE_IRQ Some serial boards have hardware support which allows multiple dumb serial ports on the same board to share a single IRQ. To enable support for this in the serial driver, say Y here. Auto-detect IRQ on standard ports (unsafe) CONFIG_SERIAL_DETECT_IRQ Say Y here if you want the kernel to try to guess which IRQ to use for your serial port. This is considered unsafe; it is far better to configure the IRQ in a boot script using the setserial command. If unsure, say N. Support special multiport boards CONFIG_SERIAL_MULTIPORT Some multiport serial ports have special ports which are used to signal when there are any serial ports on the board which need servicing. Say Y here to enable the serial driver to take advantage of those special I/O ports. SGI IP22 Zilog85C30 serial support CONFIG_IP22_SERIAL If you want to use your IP22's built-in serial ports under Linux, answer Y. SGI Newport Graphics support CONFIG_SGI_NEWPORT_GFX If you have an SGI machine and you want to compile the graphics drivers, say Y here. This will include the code for the /dev/graphics and /dev/gfx drivers into the kernel for supporting virtualized access to your graphics hardware. SGI Newport Console support CONFIG_SGI_NEWPORT_CONSOLE Say Y here if you want the console on the Newport aka XL graphics card of your Indy. Most people say Y here. SGI DS1286 RTC support CONFIG_SGI_DS1286 If you say Y here and create a character special file /dev/rtc with major number 10 and minor number 135 using mknod ("man mknod"), you will get access to the real time clock built into your computer. Every SGI has such a clock built in. It reports status information via the file /proc/rtc and its behaviour is set by various ioctls on /dev/rtc. Indy/I2 Hardware Watchdog CONFIG_INDYDOG Hardwaredriver for the Indy's/I2's watchdog. This is a watchdog timer that will reboot the machine after a 60 second timer expired and no process has written to /dev/watchdog during that time. Support the Bell Technologies HUB6 card CONFIG_HUB6 Say Y here to enable support in the dumb serial driver to support the HUB6 card. PCMCIA serial device support CONFIG_PCMCIA_SERIAL_CS Say Y here to enable support for 16-bit PCMCIA serial devices, including serial port cards, modems, and the modem functions of multi-function Ethernet/modem cards. (PCMCIA- or PC-cards are credit-card size devices often used with laptops.) 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 serial_cs.o. If you want to compile it as a module, say M here and read . If unsure, say N. CONFIG_SYNCLINK_CS Enable support for the SyncLink PC Card serial adapter, running asynchronous and HDLC communications up to 512Kbps. The port is selectable for RS-232, V.35, RS-449, RS-530, and X.21 This driver may be built as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The module will be called synclinkmp.o. If you want to do that, say M here. ACP Modem (Mwave) support CONFIG_MWAVE The ACP modem (Mwave) for Linux is a WinModem. It is composed of a kernel driver and a user level application. Together these components support direct attachment to public switched telephone networks (PSTNs) and support selected world wide countries. This version of the ACP Modem driver supports the IBM Thinkpad 600E, 600, and 770 that include on board ACP modem hardware. The modem also supports the standard communications port interface (ttySx) and is compatible with the Hayes AT Command Set. The user level application needed to use this driver can be found at the IBM Linux Technology Center (LTC) web site: . If you own one of the above IBM Thinkpads which has the Mwave chipset in it, say Y. 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 mwave.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. /dev/agpgart (AGP Support) CONFIG_AGP AGP (Accelerated Graphics Port) is a bus system mainly used to connect graphics cards to the rest of the system. If you have an AGP system and you say Y here, it will be possible to use the AGP features of your 3D rendering video card. This code acts as a sort of "AGP driver" for the motherboard's chipset. If you need more texture memory than you can get with the AGP GART (theoretically up to 256 MB, but in practice usually 64 or 128 MB due to kernel allocation issues), you could use PCI accesses and have up to a couple gigs of texture space. Note that this is the only means to have XFree4/GLX use write-combining with MTRR support on the AGP bus. Without it, OpenGL direct rendering will be a lot slower but still faster than PIO. You should say Y here if you use XFree86 3.3.6 or 4.x and want to use GLX or DRI. If unsure, say N. This driver is available as a module. If you want to compile it as a module, say M here and read . The module will be called agpgart.o. Intel 440LX/BX/GX/815/820/830/840/845/850/860 support CONFIG_AGP_INTEL This option gives you AGP support for the GLX component of the XFree86 4.x on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850 and 860 chipsets. You should say Y here if you use XFree86 3.3.6 or 4.x and want to use GLX or DRI. If unsure, say N. Intel 460GX support CONFIG_AGP_I460 This option gives you AGP support for the Intel 460GX chipset. This chipset, the first to support Intel Itanium processors, is new and this option is correspondingly a little experimental. If you don't have a 460GX based machine (such as BigSur) with an AGP slot then this option isn't going to do you much good. If you're dying to do Direct Rendering on IA-64, this is what you're looking for. Intel I810/I815 DC100/I810e support CONFIG_AGP_I810 This option gives you AGP support for the Xserver on the Intel 810 815 and 830m chipset boards for their on-board integrated graphics. This is required to do any useful video modes with these boards. VIA chipset support CONFIG_AGP_VIA This option gives you AGP support for the GLX component of the XFree86 4.x on VIA MPV3/Apollo Pro chipsets. You should say Y here if you use XFree86 3.3.6 or 4.x and want to use GLX or DRI. If unsure, say N. AMD Irongate, 761, and 762 support CONFIG_AGP_AMD This option gives you AGP support for the GLX component of the XFree86 4.x on AMD Irongate, 761, and 762 chipsets. You should say Y here if you use XFree86 3.3.6 or 4.x and want to use GLX or DRI. If unsure, say N. Generic SiS support CONFIG_AGP_SIS This option gives you AGP support for the GLX component of the "soon to be released" XFree86 4.x on Silicon Integrated Systems [SiS] chipsets. Note that 5591/5592 AGP chipsets are NOT supported. You should say Y here if you use XFree86 3.3.6 or 4.x and want to use GLX or DRI. If unsure, say N. Serverworks LE/HE support CONFIG_AGP_SWORKS Say Y here to support the Serverworks AGP card. See for product descriptions and images. ALI chipset support CONFIG_AGP_ALI This option gives you AGP support for the GLX component of the XFree86 4.x on the following ALi chipsets. The supported chipsets include M1541, M1621, M1631, M1632, M1641,M1647,and M1651. For the ALi-chipset question, ALi suggests you refer to . The M1541 chipset can do AGP 1x and 2x, but note that there is an acknowledged incompatibility with Matrox G200 cards. Due to timing issues, this chipset cannot do AGP 2x with the G200. This is a hardware limitation. AGP 1x seems to be fine, though. You should say Y here if you use XFree86 3.3.6 or 4.x and want to use GLX or DRI. If unsure, say N. CONFIG_AGP_HP_ZX1 This option gives you AGP GART support for the HP ZX1 chipset for IA64 processors. Support for ISA-bus hardware CONFIG_ISA 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. Other bus systems are PCI, EISA, MicroChannel (MCA) or VESA. ISA is an older system, now being displaced by PCI; newer boards don't support it. If you have ISA, say Y, otherwise N. Support for PCI bus hardware CONFIG_PCI Find out whether you have a PCI motherboard. PCI is the name of a bus system, i.e. the way the CPU talks to the other stuff inside your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or VESA. If you have PCI, say Y, otherwise N. The PCI-HOWTO, available from , contains valuable information about which PCI hardware does work under Linux and which doesn't. PCI support CONFIG_PCI_INTEGRATOR Find out whether you have a PCI motherboard. PCI is the name of a bus system, i.e. the way the CPU talks to the other stuff inside your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or VESA. If you have PCI, say Y, otherwise N. The PCI-HOWTO, available from , contains valuable information about which PCI hardware does work under Linux and which doesn't. QSpan PCI CONFIG_PCI_QSPAN Find out whether you have a PCI motherboard. PCI is the name of a bus system, i.e. the way the CPU talks to the other stuff inside your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or VESA. If you have PCI, say Y, otherwise N. The PCI-HOWTO, available from , contains valuable information about which PCI hardware does work under Linux and which doesn't. # Choice: pci_access PCI access mode CONFIG_PCI_GOBIOS On PCI systems, the BIOS can be used to detect the PCI devices and determine their configuration. However, some old PCI motherboards have BIOS bugs and may crash if this is done. Also, some embedded PCI-based systems don't have any BIOS at all. Linux can also try to detect the PCI hardware directly without using the BIOS. With this option, you can specify how Linux should detect the PCI devices. If you choose "BIOS", the BIOS will be used, if you choose "Direct", the BIOS won't be used, and if you choose "Any", the kernel will try the direct access method and falls back to the BIOS if that doesn't work. If unsure, go with the default, which is "Any". PCI device name database CONFIG_PCI_NAMES By default, the kernel contains a database of all known PCI device names to make the information in /proc/pci, /proc/ioports and similar files comprehensible to the user. This database increases size of the kernel image by about 80KB, but it gets freed after the system boots up, so it doesn't take up kernel memory. Anyway, if you are building an installation floppy or kernel for an embedded system where kernel image size really matters, you can disable this feature and you'll get device ID numbers instead of names. When in doubt, say Y. Generic PCI hotplug support CONFIG_HOTPLUG_PCI Say Y here if you have a motherboard with a PCI Hotplug controller. This allows you to add and remove PCI cards while the machine is powered up and running. The file system pcihpfs must be mounted in order to interact with any PCI Hotplug controllers. This code 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 pci_hotplug.o. If you want to compile it as a module, say M here and read . When in doubt, say N. Compaq PCI Hotplug driver CONFIG_HOTPLUG_PCI_COMPAQ Say Y here if you have a motherboard with a Compaq PCI Hotplug controller. This code 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 cpqphp.o. If you want to compile it as a module, say M here and read . When in doubt, say N. PCI Compaq Hotplug controller NVRAM support CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM Say Y here if you have a Compaq server that has a PCI Hotplug controller. This will allow the PCI Hotplug driver to store the PCI system configuration options in NVRAM. When in doubt, say N. ACPI PCI Hotplug driver CONFIG_HOTPLUG_PCI_ACPI Say Y here if you have a system that supports PCI Hotplug using ACPI. This code 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 acpiphp.o. If you want to compile it as a module, say M here and read . MCA support CONFIG_MCA MicroChannel Architecture is found in some IBM PS/2 machines and laptops. It is a bus system similar to PCI or ISA. See (and especially the web page given there) before attempting to build an MCA bus kernel. Support for EISA-bus hardware CONFIG_EISA The Extended Industry Standard Architecture (EISA) bus was developed as an open alternative to the IBM MicroChannel bus. The EISA bus provided some of the features of the IBM MicroChannel bus while maintaining backward compatibility with cards made for the older ISA bus. The EISA bus saw limited use between 1988 and 1995 when it was made obsolete by the PCI bus. Say Y here if you are building a kernel for an EISA-based machine. Otherwise, say N. SGI Visual Workstation support CONFIG_VISWS The SGI Visual Workstation series is an IA32-based workstation based on SGI systems chips with some legacy PC hardware attached. Say Y here to create a kernel to run on the SGI 320 or 540. A kernel compiled for the Visual Workstation will not run on other PC boards and vice versa. See for more. SGI Visual Workstation framebuffer support CONFIG_FB_SGIVW SGI Visual Workstation support for framebuffer graphics. I2O support CONFIG_I2O The Intelligent Input/Output (I2O) architecture allows hardware drivers to be split into two parts: an operating system specific module called the OSM and an hardware specific module called the HDM. The OSM can talk to a whole range of HDM's, and ideally the HDM's are not OS dependent. This allows for the same HDM driver to be used under different operating systems if the relevant OSM is in place. In order for this to work, you need to have an I2O interface adapter card in your computer. This card contains a special I/O processor (IOP), thus allowing high speeds since the CPU does not have to deal with I/O. If you say Y here, you will get a choice of interface adapter drivers and OSM's with the following questions. This support 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 . You will get modules called i2o_core.o and i2o_config.o. If unsure, say N. I2O PCI support CONFIG_I2O_PCI Say Y for support of PCI bus I2O interface adapters. Currently this is the only variety supported, so you should say Y. This support is also available as a module called i2o_pci.o ( = 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 . I2O Block OSM CONFIG_I2O_BLOCK Include support for the I2O Block OSM. The Block OSM presents disk and other structured block devices to the operating system. This support is also available as a module called i2o_block.o ( = 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 . I2O LAN OSM CONFIG_I2O_LAN Include support for the LAN OSM. You will also need to include support for token ring or FDDI if you wish to use token ring or FDDI I2O cards with this driver. This support is also available as a module called i2o_lan.o ( = 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 . I2O SCSI OSM CONFIG_I2O_SCSI Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel I2O controller. You can use both the SCSI and Block OSM together if you wish. This support is also available as a module called i2o_scsi.o ( = 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 . I2O /proc support CONFIG_I2O_PROC If you say Y here and to "/proc file system support", you will be able to read I2O related information from the virtual directory /proc/i2o. This support is also available as a module called i2o_proc.o ( = 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 . Plug and Play support CONFIG_PNP Plug and Play (PnP) is a standard for peripherals which allows those peripherals to be configured by software, e.g. assign IRQ's or other parameters. No jumpers on the cards are needed, instead the values are provided to the cards from the BIOS, from the operating system, or using a user-space utility. Say Y here if you would like Linux to configure your Plug and Play devices. You should then also say Y to "ISA Plug and Play support", below. Alternatively, you can say N here and configure your PnP devices using the user space utilities contained in the isapnptools package. This support 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 . ISA Plug and Play support CONFIG_ISAPNP Say Y here if you would like support for ISA Plug and Play devices. Some information is in . This support is also available as a module called isapnp.o ( = 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 . If unsure, say Y. PNPBIOS support CONFIG_PNPBIOS Linux uses the PNPBIOS as defined in "Plug and Play BIOS Specification Version 1.0A May 5, 1994" to autodetect built-in mainboard resources (e.g. parallel port resources). Other features (e.g. change resources, ESCD, event notification, Docking station information, ISAPNP services) are not used. Note: ACPI is expected to supersede PNPBIOS some day, currently it co-exists nicely. See latest pcmcia-cs (stand-alone package) for a nice "lspnp" tools, or have a look at /proc/bus/pnp. If unsure, say Y. Support for hot-pluggable devices CONFIG_HOTPLUG Say Y here if you want to plug devices into your computer while the system is running, and be able to use them quickly. In many cases, the devices can likewise be unplugged at any time too. One well known example of this is PCMCIA- or PC-cards, credit-card size devices such as network cards, modems or hard drives which are plugged into slots found on all modern laptop computers. Another example, used on modern desktops as well as laptops, is USB. Enable HOTPLUG and KMOD, and build a modular kernel. Get agent software (at ) and install it. Then your kernel will automatically call out to a user mode "policy agent" (/sbin/hotplug) to load modules and set up software needed to use devices as you hotplug them. PCMCIA/CardBus support CONFIG_PCMCIA Say Y here if you want to attach PCMCIA- or PC-cards to your Linux computer. These are credit-card size devices such as network cards, modems or hard drives often used with laptops computers. There are actually two varieties of these cards: the older 16 bit PCMCIA cards and the newer 32 bit CardBus cards. If you want to use CardBus cards, you need to say Y here and also to "CardBus support" below. To use your PC-cards, you will need supporting software from David Hinds' pcmcia-cs package (see the file for location). Please also read the PCMCIA-HOWTO, available from . This driver is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). When compiled this way, there will be modules called pcmcia_core.o and ds.o. If you want to compile it as a module, say M here and read . CardBus card and (Yenta) bridge support CONFIG_CARDBUS CardBus is a bus mastering architecture for PC-cards, which allows for 32 bit PC-cards (the original PCMCIA standard specifies only a 16 bit wide bus). Many newer PC-cards are actually CardBus cards. This option enables support for CardBus PC Cards, as well as support for CardBus host bridges. Virtually all modern PCMCIA bridges are CardBus compatible. A "bridge" is the hardware inside your computer that PCMCIA cards are plugged into. To use your PC-cards, you will need supporting software from David Hinds' pcmcia-cs package (see the file for location). If unsure, say Y. i82092 compatible bridge support CONFIG_I82092 This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device, found in some older laptops and more commonly in evaluation boards for the chip. i82365 compatible host bridge support CONFIG_I82365 Say Y here to include support for ISA-bus PCMCIA host bridges that are register compatible with the Intel i82365. These are found on older laptops and ISA-bus card readers for desktop systems. A "bridge" is the hardware inside your computer that PCMCIA cards are plugged into. If unsure, say N. Databook TCIC host bridge support CONFIG_TCIC Say Y here to include support for the Databook TCIC family of PCMCIA host bridges. These are only found on a handful of old systems. "Bridge" is the name used for the hardware inside your computer that PCMCIA cards are plugged into. If unsure, say N. System V IPC CONFIG_SYSVIPC Inter Process Communication is a suite of library functions and system calls which let processes (running programs) synchronize and exchange information. It is generally considered to be a good thing, and some programs won't run unless you say Y here. In particular, if you want to run the DOS emulator dosemu under Linux (read the DOSEMU-HOWTO, available from ), you'll need to say Y here. You can find documentation about IPC with "info ipc" and also in section 6.4 of the Linux Programmer's Guide, available from . BSD Process Accounting CONFIG_BSD_PROCESS_ACCT If you say Y here, a user level program will be able to instruct the kernel (via a special system call) to write process accounting information to a file: whenever a process exits, information about that process will be appended to the file by the kernel. The information includes things such as creation time, owning user, command name, memory usage, controlling terminal etc. (the complete list is in the struct acct in ). It is up to the user level program to do useful things with this information. This is generally a good idea, so say Y. Sysctl support CONFIG_SYSCTL The sysctl interface provides a means of dynamically changing certain kernel parameters and variables on the fly without requiring a recompile of the kernel or reboot of the system. The primary interface consists of a system call, but if you say Y to "/proc file system support", a tree of modifiable sysctl entries will be generated beneath the /proc/sys directory. They are explained in the files in . Note that enabling this option will enlarge the kernel by at least 8 KB. As it is generally a good thing, you should say Y here unless building a kernel for install/rescue disks or your system is very limited in memory. # Choice: kcore Kernel core (/proc/kcore) format CONFIG_KCORE_ELF If you enabled support for /proc file system then the file /proc/kcore will contain the kernel core image. This can be used in gdb: $ cd /usr/src/linux ; gdb vmlinux /proc/kcore You have two choices here: ELF and A.OUT. Selecting ELF will make /proc/kcore appear in ELF core format as defined by the Executable and Linking Format specification. Selecting A.OUT will choose the old "a.out" format which may be necessary for some old versions of binutils or on some architectures. This is especially useful if you have compiled the kernel with the "-g" option to preserve debugging information. It is mainly used for examining kernel data structures on the live kernel so if you don't understand what this means or are not a kernel hacker, just leave it at its default value ELF. Select a.out format for /proc/kcore CONFIG_KCORE_AOUT Not necessary unless you're using a very out-of-date binutils version. You probably want KCORE_ELF. Kernel support for ELF binaries CONFIG_BINFMT_ELF ELF (Executable and Linkable Format) is a format for libraries and executables used across different architectures and operating systems. Saying Y here will enable your kernel to run ELF binaries and enlarge it by about 13 KB. ELF support under Linux has now all but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC) because it is portable (this does *not* mean that you will be able to run executables from different architectures or operating systems however) and makes building run-time libraries very easy. Many new executables are distributed solely in ELF format. You definitely want to say Y here. Information about ELF is contained in the ELF HOWTO available from . If you find that after upgrading from Linux kernel 1.2 and saying Y here, you still can't run any ELF binaries (they just crash), then you'll have to install the newest ELF runtime libraries, including ld.so (check the file for location and latest version). If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called binfmt_elf.o. Saying M or N here is dangerous because some crucial programs on your system might be in ELF format. Kernel support for a.out binaries CONFIG_BINFMT_AOUT A.out (Assembler.OUTput) is a set of formats for libraries and executables used in the earliest versions of UNIX. Linux used the a.out formats QMAGIC and ZMAGIC until they were replaced with the ELF format. As more and more programs are converted to ELF, the use for a.out will gradually diminish. If you disable this option it will reduce your kernel by one page. This is not much and by itself does not warrant removing support. However its removal is a good idea if you wish to ensure that absolutely none of your programs will use this older executable format. If you don't know what to answer at this point then answer Y. If someone told you "You need a kernel with QMAGIC support" then you'll have to say Y here. You may answer M to compile a.out support as a module and later load the module when you want to use a program or library in a.out format. The module will be called binfmt_aout.o. Saying M or N here is dangerous though, because some crucial programs on your system might still be in A.OUT format. OSF/1 v4 readv/writev compatibility CONFIG_OSF4_COMPAT Say Y if you are using OSF/1 binaries (like Netscape and Acrobat) with v4 shared libraries freely available from Compaq. If you're going to use shared libraries from Tru64 version 5.0 or later, say N. Kernel support for Linux/Intel ELF binaries CONFIG_BINFMT_EM86 Say Y here if you want to be able to execute Linux/Intel ELF binaries just like native Alpha binaries on your Alpha machine. For this to work, you need to have the emulator /usr/bin/em86 in place. You can get the same functionality by saying N here and saying Y to "Kernel support for MISC binaries". You may answer M to compile the emulation support as a module and later load the module when you want to use a Linux/Intel binary. The module will be called binfmt_em86.o. If unsure, say Y. Kernel support for SOM binaries CONFIG_BINFMT_SOM SOM is a binary executable format inherited from HP/UX. Say Y here to be able to load and execute SOM binaries directly. Kernel support for MISC binaries CONFIG_BINFMT_MISC If you say Y here, it will be possible to plug wrapper-driven binary formats into the kernel. You will like this especially when you use programs that need an interpreter to run like Java, Python or Emacs-Lisp. It's also useful if you often run DOS executables under the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from ). Once you have registered such a binary class with the kernel, you can start one of those programs simply by typing in its name at a shell prompt; Linux will automatically feed it to the correct interpreter. You can do other nice things, too. Read the file to learn how to use this feature, and for information about how to include Java support. You must say Y to "/proc file system support" (CONFIG_PROC_FS) to use this part of the kernel. You may say M here for module support and later load the module when you have use for it; the module is called binfmt_misc.o. If you don't know what to answer at this point, say Y. Kernel support for JAVA binaries CONFIG_BINFMT_JAVA If you say Y here, the kernel will load and execute Java J-code binaries directly. Note: this option is obsolete and scheduled for removal, use CONFIG_BINFMT_MISC instead. Solaris binary emulation CONFIG_SOLARIS_EMUL This is experimental code which will enable you to run (many) Solaris binaries on your SPARC Linux machine. This code 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 solaris.o. If you want to compile it as a module, say M here and read . SUN SME environment monitoring CONFIG_ENVCTRL Kernel support for temperature and fan monitoring on Sun SME machines. This code 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 envctrl.o. If you want to compile it as a module, say M here and read . # Choice: x86type Processor family CONFIG_M386 This is the processor type of your CPU. This information is used for optimizing purposes. In order to compile a kernel that can run on all x86 CPU types (albeit not optimally fast), you can specify "386" here. The kernel will not necessarily run on earlier architectures than the one you have chosen, e.g. a Pentium optimized kernel will run on a PPro, but not necessarily on a i486. Here are the settings recommended for greatest speed: - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI 486DLC/DLC2, UMC 486SX-S and NexGen Nx586. Only "386" kernels will run on a 386 class machine. - "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S. - "586" for generic Pentium CPUs, possibly lacking the TSC (time stamp counter) register. - "Pentium-Classic" for the Intel Pentium. - "Pentium-MMX" for the Intel Pentium MMX. - "Pentium-Pro" for the Intel Pentium Pro/Celeron/Pentium II. - "Pentium-III" for the Intel Pentium III and Celerons based on the Coppermine core. - "Pentium-4" for the Intel Pentium 4. - "K6" for the AMD K6, K6-II and K6-III (aka K6-3D). - "Athlon" for the AMD K7 family (Athlon/Duron/Thunderbird). - "Elan" for the AMD Elan family (Elan SC400/SC410). - "Crusoe" for the Transmeta Crusoe series. - "Winchip-C6" for original IDT Winchip. - "Winchip-2" for IDT Winchip 2. - "Winchip-2A" for IDT Winchips with 3dNow! capabilities. - "CyrixIII" for VIA Cyrix III or VIA C3. If you don't know what to do, choose "386". 486 CONFIG_M486 Select this for a x486 processor, ether Intel or one of the compatible processors from AMD, Cyrix, IBM, or Intel. Includes DX, DX2, and DX4 variants; also SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S. 586/K5/5x86/6x86/6x86MX CONFIG_M586 Select this for an x586 or x686 processor such as the AMD K5, the Intel 5x86 or 6x86, or the Intel 6x86MX. This choice does not assume the RDTSC instruction. Pentium Classic CONFIG_M586TSC Select this for a Pentium Classic processor with the RDTSC (Read Time Stamp Counter) instruction for benchmarking. 32-bit PDC CONFIG_PDC_NARROW Saying Y here will allow developers with a C180, C200, C240, C360, J200, J210, and/or a J2240 to test 64-bit kernels by providing a wrapper for the 32-bit PDC calls. Since the machines which require this option do not support over 4G of RAM, this option is targeted for developers of these machines wishing to test changes on both 32-bit and 64-bit configurations. If unsure, say N. VGA text console CONFIG_VGA_CONSOLE Saying Y here will allow you to use Linux in text mode through a display that complies with the generic VGA standard. Virtually everyone wants that. The program SVGATextMode can be used to utilize SVGA video cards to their full potential in text mode. Download it from . Say Y. Distribute interrupts on all CPUs by default CONFIG_IRQ_ALL_CPUS This option gives the kernel permission to distribute IRQs across multiple CPUs. Saying N here will route all IRQs to the first CPU. Generally SMP PowerMacs can answer Y. SMP IBM CHRP boxes or Power3 boxes should say N for now. Video mode selection support CONFIG_VIDEO_SELECT This enables support for text mode selection on kernel startup. If you want to take advantage of some high-resolution text mode your card's BIOS offers, but the traditional Linux utilities like SVGATextMode don't, you can say Y here and set the mode using the "vga=" option from your boot loader (lilo or loadlin) or set "vga=ask" which brings up a video mode menu on kernel startup. (Try "man bootparam" or see the documentation of your boot loader about how to pass options to the kernel.) Read the file for more information about the Video mode selection support. If unsure, say N. Support for frame buffer devices CONFIG_FB The frame buffer device provides an abstraction for the graphics hardware. It represents the frame buffer of some video hardware and allows application software to access the graphics hardware through a well-defined interface, so the software doesn't need to know anything about the low-level (hardware register) stuff. Frame buffer devices work identically across the different architectures supported by Linux and make the implementation of application programs easier and more portable; at this point, an X server exists which uses the frame buffer device exclusively. On several non-X86 architectures, the frame buffer device is the only way to use the graphics hardware. The device is accessed through special device nodes, usually located in the /dev directory, i.e. /dev/fb*. You need an utility program called fbset to make full use of frame buffer devices. Please read and the Framebuffer-HOWTO at for more information. Say Y here and to the driver for your graphics board below if you are compiling a kernel for a non-x86 architecture. If you are compiling for the x86 architecture, you can say Y if you want to play with it, but it is not essential. Please note that running graphical applications that directly touch the hardware (e.g. an accelerated X server) and that are not frame buffer device-aware may cause unexpected results. If unsure, say N. Acorn VIDC support CONFIG_FB_ACORN This is the frame buffer device driver for the Acorn VIDC graphics hardware found in Acorn RISC PCs and other ARM-based machines. If unsure, say N. Permedia2 support CONFIG_FB_PM2 This is the frame buffer device driver for the Permedia2 AGP frame buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a product page at . Enable FIFO disconnect feature CONFIG_FB_PM2_FIFO_DISCONNECT Support the Permedia2 FIFOI disconnect feature (see CONFIG_FB_PM2). Generic Permedia2 PCI board support CONFIG_FB_PM2_PCI Say Y to enable support for Permedia2 AGP frame buffer card from 3Dlabs (aka `Graphic Blaster Exxtreme') on the PCI bus. Phase5 CVisionPPC/BVisionPPC support CONFIG_FB_PM2_CVPPC Say Y to enable support for the Amiga Phase 5 CVisionPPC BVisionPPC framebuffer cards. Phase 5 is no longer with us, alas. Amiga native chipset support CONFIG_FB_AMIGA This is the frame buffer device driver for the builtin graphics chipset found in Amigas. 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 amifb.o. If you want to compile it as a module, say M here and read . Amiga OCS chipset support CONFIG_FB_AMIGA_OCS This enables support for the original Agnus and Denise video chips, found in the Amiga 1000 and most A500's and A2000's. If you intend to run Linux on any of these systems, say Y; otherwise say N. Amiga ECS chipset support CONFIG_FB_AMIGA_ECS This enables support for the Enhanced Chip Set, found in later A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If you intend to run Linux on any of these systems, say Y; otherwise say N. Amiga AGA chipset support CONFIG_FB_AMIGA_AGA This enables support for the Advanced Graphics Architecture (also known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T and CD32. If you intend to run Linux on any of these systems, say Y; otherwise say N. Amiga CyberVision support CONFIG_FB_CYBER This enables support for the Cybervision 64 graphics card from Phase5. Please note that its use is not all that intuitive (i.e. if you have any questions, be sure to ask!). Say N unless you have a Cybervision 64 or plan to get one before you next recompile the kernel. Please note that this driver DOES NOT support the Cybervision 64 3D card, as they use incompatible video chips. CyberPro 20x0 support CONFIG_FB_CYBER2000 This enables support for the Integraphics CyberPro 20x0 and 5000 VGA chips used in the Rebel.com Netwinder and other machines. Say Y if you have a NetWinder or a graphics card containing this device, otherwise say N. Amiga CyberVision3D support CONFIG_FB_VIRGE This enables support for the Cybervision 64/3D graphics card from Phase5. Please note that its use is not all that intuitive (i.e. if you have any questions, be sure to ask!). Say N unless you have a Cybervision 64/3D or plan to get one before you next recompile the kernel. Please note that this driver DOES NOT support the older Cybervision 64 card, as they use incompatible video chips. Amiga RetinaZ3 support CONFIG_FB_RETINAZ3 This enables support for the Retina Z3 graphics card. Say N unless you have a Retina Z3 or plan to get one before you next recompile the kernel. Cirrus Logic generic driver CONFIG_FB_CLGEN This enables support for Cirrus Logic GD542x/543x based boards on Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum. If you have a PCI-based system, this enables support for these chips: GD-543x, GD-544x, GD-5480. Please read the file . Say N unless you have such a graphics board or plan to get one before you next recompile the kernel. Apollo support CONFIG_APOLLO Say Y here if you want to run Linux on an MC680x0-based Apollo Domain workstation such as the DN3500. Apollo 3c505 "EtherLink Plus" support CONFIG_APOLLO_ELPLUS Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card. If you don't have one made for Apollos, you can use one from a PC, except that your Apollo won't be able to boot from it (because the code in the ROM will be for a PC). Atari native chipset support CONFIG_FB_ATARI This is the frame buffer device driver for the builtin graphics chipset found in Ataris. Amiga FrameMaster II/Rainbow II support CONFIG_FB_FM2 This is the frame buffer device driver for the Amiga FrameMaster card from BSC (exhibited 1992 but not shipped as a CBM product). Open Firmware frame buffer device support CONFIG_FB_OF Say Y if you want support with Open Firmware for your graphics board. S3 Trio frame buffer device support CONFIG_FB_S3TRIO If you have a S3 Trio say Y. Say N for S3 Virge. 3Dfx Banshee/Voodoo3 display support CONFIG_FB_3DFX This driver supports graphics boards with the 3Dfx Banshee/Voodoo3 chips. Say Y if you have such a graphics board. 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 tdfxfb.o. If you want to compile it as a module, say M here and read . nVidia Riva support CONFIG_FB_RIVA This driver supports graphics boards with the nVidia Riva/Geforce chips. Say Y if you have such a graphics board. 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 rivafb.o. If you want to compile it as a module, say M here and read . Trident Blade/Image support CONFIG_FB_TRIDENT This driver is supposed to support graphics boards with the Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops but also on some motherboards.Read Say Y if you have such a graphics board. 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 rivafb.o. If you want to compile it as a module, say M here and read . ATI Mach64 display support CONFIG_FB_ATY This driver supports graphics boards with the ATI Mach64 chips. Say Y if you have such a graphics board. 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 atyfb.o. If you want to compile it as a module, say M here and read . ATI Rage128 display support CONFIG_FB_ATY128 This driver supports graphics boards with the ATI Rage128 chips. Say Y if you have such a graphics board and read . 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 aty128fb.o. If you want to compile it as a module, say M here and read . Maxine (Personal DECstation) onboard framebuffer support CONFIG_FB_MAXINE Support for the onboard framebuffer (1024x768x8) in the Personal DECstation series (Personal DECstation 5000/20, /25, /33, /50, Codename "Maxine"). PMAG-BA TURBOchannel framebuffer support CONFIG_FB_PMAG_BA Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8) used mainly in the MIPS-based DECstation series. PMAGB-B TURBOchannel framebuffer support CONFIG_FB_PMAGB_B Support for the PMAGB-B TURBOchannel framebuffer card used mainly in the MIPS-based DECstation series. The card is currently only supported in 1280x1024x8 mode. FutureTV PCI card CONFIG_ARCH_FTVPCI Say Y here if you intend to run this kernel on a FutureTV (nee Nexus Electronics) StrongARM PCI card. ANAKIN Vehicle Telematics Platform CONFIG_ARCH_ANAKIN The Anakin is a StrongArm based SA110 - 2 DIN Vehicle Telematics Platform. 64MB SDRAM - 4 Mb Flash - Compact Flash Interface - 1 MB VRAM On board peripherals: * Front display: 400x234 16 bit TFT touchscreen * External independent second screen interface * CAN controller SJA1000 * USB host controller * 6 channel video codec with hardware overlay * Smartcard reader * IrDa Modules interfaced over the Multi Media Extension slots: * A communication card Wavecom GPRS modem uBlock GPS Bosch DAB module * An audio card ( 4 * 40W, AC97 Codec, I2S) Altera Excalibur XA10 Dev Board ARCH_CAMELOT This enables support for Altera's Excalibur XA10 development board. If you would like to build your kernel to run on one of these boards then you must say 'Y' here. Otherwise say 'N' Link-Up Systems LCD support CONFIG_FB_L7200 This driver supports the L7200 Color LCD. Say Y if you want graphics support. NeoMagic display support (EXPERIMENTAL) CONFIG_FB_NEOMAGIC This driver supports notebooks with NeoMagic PCI chips. Say Y if you have such a graphics card. 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 neofb.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. PowerMac "control" frame buffer device support CONFIG_FB_CONTROL This driver supports a frame buffer for the graphics adapter in the Power Macintosh 7300 and others. PowerMac "platinum" frame buffer device support CONFIG_FB_PLATINUM This driver supports a frame buffer for the "platinum" graphics adapter in some Power Macintoshes. PowerMac "valkyrie" frame buffer device support CONFIG_FB_VALKYRIE This driver supports a frame buffer for the "valkyrie" graphics adapter in some Power Macintoshes. Chips 65550 display support CONFIG_FB_CT65550 This is the frame buffer device driver for the Chips & Technologies 65550 graphics chip in PowerBooks. TGA frame buffer support CONFIG_FB_TGA This is the frame buffer device driver for generic TGA graphic cards. Say Y if you have one of those. VESA VGA graphics console CONFIG_FB_VESA This is the frame buffer device driver for generic VESA 2.0 compliant graphic cards. The older VESA 1.2 cards are not supported. You will get a boot time penguin logo at no additional cost. Please read . If unsure, say Y. VGA 16-color planar support CONFIG_FBCON_VGA_PLANES This low level frame buffer console driver enable the kernel to use the 16-color planar modes of the old VGA cards where the bits of each pixel are separated into 4 planes. Only answer Y here if you have a (very old) VGA card that isn't VESA 2 compatible. VGA 16-color graphics console CONFIG_FB_VGA16 This is the frame buffer device driver for VGA 16 color graphic cards. Say Y if you have such a card. This code is also available as a module. If you want to compile it as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called vga16fb.o. Generic STI frame buffer device support CONFIG_FB_STI STI refers to the HP "Standard Text Interface" which is a set of BIOS routines contained in a ROM chip in HP PA-RISC based machines. Enabling this option will implement the linux framebuffer device and an fbcon color text console using calls to the STI BIOS routines. The HP framebuffer device is usually planar, uses a strange memory layout, and changing the plane mask to create colored pixels requires a call to the STI routines, so do not expect /dev/fb to actually be useful. However, it is the best we have as far as graphics on the HP chipsets due to lack of hardware level documentation for the various on-board HP chipsets used in these systems. It is sufficient for basic text console functions, including fonts. You should probably enable this option, unless you are having trouble getting video when booting the kernel (make sure it isn't just that you are running the console on the serial port, though). Really old HP boxes may not have STI, and must use the PDC BIOS console or the IODC BIOS. Select other compiled-in fonts CONFIG_FBCON_FONTS Say Y here if you would like to use fonts other than the default your frame buffer console usually use. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about foreign fonts. If unsure, say N (the default choices are safe). VGA 8x16 font CONFIG_FONT_8x16 This is the "high resolution" font for the VGA frame buffer (the one provided by the VGA text console 80x25 mode. If unsure, say Y. Support only 8 pixels wide fonts CONFIG_FBCON_FONTWIDTH8_ONLY Answer Y here will make the kernel provide only the 8x8 fonts (these are the less readable). If unsure, say N. Sparc console 8x16 font CONFIG_FONT_SUN8x16 This is the high resolution console font for Sun machines. Say Y. Sparc console 12x22 font (not supported by all drivers) CONFIG_FONT_SUN12x22 This is the high resolution console font for Sun machines with very big letters (like the letters used in the SPARC PROM). If the standard font is unreadable for you, say Y, otherwise say N. VGA 8x8 font CONFIG_FONT_8x8 This is the "high resolution" font for the VGA frame buffer (the one provided by the text console 80x50 (and higher) modes). Note that this is a poor quality font. The VGA 8x16 font is quite a lot more readable. Given the resolution provided by the frame buffer device, answer N here is safe. Mac console 6x11 font (not supported by all drivers) CONFIG_FONT_6x11 Small console font with Macintosh-style high-half glyphs. Some Mac framebuffer drivers don't support this one at all. Pearl (old m68k) console 8x8 font CONFIG_FONT_PEARL_8x8 Small console font with PC-style control-character and high-half glyphs. Acorn console 8x8 font CONFIG_FONT_ACORN_8x8 Small console font with PC-style control characters and high-half glyphs. Backward compatibility mode for Xpmac CONFIG_FB_COMPAT_XPMAC If you use the Xpmac X server (common with mklinux), you'll need to say Y here to use X. You should consider changing to XFree86 which includes a server that supports the frame buffer device directly (XF68_FBDev). Hercules (HGA) mono graphics support CONFIG_FB_HGA Say Y here if you have a Hercules mono graphics card. This 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 hgafb.o. If you want to compile it as a module, say M here and read . As this card technology is 15 years old, most people will answer N here. Epson 1355 framebuffer support CONFIG_FB_E1355 Build in support for the SED1355 Epson Research Embedded RAMDAC LCD/CRT Controller (since redesignated as the S1D13505) as a framebuffer. Product specs at . Dreamcast Frame Buffer support CONFIG_FB_DC Say Y here to enable support for the framebuffer on the Sega Dreamcast. This driver is also available as a module, dcfb.o. Register Base Address CONFIG_E1355_REG_BASE Epson SED1355/S1D13505 LCD/CRT controller register base address. See the manuals at for discussion. Framebuffer Base Address CONFIG_E1355_FB_BASE Epson SED1355/S1D13505 LCD/CRT controller memory base address. See the manuals at for discussion. NEC PowerVR 2 display support CONFIG_FB_PVR2 Say Y here if you have a PowerVR 2 card in your box. If you plan to run linux on your Dreamcast, you will have to say Y here. This driver may or may not work on other PowerVR 2 cards, but is totally untested. Use at your own risk. If unsure, say N. This 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 pvr2fb.o. If you want to compile it as a module, say M here and read . You can pass several parameters to the driver at boot time or at module load time. The parameters look like "video=pvr2:XXX", where the meaning of XXX can be found at the end of the main source file (). Please see the file . Debug pvr2fb CONFIG_FB_PVR2_DEBUG Say Y here if you wish for the pvr2fb driver to print out debugging messages. Most people will want to say N here. If unsure, you will also want to say N. Matrox unified accelerated driver CONFIG_FB_MATROX Say Y here if you have a Matrox Millennium, Millennium II, Mystique, Mystique 220, Productiva G100, Mystique G200, Millennium G200, Matrox G400, G450 or G550 card in your box. At this time, support for the G-series digital output is almost non-existant. This 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 matroxfb.o. If you want to compile it as a module, say M here and read . You can pass several parameters to the driver at boot time or at module load time. The parameters look like "video=matrox:XXX", and are described in . Matrox Millennium I/II support CONFIG_FB_MATROX_MILLENIUM Say Y here if you have a Matrox Millennium or Matrox Millennium II video card. If you select "Advanced lowlevel driver options" below, you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can also use font widths different from 8. Matrox Mystique support CONFIG_FB_MATROX_MYSTIQUE Say Y here if you have a Matrox Mystique or Matrox Mystique 220 video card. If you select "Advanced lowlevel driver options" below, you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can also use font widths different from 8. Matrox G100/G200/G400/G450/G550 support CONFIG_FB_MATROX_G100 Say Y here if you have a Matrox G100, G200, G400, G450, or G550 based video card. If you select "Advanced lowlevel driver options", you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can also use font widths different from 8. If you need support for G400 secondary head, you must first say Y to "I2C support" and "I2C bit-banging support" in the character devices section, and then to "Matrox I2C support" and "G400 second head support" here in the framebuffer section. If you have G550, you must also compile support for G450/G550 secondary head into kernel, otherwise picture will be shown only on the output you are probably not using... If you need support for G450 or G550 secondary head, say Y to "Matrox G450/G550 second head support" below. Matrox I2C support CONFIG_FB_MATROX_I2C This drivers creates I2C buses which are needed for accessing the DDC (I2C) bus present on all Matroxes, an I2C bus which interconnects Matrox optional devices, like MGA-TVO on G200 and G400, and the secondary head DDC bus, present on G400 only. You can say Y or M here if you want to experiment with monitor detection code. You must say Y or M here if you want to use either second head of G400 or MGA-TVO on G200 or G400. If you compile it as module, it will create a module named i2c-matroxfb.o. Matrox G400 second head support CONFIG_FB_MATROX_MAVEN WARNING !!! This support does not work with G450 !!! Say Y or M here if you want to use a secondary head (meaning two monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary head is not compatible with accelerated XFree 3.3.x SVGA servers - secondary head output is blanked while you are in X. With XFree 3.9.17 preview you can use both heads if you use SVGA over fbdev or the fbdev driver on first head and the fbdev driver on second head. If you compile it as module, two modules are created, matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for both G200 and G400, matroxfb_crtc2 is needed only by G400. You must also load i2c-matroxfb to get it to run. The driver starts in monitor mode and you must use the matroxset tool (available at ) to switch it to PAL or NTSC or to swap primary and secondary head outputs. Secondary head driver also always start in 640x480 resolution, you must use fbset to change it. Also do not forget that second head supports only 16 and 32 bpp packed pixels, so it is a good idea to compile them into the kernel too. You can use only some font widths, as the driver uses generic painting procedures (the secondary head does not use acceleration engine). Matrox G450 second head support CONFIG_FB_MATROX_G450 Say Y or M here if you want to use a secondary head (meaning two monitors in parallel) on G450, or if you are using analog output of G550. If you compile it as module, two modules are created, matroxfb_crtc2.o and matroxfb_g450.o. Both modules are needed if you want two independent display devices. The driver starts in monitor mode and currently does not support output in TV modes. You must use the matroxset tool (available at ) to swap primary and secondary head outputs. Secondary head driver always start in 640x480 resolution and you must use fbset to change it. Note on most G550 cards the analog output is the secondary head, so you will need to say Y here to use it. Also do not forget that second head supports only 16 and 32 bpp packed pixels, so it is a good idea to compile them into the kernel too. You can use only some font widths, as the driver uses generic painting procedures (the secondary head does not use acceleration engine). Matrox unified driver multihead support CONFIG_FB_MATROX_MULTIHEAD Say Y here if you have more than one (supported) Matrox device in your computer and you want to use all of them for different monitors ("multihead"). If you have only one device, you should say N because the driver compiled with Y is larger and a bit slower, especially on ia32 (ix86). If you said M to "Matrox unified accelerated driver" and N here, you will still be able to use several Matrox devices simultaneously: insert several instances of the module matroxfb.o into the kernel with insmod, supplying the parameter "dev=N" where N is 0, 1, etc. for the different Matrox devices. This method is slightly faster but uses 40 KB of kernel memory per Matrox card. There is no need for enabling 'Matrox multihead support' if you have only one Matrox card in the box. 3Dfx Voodoo Graphics / Voodoo2 frame buffer support CONFIG_FB_VOODOO1 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or Voodoo2 (cvg) based graphics card. This 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 sstfb.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. WARNING: Do not use any application that uses the 3D engine (namely glide) while using this driver. Please read the file Documentation/fb/README-sstfb.txt for supported options and other important info support. MDA text console (dual-headed) CONFIG_MDA_CONSOLE Say Y here if you have an old MDA or monochrome Hercules graphics adapter in your system acting as a second head ( = video card). You will then be able to use two monitors with your Linux system. Do not say Y here if your MDA card is the primary card in your system; the normal VGA driver will handle it. This 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 mdacon.o. If you want to compile it as a module, say M here and read . If unsure, say N. SBUS and UPA framebuffers CONFIG_FB_SBUS Say Y if you want support for SBUS or UPA based frame buffer device. Creator/Creator3D support CONFIG_FB_CREATOR This is the frame buffer device driver for the Creator and Creator3D graphics boards. CGsix (GX,TurboGX) support CONFIG_FB_CGSIX This is the frame buffer device driver for the CGsix (GX, TurboGX) frame buffer. BWtwo support CONFIG_FB_BWTWO This is the frame buffer device driver for the BWtwo frame buffer. CGthree support CONFIG_FB_CGTHREE This is the frame buffer device driver for the CGthree frame buffer. CGfourteen (SX) support CONFIG_FB_CGFOURTEEN This is the frame buffer device driver for the CGfourteen frame buffer on Desktop SPARCsystems with the SX graphics option. P9100 (Sparcbook 3 only) support CONFIG_FB_P9100 This is the frame buffer device driver for the P9100 card supported on Sparcbook 3 machines. Leo (ZX) support CONFIG_FB_LEO This is the frame buffer device driver for the SBUS-based Sun ZX (leo) frame buffer cards. IGA 168x display support CONFIG_FB_IGA This is the framebuffer device for the INTERGRAPHICS 1680 and successor frame buffer cards. TCX (SS4/SS5 only) support CONFIG_FB_TCX This is the frame buffer device driver for the TCX 24/8bit frame buffer. HD64461 Frame Buffer support CONFIG_FB_HIT This is the frame buffer device driver for the Hitachi HD64461 LCD frame buffer card. SIS acceleration CONFIG_FB_SIS This is the frame buffer device driver for the SiS 630 and 640 Super Socket 7 UMA cards. Specs available at . SIS 630/540/730 support CONFIG_FB_SIS_300 This is the frame buffer device driver for the SiS 630 and related Super Socket 7 UMA cards. Specs available at . SIS 315H/315 support CONFIG_FB_SIS_315 This is the frame buffer device driver for the SiS 315 graphics card. Specs available at . IMS Twin Turbo display support CONFIG_FB_IMSTT The IMS Twin Turbo is a PCI-based frame buffer card bundled with many Macintosh and compatible computers. CONFIG_FB_TX3912 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core; see . Say Y here to enable kernel support for the on-board framebuffer. Virtual Frame Buffer support (ONLY FOR TESTING!) CONFIG_FB_VIRTUAL This is a `virtual' frame buffer device. It operates on a chunk of unswappable kernel memory instead of on the memory of a graphics board. This means you cannot see any output sent to this frame buffer device, while it does consume precious memory. The main use of this frame buffer device is testing and debugging the frame buffer subsystem. Do NOT enable it for normal systems! To protect the innocent, it has to be enabled explicitly at boot time using the kernel option `video=vfb:'. This 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 vfb.o. If you want to compile it as a module, say M here and read . If unsure, say N. Mach64 CT/VT/GT/LT (incl. 3D RAGE) support CONFIG_FB_ATY_CT Say Y here to support use of ATI's 64-bit Rage boards (or other boards based on the Mach64 CT, VT, GT, and LT chipsets) as a framebuffer device. The ATI product support page for these boards is at . Sony Vaio Picturebook laptop LCD panel support CONFIG_FB_ATY_CT_VAIO_LCD Say Y here if you want to use the full width of the Sony Vaio Picturebook laptops LCD panels (you will get a 128x30 console). Note that you need to activate this mode using the 'vga=0x301' option from your boot loader (lilo or loadlin). See the documentation of your boot loader about how to pass options to the kernel. Mach64 GX support CONFIG_FB_ATY_GX Say Y here to support use of the ATI Mach64 Graphics Expression board (or other boards based on the Mach64 GX chipset) as a framebuffer device. The ATI product support page for these boards is at . ATI Radeon display support CONFIG_FB_RADEON Choose this option if you want to use an ATI Radeon graphics card as a framebuffer device. There are both PCI and AGP versions. You don't need to choose this to run the Radeon in plain VGA mode. There is a product page at . SA-1100 LCD support CONFIG_FB_SA1100 This is a framebuffer device for the SA-1100 LCD Controller. See for information on framebuffer devices. If you plan to use the LCD display with your SA-1100 system, say Y here. Advanced low level driver options CONFIG_FBCON_ADVANCED The frame buffer console uses character drawing routines that are tailored to the specific organization of pixels in the memory of your graphics hardware. These are called the low level frame buffer console drivers. Note that they are used for text console output only; they are NOT needed for graphical applications. If you say N here, the needed low level drivers are automatically enabled, depending on what frame buffer devices you selected above. This is recommended for most users. If you say Y here, you have more fine-grained control over which low level drivers are enabled. You can e.g. leave out low level drivers for color depths you do not intend to use for text consoles. Low level frame buffer console drivers can be modules ( = code which can be inserted and removed from the running kernel whenever you want). The modules will be called fbcon-*.o. If you want to compile (some of) them as modules, read . If unsure, say N. Monochrome support CONFIG_FBCON_MFB This is the low level frame buffer console driver for monochrome (2 colors) packed pixels. 2 bpp packed pixels support CONFIG_FBCON_CFB2 This is the low level frame buffer console driver for 2 bits per pixel (4 colors) packed pixels. 4 bpp packed pixels support CONFIG_FBCON_CFB4 This is the low level frame buffer console driver for 4 bits per pixel (16 colors) packed pixels. 8 bpp packed pixels support CONFIG_FBCON_CFB8 This is the low level frame buffer console driver for 8 bits per pixel (256 colors) packed pixels. 16 bpp packed pixels support CONFIG_FBCON_CFB16 This is the low level frame buffer console driver for 15 or 16 bits per pixel (32K or 64K colors, also known as `hicolor') packed pixels. 24 bpp packed pixels support CONFIG_FBCON_CFB24 This is the low level frame buffer console driver for 24 bits per pixel (16M colors, also known as `truecolor') packed pixels. It is NOT for `sparse' 32 bits per pixel mode. 32 bpp packed pixels support CONFIG_FBCON_CFB32 This is the low level frame buffer console driver for 32 bits per pixel (16M colors, also known as `truecolor') sparse packed pixels. Amiga bitplanes support CONFIG_FBCON_AFB This is the low level frame buffer console driver for 1 to 8 bitplanes (2 to 256 colors) on Amiga. Amiga interleaved bitplanes support CONFIG_FBCON_ILBM This is the low level frame buffer console driver for 1 to 8 interleaved bitplanes (2 to 256 colors) on Amiga. Atari interleaved bitplanes (2 planes) support CONFIG_FBCON_IPLAN2P2 This is the low level frame buffer console driver for 2 interleaved bitplanes (4 colors) on Atari. Atari interleaved bitplanes (4 planes) support CONFIG_FBCON_IPLAN2P4 This is the low level frame buffer console driver for 4 interleaved bitplanes (16 colors) on Atari. Atari interleaved bitplanes (8 planes) support CONFIG_FBCON_IPLAN2P8 This is the low level frame buffer console driver for 8 interleaved bitplanes (256 colors) on Atari. Mac variable bpp packed pixels support CONFIG_FBCON_MAC This is the low level frame buffer console driver for 1/2/4/8/16/32 bits per pixel packed pixels on Mac. It supports variable font widths for low resolution screens. 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. HGA monochrome support CONFIG_FBCON_HGA This is the low level frame buffer console driver for Hercules mono graphics cards. VGA characters/attributes support CONFIG_FBCON_VGA This is the low level frame buffer console driver for VGA text mode; it is used by frame buffer device drivers that support VGA text mode. Parallel-port support CONFIG_PARPORT If you want to use devices connected to your machine's parallel port (the connector at the computer with 25 holes), e.g. printer, ZIP drive, PLIP link (Parallel Line Internet Protocol is mainly used to create a mini network by connecting the parallel ports of two local machines) etc., then you need to say Y here; please read and . For extensive information about drivers for many devices attaching to the parallel port see on the WWW. It is possible to share a single parallel port among several devices and it is safe to compile all the corresponding drivers into the kernel. If you want to compile parallel port support as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called parport.o. If you have more than one parallel port and want to specify which port and IRQ to be used by this driver at module load time, take a look at . If unsure, say Y. PC-style hardware CONFIG_PARPORT_PC You should say Y here if you have a PC-style parallel port. All IBM PC compatible computers and some Alphas have PC-style parallel ports. This code is also available as a module. If you want to compile it as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called parport_pc.o. If unsure, say Y. Parallel+serial PCI multi-IO card support CONFIG_PARPORT_SERIAL This adds support for multi-IO PCI cards that have parallel and serial ports. You should say Y or M here. If you say M, the module will be called parport_serial.o. Use FIFO/DMA if available CONFIG_PARPORT_PC_FIFO Many parallel port chipsets provide hardware that can speed up printing. Say Y here if you want to take advantage of that. As well as actually having a FIFO, or DMA capability, the kernel will need to know which IRQ the parallel port has. By default, parallel port interrupts will not be used, and so neither will the FIFO. See to find out how to specify which IRQ/DMA to use. SuperIO chipset support CONFIG_PARPORT_PC_SUPERIO Saying Y here enables some probes for Super-IO chipsets in order to find out things like base addresses, IRQ lines and DMA channels. It is safe to say N. Support for PCMCIA management for PC-style ports CONFIG_PARPORT_PC_PCMCIA Say Y here if you need PCMCIA support for your PC-style parallel ports. If unsure, say N. 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 . The module will be called parport_cs.o Support foreign hardware CONFIG_PARPORT_OTHER Say Y here if you want to be able to load driver modules to support other non-standard types of parallel ports. This causes a performance loss, so most people say N. Amiga built-in parallel port support CONFIG_PARPORT_AMIGA Say Y here if you need support for the parallel port hardware on Amiga machines. This code is also available as a module (say M), called parport_amiga.o. If in doubt, saying N is the safe plan. Atari built-in parallel port support CONFIG_PARPORT_ATARI Say Y here if you need support for the parallel port hardware on Atari machines. This code is also available as a module (say M), called parport_atari.o. If in doubt, saying N is the safe plan. Multiface III parallel port support CONFIG_PARPORT_MFC3 Say Y here if you need parallel port support for the MFC3 card. This code is also available as a module (say M), called parport_mfc3.o. If in doubt, saying N is the safe plan. Support IEEE 1284 status readback CONFIG_PRINTER_READBACK If you have a device on your parallel port that support this protocol, this option will allow the device to report its status. It is safe to say Y. IEEE 1284 transfer modes CONFIG_PARPORT_1284 If you have a printer that supports status readback or device ID, or want to use a device that uses enhanced parallel port transfer modes such as EPP and ECP, say Y here to enable advanced IEEE 1284 transfer modes. Also say Y if you want device ID information to appear in /proc/sys/dev/parportYYDELETEMEYYmsr - Model-specific register support CONFIG_X86_MSR This device gives privileged processes access to the x86 Model-Specific Registers (MSRs). It is a character device with major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr. MSR accesses are directed to a specific CPU on multi-processor systems. 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 . The module will be called msr.o /dev/cpu/*/cpuid - CPU information support CONFIG_X86_CPUID This device gives processes access to the x86 CPUID instruction to be executed on a specific processor. It is a character device with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to /dev/cpu/31/cpuid. 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 . The module will be called cpuid.o SBC-60XX Watchdog Timer CONFIG_60XX_WDT This driver can be used with the watchdog timer found on some single board computers, namely the 6010 PII based computer. It may well work with other cards. It reads port 0x443 to enable and re-set the watchdog timer, and reads port 0x45 to disable the watchdog. If you have a card that behave in similar ways, you can probably make this driver work with your card as well. You can compile this driver directly into the kernel, or use it as a module. The module will be called sbc60xxwdt.o. Eurotech CPU-1220/1410 Watchdog Timer CONFIG_EUROTECH_WDT Enable support for the watchdog timer on the Eurotech CPU-1220 and CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product information are at . W83877F Watchdog Timer CONFIG_W83877F_WDT This is the driver for the hardware watchdog on the W83877F chipset as used in EMACS PC-104 motherboards (and may work on others). This watchdog simply watches your kernel to make sure it doesn't freeze, and if it does, it reboots your computer after a certain amount of time. You can compile this driver directly into the kernel, or use it as a module. The module will be called w83877f_wdt.o. SC520 (AMD Elan) Watchdog Timer CONFIG_SC520_WDT This is the driver for the hardware watchdog built in to the AMD "Elan" SC520 microcomputer commonly used in embedded systems. This watchdog simply watches your kernel to make sure it doesn't freeze, and if it does, it reboots your computer after a certain amount of time. You can compile this driver directly into the kernel, or use it as a module. The module will be called sc520_wdt.o. Enhanced Real Time Clock Support CONFIG_RTC If you say Y here and create a character special file /dev/rtc with major number 10 and minor number 135 using mknod ("man mknod"), you will get access to the real time clock (or hardware clock) built into your computer. Every PC has such a clock built in. It can be used to generate signals from as low as 1Hz up to 8192Hz, and can also be used as a 24 hour alarm. It reports status information via the file /proc/driver/rtc and its behaviour is set by various ioctls on /dev/rtc. If you run Linux on a multiprocessor machine and said Y to "Symmetric Multi Processing" above, you should say Y here to read and set the RTC in an SMP compatible fashion. If you think you have a use for such a device (such as periodic data sampling), then say Y here, and read for details. 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 is called rtc.o. If you want to compile it as a module, say M here and read . Tadpole ANA H8 Support CONFIG_H8 The Hitachi H8/337 is a microcontroller used to deal with the power and thermal environment. If you say Y here, you will be able to communicate with it via a character special device. If unsure, say N. /dev/profile support CONFIG_KERNPROF Saying Y here will compile in support for kernel profiling. To use it you need to create the character special device /dev/profile with major 192 and minor 0 using mknod. User-level commands such as kernprof and gprof can then be used to control the provided facilities and to generate user-readable profiles. If you do not want to profile the kernel, say N here. This driver is also available as a module (i.e., code which can be inserted in and removed from the running kernel whenever you want). The module will be called kernprof.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. Function-entry instrumentation CONFIG_MCOUNT This will instrument the kernel with calls to mcount(), which enables call-graph and call-count profiling. Because mcount() is called at entry to each function, this will slow down execution somewhat. If you do not plan to use profiling, say N here. IMPORTANT NOTICE: Do not use this option if you compile the i386 kernel with stock gcc. If you do, the kernel will crash or hang at boot time. Find a simple patch at http://oss.sgi.com/projects/kernprof/download to modify egcs-1.1.2 and rebuild gcc. Function-limit recursion CONFIG_LIMIT_RECURS On certain hardware, call-graph profiling and exit instrumentation may cause kernel crashes because of excessive recursive invocations of the instrumentation functions. Answer Y to limit the level of recursion permitted to 3. /dev/nvram support CONFIG_NVRAM If you say Y here and create a character special file /dev/nvram with major number 10 and minor number 144 using mknod ("man mknod"), you get read and write access to the extra bytes of non-volatile memory in the real time clock (RTC), which is contained in every PC and most Ataris. The actual number of bytes varies, depending on the nvram in the system, but is usually 114 (128-14 for the RTC). This memory is conventionally called "CMOS RAM" on PCs and "NVRAM" on Ataris. /dev/nvram may be used to view settings there, or to change them (with some utility). It could also be used to frequently save a few bits of very important data that may not be lost over power-off and for which writing to disk is too insecure. Note however that most NVRAM space in a PC belongs to the BIOS and you should NEVER idly tamper with it. See Ralf Brown's interrupt list for a guide to the use of CMOS bytes by your BIOS. On Atari machines, /dev/nvram is always configured and does not need to be selected. 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 nvram.o. If you want to compile it as a module, say M here and read . Joystick support CONFIG_JOYSTICK If you have a joystick, 6dof controller, gamepad, steering wheel, weapon control system or something like that you can say Y here to enable generic support for these controllers. You will also need to say Y or M to at least one of the hardware specific drivers. This will make the controllers available as /dev/input/jsX devices. Please read the file which contains more information and the location of the joystick package that you'll need. Game port support CONFIG_INPUT_GAMEPORT Gameport support is for the standard 15-pin PC gameport. If you have a joystick, gamepad, gameport card, a soundcard with a gameport or anything else that uses the gameport, say Y or M here and also to at least one of the hardware specific drivers. Please read the file which contains more information and the location of the joystick package that you'll need if you use the gameport with a joystick. 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 gameport.o. If you want to compile it as a module, say M here and read . Classic ISA/PnP gameports CONFIG_INPUT_NS558 Say Y here if you have an ISA or PnP gameport. For more information on how to use the driver please read . 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 ns558.o. If you want to compile it as a module, say M here and read . PDPI Lightning 4 gamecard CONFIG_INPUT_LIGHTNING Say Y here if you have a PDPI Lightning 4 gamecard. For more information on how to use the driver please read . 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 lightning.o. If you want to compile it as a module, say M here and read . Crystal SoundFusion gameports CONFIG_INPUT_CS461X Say Y here if you have a Cirrus CS461x aka "Crystal SoundFusion" PCI audio accelerator. A product page for the CS4614 is at . 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 cs461x.o. If you want to compile it as a module, say M here and read . Aureal Vortex and Trident 4DWave gameports CONFIG_INPUT_PCIGAME Say Y here if you have a Trident 4DWave DX/NX or Aureal Vortex 1/2 card. For more information on how to use the driver please read . 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 pcigame.o. If you want to compile it as a module, say M here and read . SoundBlaster Live! gameports CONFIG_INPUT_EMU10K1 Say Y here if you have a SoundBlaster Live! card and want to use its gameport. For more information on how to use the driver please read . 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 emu10k1-gp.o. If you want to compile it as a module, say M here and read . Classic PC analog joysticks and gamepads CONFIG_INPUT_ANALOG Say Y here if you have a controller that connects to the PC gameport. This supports many different types, including joysticks with throttle control, with rudders, or with extensions like additional hats and buttons compatible with CH Flightstick Pro, ThrustMaster FCS, 6 and 8 button gamepads, or Saitek Cyborg joysticks. For more information on how to use the driver please read . 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 analog.o. If you want to compile it as a module, say M here and read . Assassin 3D and MadCatz Panther devices CONFIG_INPUT_A3D Say Y here if you have an FPGaming or MadCatz controller using the A3D protocol over the PC gameport. For more information on how to use the driver please read . 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 a3d.o. If you want to compile it as a module, say M here and read . Logitech ADI digital joysticks and gamepads CONFIG_INPUT_ADI Say Y here if you have a Logitech controller using the ADI protocol over the PC gameport. For more information on how to use the driver please read . 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 adi.o. If you want to compile it as a module, say M here and read . Creative Labs Blaster Cobra gamepad CONFIG_INPUT_COBRA Say Y here if you have a Creative Labs Blaster Cobra gamepad. For more information on how to use the driver please read . 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 cobra.o. If you want to compile it as a module, say M here and read . Genius Flight2000 Digital joysticks and gamepads CONFIG_INPUT_GF2K Say Y here if you have a Genius Flight2000 or MaxFighter digitally communicating joystick or gamepad. For more information on how to use the driver please read . 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 gf2k.o. If you want to compile it as a module, say M here and read . Gravis GrIP joysticks and gamepads CONFIG_INPUT_GRIP Say Y here if you have a Gravis controller using the GrIP protocol over the PC gameport. For more information on how to use the driver please read . 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 grip.o. If you want to compile it as a module, say M here and read . InterAct digital joysticks and gamepads CONFIG_INPUT_INTERACT Say Y hereif you have an InterAct gameport or joystick communicating digitally over the gameport. For more information on how to use the driver please read . 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 interact.o. If you want to compile it as a module, say M here and read . ThrustMaster DirectConnect joysticks and gamepads CONFIG_INPUT_TMDC Say Y here if you have a ThrustMaster controller using the DirectConnect (BSP) protocol over the PC gameport. For more information on how to use the driver please read . 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 tmdc.o. If you want to compile it as a module, say M here and read . Microsoft SideWinder digital joysticks and gamepads CONFIG_INPUT_SIDEWINDER Say Y here if you have a Microsoft controller using the Digital Overdrive protocol over PC gameport. For more information on how to use the driver please read . 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 sidewinder.o. If you want to compile it as a module, say M here and read . Serial port device support CONFIG_INPUT_SERIO Say Y here and to the Serial port input line discipline option if you plan to use a joystick that communicates over the serial (COM) port. For more information on how to use the driver please read . 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 sidewinder.o. If you want to compile it as a module, say M here and read . Serial port input line discipline CONFIG_INPUT_SERPORT Say Y here if you plan to use a joystick that communicates over the serial (COM) port. For more information on how to use the driver please read . 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 serport.o. If you want to compile it as a module, say M here and read . Logitech WingMan Warrior joystick CONFIG_INPUT_WARRIOR Say Y here if you have a Logitech WingMan Warrior joystick connected to your computer's serial port. For more information on how to use the driver please read . 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 warrior.o. If you want to compile it as a module, say M here and read . LogiCad3d Magellan/SpaceMouse 6dof controller CONFIG_INPUT_MAGELLAN Say Y here if you have a Magellan or Space Mouse 6DOF controller connected to your computer's serial port. For more information on how to use the driver please read . 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 magellan.o. If you want to compile it as a module, say M here and read . SpaceTec SpaceOrb/Avenger 6dof controller CONFIG_INPUT_SPACEORB Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF controller connected to your computer's serial port. For more information on how to use the driver please read . 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 spaceorb.o. If you want to compile it as a module, say M here and read . SpaceTec SpaceBall 4000 FLX 6dof controller CONFIG_INPUT_SPACEBALL Say Y here if you have a SpaceTec SpaceBall 4000 FLX controller connected to your computer's serial port. For more information on how to use the driver please read . 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 spaceball.o. If you want to compile it as a module, say M here and read . Gravis Stinger gamepad CONFIG_INPUT_STINGER Say Y here if you have a Gravis Stinger connected to one of your serial ports. For more information on how to use the driver please read . 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 stinger.o. If you want to compile it as a module, say M here and read . I-Force joysticks/wheels CONFIG_INPUT_IFORCE_232 Say Y here if you have an I-Force joystick or steering wheel connected to your serial (COM) port. For more information on how to use the driver please read . 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 iforce.o. If you want to compile it as a module, say M here and read . I-Force joysticks/wheels CONFIG_INPUT_IFORCE_USB Say Y here if you have an I-Force joystick or steering wheel connected to your USB port. For more information on how to use the driver please read . 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 iforce.o. If you want to compile it as a module, say M here and read . Multisystem, Sega Genesis, Saturn joysticks and gamepads CONFIG_INPUT_DB9 Say Y here if you have a Sega Master System gamepad, Sega Genesis gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga, Commodore, Amstrad CPC joystick connected to your parallel port. For more information on how to use the driver please read and . 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 db9.o. If you want to compile it as a module, say M here and read . Multisystem, NES, SNES, N64, PSX joysticks and gamepads CONFIG_INPUT_GAMECON Say Y here if you have a Nintendo Entertainment System gamepad, Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad, Sony PlayStation gamepad or a Multisystem -- Atari, Amiga, Commodore, Amstrad CPC joystick connected to your parallel port. For more information on how to use the driver please read and . 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 gamecon.o. If you want to compile it as a module, say M here and read . Multisystem joysticks via TurboGraFX device CONFIG_INPUT_TURBOGRAFX Say Y here if you have the TurboGraFX interface by Steffen Schwenke, and want to use it with Multisystem -- Atari, Amiga, Commodore, Amstrad CPC joystick. For more information on how to use the driver please read and . 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 turbografx.o. If you want to compile it as a module, say M here and read . Amiga joysticks CONFIG_INPUT_AMIJOY Say Y here if you have an Amiga with a digital joystick connected to it. For more information on how to use the driver please read . 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 joy-amiga.o. If you want to compile it as a module, say M here and read . Atomwide serial port support CONFIG_ATOMWIDE_SERIAL If you have an Atomwide Serial card for an Acorn system, say Y to this option. The driver can handle 1, 2, or 3 port cards. If unsure, say N. Dual serial port support CONFIG_DUALSP_SERIAL If you have the Serial Port's dual serial card for an Acorn system, say Y to this option. If unsure, say N. NetWinder Button CONFIG_NWBUTTON If you say Y here and create a character device node /dev/nwbutton with major and minor numbers 10 and 158 ("man mknod"), then every time the orange button is pressed a number of times, the number of times the button was pressed will be written to that device. This is most useful for applications, as yet unwritten, which perform actions based on how many times the button is pressed in a row. Do not hold the button down for too long, as the driver does not alter the behaviour of the hardware reset circuitry attached to the button; it will still execute a hard reset if the button is held down for longer than approximately five seconds. 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 . The module will be called nwbutton.o. Most people will answer Y to this question and "Reboot Using Button" below to be able to initiate a system shutdown from the button. Reboot Using Button CONFIG_NWBUTTON_REBOOT If you say Y here, then you will be able to initiate a system shutdown and reboot by pressing the orange button a number of times. The number of presses to initiate the shutdown is two by default, but this can be altered by modifying the value of NUM_PRESSES_REBOOT in nwbutton.h and recompiling the driver or, if you compile the driver as a module, you can specify the number of presses at load time with "insmod button reboot_count=". Sound card support CONFIG_SOUND If you have a sound card in your computer, i.e. if it can say more than an occasional beep, say Y. Be sure to have all the information about your sound card and its configuration down (I/O port, interrupt and DMA channel), because you will be asked for it. You want to read the Sound-HOWTO, available from . General information about the modular sound system is contained in the files . The file contains some slightly outdated but still useful information as well. If you have a PnP sound card and you want to configure it at boot time using the ISA PnP tools (read ), then you need to compile the sound card support as a module ( = code which can be inserted in and removed from the running kernel whenever you want) and load that module after the PnP configuration is finished. To do this, say M here and read as well as ; the module will be called soundcore.o. I'm told that even without a sound card, you can make your computer say more than an occasional beep, by programming the PC speaker. Kernel patches and supporting utilities to do that are in the pcsp package, available at . OSS sound modules CONFIG_SOUND_OSS OSS is the Open Sound System suite of sound card drivers. They make sound programming easier since they provide a common API. Say Y or M here (the module will be called sound.o) if you haven't found a driver for your sound card above, then pick your driver from the list below. Persistent DMA buffers CONFIG_SOUND_DMAP Linux can often have problems allocating DMA buffers for ISA sound cards on machines with more than 16MB of RAM. This is because ISA DMA buffers must exist below the 16MB boundary and it is quite possible that a large enough free block in this region cannot be found after the machine has been running for a while. If you say Y here the DMA buffers (64Kb) will be allocated at boot time and kept until the shutdown. This option is only useful if you said Y to "OSS sound modules", above. If you said M to "OSS sound modules" then you can get the persistent DMA buffer functionality by passing the command-line argument "dmabuf=1" to the sound.o module. Say Y unless you have 16MB or less RAM or a PCI sound card. Support for Aztech Sound Galaxy (non-PnP) cards CONFIG_SOUND_SGALAXY This module initializes the older non Plug and Play sound galaxy cards from Aztech. It supports the Waverider Pro 32 - 3D and the Galaxy Washington 16. If you compile the driver into the kernel, you have to add "sgalaxy=,,,," to the kernel command line. Support for AD1816(A) based cards CONFIG_SOUND_AD1816 Say M here if you have a sound card based on the Analog Devices AD1816(A) chip. If you compile the driver into the kernel, you have to add "ad1816=,,," to the kernel command line. Yamaha OPL3-SA1 audio controller CONFIG_SOUND_OPL3SA1 Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is usually built into motherboards. Read for details. If you compile the driver into the kernel, you have to add "opl3sa=,,,,," to the kernel command line. ProAudioSpectrum 16 support CONFIG_SOUND_PAS Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio 16 or Logitech SoundMan 16 sound card. Answer N if you have some other card made by Media Vision or Logitech since those are not PAS16 compatible. Please read . It is not necessary to add Sound Blaster support separately; it is included in PAS support. If you compile the driver into the kernel, you have to add "pas2=,,,,,,, to the kernel command line. Enable PAS16 joystick port CONFIG_PAS_JOYSTICK Say Y here to enable the Pro Audio Spectrum 16's auxiliary joystick port. 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support CONFIG_SOUND_SB Answer Y if you have an original Sound Blaster card made by Creative Labs or a 100% hardware compatible clone (like the Thunderboard or SM Games). For an unknown card you may answer Y if the card claims to be Sound Blaster-compatible. Please read the file . You should also say Y here for cards based on the Avance Logic ALS-007 and ALS-1X0 chips (read ) and for cards based on ESS chips (read and ). If you have an SB AWE 32 or SB AWE 64, say Y here and also to "AWE32 synth" below and read . If you have an IBM Mwave card, say Y here and read . If you compile the driver into the kernel and don't want to use isapnp, you have to add "sb=,,," to the kernel command line. You can say M here to compile this driver as a module; the module is called sb.o. Gravis Ultrasound support CONFIG_SOUND_GUS Say Y here for any type of Gravis Ultrasound card, including the GUS or GUS MAX. See also for more information on configuring this card with modules. If you compile the driver into the kernel, you have to add "gus=,,," to the kernel command line. MPU-401 support (NOT for SB16) CONFIG_SOUND_MPU401 Be careful with this question. The MPU401 interface is supported by all sound cards. However, some natively supported cards have their own driver for MPU401. Enabling this MPU401 option with these cards will cause a conflict. Also, enabling MPU401 on a system that doesn't really have a MPU401 could cause some trouble. If your card was in the list of supported cards, look at the card specific instructions in the file. It is safe to answer Y if you have a true MPU401 MIDI interface card. If you compile the driver into the kernel, you have to add "mpu401=," to the kernel command line. 6850 UART support CONFIG_SOUND_UART6850 This option enables support for MIDI interfaces based on the 6850 UART chip. This interface is rarely found on sound cards. It's safe to answer N to this question. If you compile the driver into the kernel, you have to add "uart6850=," to the kernel command line. PSS (AD1848, ADSP-2115, ESC614) support CONFIG_SOUND_PSS Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven ADSP-16 or some other card based on the PSS chipset (AD1848 codec + ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on how to compile it into the kernel or as a module see the file . If you compile the driver into the kernel, you have to add "pss=,,,,," to the kernel command line. Enable PSS mixer (Beethoven ADSP-16 and other compatible) CONFIG_PSS_MIXER Answer Y for Beethoven ADSP-16. You may try to say Y also for other cards if they have master volume, bass, treble, and you can't control it under Linux. If you answer N for Beethoven ADSP-16, you can't control master volume, bass, treble and synth volume. If you said M to "PSS support" above, you may enable or disable this PSS mixer with the module parameter pss_mixer. For more information see the file . Have DSPxxx.LD firmware file CONFIG_PSS_HAVE_BOOT If you have the DSPxxx.LD file or SYNTH.LD file for you card, say Y to include this file. Without this file the synth device (OPL) may not work. Full pathname of DSPxxx.LD firmware file CONFIG_PSS_BOOT_FILE Enter the full pathname of your DSPxxx.LD file or SYNTH.LD file, starting from /. Microsoft Sound System support CONFIG_SOUND_MSS Again think carefully before answering Y to this question. It's safe to answer Y if you have the original Windows Sound System card made by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may say Y in case your card is NOT among these: ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16, Ensoniq SoundScape (and compatibles made by Reveal and Spea), Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max, Gravis Ultrasound with 16 bit option, Logitech Sound Man 16, Logitech SoundMan Games, Logitech SoundMan Wave, MAD16 Pro (OPTi 82C929), Media Vision Jazz16, MediaTriX AudioTriX Pro, Microsoft Windows Sound System (MSS/WSS), Mozart (OAK OTI-601), Orchid SW32, Personal Sound System (PSS), Pro Audio Spectrum 16, Pro Audio Studio 16, Pro Sonic 16, Roland MPU-401 MIDI interface, Sound Blaster 1.0, Sound Blaster 16, Sound Blaster 16ASP, Sound Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface. For cards having native support in VoxWare, consult the card specific instructions in . Some drivers have their own MSS support and saying Y to this option will cause a conflict. If you compile the driver into the kernel, you have to add "ad1848=,,,[,]" to the kernel command line. SGI Visual Workstation on-board audio CONFIG_SOUND_VWSND Say Y or M if you have an SGI Visual Workstation and you want to be able to use its on-board audio. Read for more info on this driver's capabilities. NEC Vrc5477 AC97 sound CONFIG_SOUND_VRC5477 Say Y here to enable sound support for the NEC Vrc5477 chip, an integrated, multi-function controller chip for MIPS CPUs. Works with the AC97 codec. Ensoniq SoundScape support CONFIG_SOUND_SSCAPE Answer Y if you have a sound card based on the Ensoniq SoundScape chipset. Such cards are being manufactured at least by Ensoniq, Spea and Reveal (Reveal makes also other cards). If you compile the driver into the kernel, you have to add "sscape=,,,," to the kernel command line. MediaTriX AudioTriX Pro support CONFIG_SOUND_TRIX Answer Y if you have the AudioTriX Pro sound card manufactured by MediaTrix. Have TRXPRO.HEX firmware file CONFIG_TRIX_HAVE_BOOT The MediaTrix AudioTrix Pro has an on-board microcontroller which needs to be initialized by downloading the code from the file TRXPRO.HEX in the DOS driver directory. If you don't have the TRXPRO.HEX file handy you may skip this step. However, the SB and MPU-401 modes of AudioTrix Pro will not work without this file! Full pathname of TRXPRO.HEX firmware file CONFIG_TRIX_BOOT_FILE Enter the full pathname of your TRXPRO.HEX file, starting from /. Support for OPTi MAD16 and/or Mozart based cards CONFIG_SOUND_MAD16 Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi 82C928 or 82C929 or 82C931) audio interface chip. These chips are quite common so it's possible that many no-name cards have one of them. In addition the MAD16 chip is used in some cards made by known manufacturers such as Turtle Beach (Tropez), Reveal (some models) and Diamond (latest ones). Note however that the Tropez sound cards have their own driver; if you have one of those, say N here and Y or M to "Full support for Turtle Beach WaveFront", below. If you compile the driver into the kernel, you have to add "mad16=,,,,," to the kernel command line. See also and for more information on setting these cards up as modules. Full support for Turtle Beach WaveFront (Tropez Plus, Tropez, Maui) synth/sound cards CONFIG_SOUND_WAVEFRONT Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card and read the files and . Support MIDI in older MAD16 based cards (requires SB) CONFIG_MAD16_OLDCARD Answer Y (or M) if you have an older card based on the C928 or Mozart chipset and you want to have MIDI support. If you enable this option you also need to enable support for Sound Blaster. Support for Crystal CS4232 based (PnP) cards CONFIG_SOUND_CS4232 Say Y here if you have a card based on the Crystal CS4232 chip set, which uses its own Plug and Play protocol. If you compile the driver into the kernel, you have to add "cs4232=,,,,," to the kernel command line. See for more information on configuring this card. Support for Yamaha OPL3-SA2 and SA3 based PnP cards CONFIG_SOUND_OPL3SA2 Say Y or M if you have a card based on one of these Yamaha sound chipsets or the "SAx", which is actually a SA3. Read for more information on configuring these cards. If you compile the driver into the kernel and do not also configure in the optional ISA PnP support, you will have to add "opl3sa2=,,,,," to the kernel command line. Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers CONFIG_SOUND_MAUI Say Y here if you have a Turtle Beach Wave Front, Maui, or Tropez sound card. If you compile the driver into the kernel, you have to add "maui=," to the kernel command line. Have OSWF.MOT firmware file CONFIG_MAUI_HAVE_BOOT Turtle Beach Maui and Tropez sound cards have a microcontroller which needs to be initialized prior to use. OSWF.MOT is a file distributed with the card's DOS/Windows drivers. Answer Y if you have this file. Full pathname of OSWF.MOT firmware file CONFIG_MAUI_BOOT_FILE Enter the full pathname of your OSWF.MOT file, starting from /. Support for Turtle Beach MultiSound Classic, Tahiti, Monterey CONFIG_SOUND_MSNDCLAS Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or Monterey (not for the Pinnacle or Fiji). See for important information about this driver. Note that it has been discontinued, but the Voyetra Turtle Beach knowledge base entry for it is still available at . MSND Classic I/O CONFIG_MSNDCLAS_IO I/O port address for the MultiSound Classic and related cards. MSND Classic IRQ CONFIG_MSNDCLAS_IRQ Interrupt Request line for the MultiSound Classic and related cards. MSND Classic memory address CONFIG_MSNDCLAS_MEM Memory-mapped I/O base address for the MultiSound Classic and related cards. Full pathname of MSNDINIT.BIN firmware file CONFIG_MSNDCLAS_INIT_FILE The MultiSound cards have two firmware files which are required for operation, and are not currently included. These files can be obtained from Turtle Beach. See for information on how to obtain this. Full pathname of MSNDPERM.BIN firmware file CONFIG_MSNDCLAS_PERM_FILE The MultiSound cards have two firmware files which are required for operation, and are not currently included. These files can be obtained from Turtle Beach. See for information on how to obtain this. Support for Turtle Beach MultiSound Pinnacle, Fiji CONFIG_SOUND_MSNDPIN Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji. See for important information about this driver. Note that it has been discontinued, but the Voyetra Turtle Beach knowledge base entry for it is still available at . MSND Pinnacle IDE I/O 0 CONFIG_MSNDPIN_IDE_IO0 CD-ROM drive 0 memory-mapped I/O base address for the MultiSound Pinnacle and Fiji sound cards. MSND Pinnacle IDE I/O 1 CONFIG_MSNDPIN_IDE_IO1 CD-ROM drive 1 memory-mapped I/O base address for the MultiSound Pinnacle and Fiji sound cards. MSND Pinnacle IDE IRQ CONFIG_MSNDPIN_IDE_IRQ Interrupt request number for the IDE CD-ROM interface on the MultiSound Pinnacle and Fiji sound cards. MSND Pinnacle I/O CONFIG_MSNDPIN_IO Memory-mapped I/O base address for the primary synthesizer on MultiSound Pinnacle and Fiji sound cards. MSND Pinnacle MPU I/O CONFIG_MSNDPIN_MPU_IO Memory-mapped I/O base address for the Kurzweil daughterboard synthesizer on MultiSound Pinnacle and Fiji sound cards. MSND Pinnacle MPU IRQ CONFIG_MSNDPIN_MPU_IRQ Iinterrupt request number for the Kurzweil daughterboard synthesizer on MultiSound Pinnacle and Fiji sound cards. MSND Pinnacle IRQ CONFIG_MSNDPIN_IRQ Interrupt request line for the primary synthesizer on MultiSound Pinnacle and Fiji sound cards. MSND Pinnacle joystick I/O CONFIG_MSNDPIN_JOYSTICK_IO Memory-mapped I/O base address for the joystick port on MultiSound Pinnacle and Fiji sound cards. MSND Pinnacle memory CONFIG_MSNDPIN_MEM Memory-mapped I/O base address for the primary synthesizer on MultiSound Pinnacle and Fiji sound cards. Full pathname of PNDSPINI.BIN firmware file CONFIG_MSNDPIN_INIT_FILE The MultiSound cards have two firmware files which are required for operation, and are not currently included. These files can be obtained from Turtle Beach. See for information on how to obtain this. Full pathname of PNDSPERM.BIN firmware file CONFIG_MSNDPIN_PERM_FILE The MultiSound cards have two firmware files which are required for operation, and are not currently included. These files can be obtained from Turtle Beach. See for information on how to obtain this. MSND Pinnacle has S/PDIF I/O CONFIG_MSNDPIN_DIGITAL If you have the S/PDIF daughter board for the Pinnacle or Fiji, answer Y here; otherwise, say N. If you have this, you will be able to play and record from the S/PDIF port (digital signal). See for information on how to make use of this capability. MSND Pinnacle non-PnP Mode CONFIG_MSNDPIN_NONPNP The Pinnacle and Fiji card resources can be configured either with PnP, or through a configuration port. Say Y here if your card is NOT in PnP mode. For the Pinnacle, configuration in non-PnP mode allows use of the IDE and joystick peripherals on the card as well; these do not show up when the card is in PnP mode. Specifying zero for any resource of a device will disable the device. If you are running the card in PnP mode, you must say N here and use isapnptools to configure the card's resources. MSND Pinnacle config port CONFIG_MSNDPIN_CFG This is the port which the Pinnacle and Fiji uses to configure the card's resources when not in PnP mode. If your card is in PnP mode, then be sure to say N to the previous option, "MSND Pinnacle Non-PnP Mode". MSND buffer size (kB) CONFIG_MSND_FIFOSIZE Configures the size of each audio buffer, in kilobytes, for recording and playing in the MultiSound drivers (both the Classic and Pinnacle). Larger values reduce the chance of data overruns at the expense of overall latency. If unsure, use the default. Yamaha FM synthesizer (YM3812/OPL-3) support CONFIG_SOUND_YM3812 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4). Answering Y is usually a safe and recommended choice, however some cards may have software (TSR) FM emulation. Enabling FM support with these cards may cause trouble (I don't currently know of any such cards, however). Please read the file if your card has an OPL3 chip. If you compile the driver into the kernel, you have to add "opl3=" to the kernel command line. If unsure, say Y. ACI mixer (miroSOUND PCM1-pro/PCM12/PCM20 radio) CONFIG_SOUND_ACI_MIXER ACI (Audio Command Interface) is a protocol used to communicate with the microcontroller on some sound cards produced by miro and Cardinal Technologies. The main function of the ACI is to control the mixer and to get a product identification. This VoxWare ACI driver currently supports the ACI functions on the miroSOUND PCM1-pro, PCM12 and PCM20 radio. On the PCM20 radio, ACI also controls the radio tuner. This is supported in the video4linux miropcm20 driver (say M or Y here and go back to "Multimedia devices" -> "Radio Adapters"). This driver is also available as a module and will be called aci.o. SB32/AWE support CONFIG_SOUND_AWE32_SYNTH Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or similar sound card. See , and the Soundblaster-AWE mini-HOWTO, available from for more info. Gallant Audio Cards (SC-6000 and SC-6600 based) CONFIG_SOUND_AEDSP16 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This driver supports Audio Excel DSP 16 but not the III nor PnP versions of this card. The Gallant's Audio Excel DSP 16 card can emulate either an SBPro or a Microsoft Sound System card, so you should have said Y to either "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support" or "Microsoft Sound System support", above, and you need to answer the "MSS emulation" and "SBPro emulation" questions below accordingly. You should say Y to one and only one of these two questions. Read the file and the head of as well as to get more information about this driver and its configuration. Audio Excel DSP 16 (SBPro emulation) CONFIG_AEDSP16_SBPRO Answer Y if you want your audio card to emulate Sound Blaster Pro. You should then say Y to "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support" and N to "Audio Excel DSP 16 (MSS emulation)". If you compile the driver into the kernel, you have to add "aedsp16=,,,,," to the kernel command line. Audio Excel DSP 16 (MSS emulation) CONFIG_AEDSP16_MSS Answer Y if you want your audio card to emulate Microsoft Sound System. You should then say Y to "Microsoft Sound System support" and say N to "Audio Excel DSP 16 (SBPro emulation)". SC-6600 based audio cards (new Audio Excel DSP 16) CONFIG_SC6600 The SC6600 is the new version of DSP mounted on the Audio Excel DSP 16 cards. Find in the manual the FCC ID of your audio card and answer Y if you have an SC6600 DSP. SC-6600 Joystick Interface CONFIG_SC6600_JOY Say Y here in order to use the joystick interface of the Audio Excel DSP 16 card. SC-6600 CD-ROM Interface CONFIG_SC6600_CDROM (4=None, 3=IDE, 1=Panasonic, 0=Sony) This is used to activate the CD-ROM interface of the Audio Excel DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no CD-ROM present. SC-6600 CD-ROM Interface I/O Address CONFIG_SC6600_CDROMBASE Base I/O port address for the CD-ROM interface of the Audio Excel DSP 16 card. Audio Excel DSP 16 (MPU401 emulation) CONFIG_AEDSP16_MPU401 Answer Y if you want your audio card to emulate the MPU-401 midi interface. You should then also say Y to "MPU-401 support". Note that the I/O base for MPU-401 support of aedsp16 is the same you have selected for "MPU-401 support". If you are using this driver as a module you have to specify the MPU I/O base address with the parameter 'mpu_base=0xNNN'. SC-6600 CDROM Interface (4=None, 3=IDE, 1=Panasonic, 0=?Sony?) CONFIG_SC6600_CDROM This is used to activate the CD-ROM interface of the Audio Excel DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no CD-ROM present. C-Media PCI (CMI8338/8378) CONFIG_SOUND_CMPCI Say Y or M if you have a PCI sound card using the CMI8338 or the CMI8378 chipset. Data on these chips are available at . A userspace utility to control some internal registers of these chips is available at . Support CMI8738 based audio cards CONFIG_SOUND_CMPCI_CM8738 Say Y or M if you have a PCI sound card using the CMI8338 or the CMI8378 chipset. Data on this chip is available at . A userspace utility to control some internal registers of these chips is available at . Enable joystick CONFIG_SOUND_CMPCI_JOYSTICK Say here in order to enable the joystick port on a sound crd using the CMI8338 or the CMI8738 chipset. Data on these chips are available at . Number of speakers (2, 4, 5, 6) CONFIG_SOUND_CMPCI_SPEAKERS Specify the number of speaker channels you want the card to drive, as an integer. Enable S/PDIF loop for CMI8738 CONFIG_SOUND_CMPCI_SPDIFLOOP Enable loopback from SPDIF in to SPDIF out. For discussion, see "The 8738 Audio SPDIF In/Out Technical Data" on the technical support page at . A userspace utility to control even more internal registers of these chips is available at . This package will among other things help you enable SPDIF out/in/loop/monitor. Enable legacy FM CONFIG_SOUND_CMPCI_FM Say Y here to enable the legacy FM (frequency-modulation) synthesis support on a card using the CMI8338 or CMI8378 chipset. FM I/O 388, 3C8, 3E0, 3E8 CONFIG_SOUND_CMPCI_FMIO Set the base I/O address for FM synthesis control on a card using the CMI8338 or CMI8378 chipset. Enable legacy MPU-401 CONFIG_SOUND_CMPCI_MIDI Say Y here to enable the legacy MP401 MIDI synthesis support on a card using the CMI8338 or CMI8378 chipset. MPU-401 I/O 330, 320, 310, 300 CONFIG_SOUND_CMPCI_MPUIO Set the base I/O address for MP401 MIDI synthesis control on a card using the CMI8338 or CMI8378 chipset. Inverse S/PDIF in for CMI8738 CONFIG_SOUND_CMPCI_SPDIFINVERSE Say Y here to have the driver invert the signal presented on SPDIF IN of a card using the CMI8338 or CMI8378 chipset. Use Line-in as Read-out CONFIG_SOUND_CMPCI_LINE_REAR Say Y here to enable using line-in jack as an output jack for a rear speaker. Use Line-in as Bass CONFIG_SOUND_CMPCI_LINE_BASS Say Y here to enable using line-in jack as an output jack for a bass speaker. Creative SBLive! (EMU10K1) based PCI sound cards CONFIG_SOUND_EMU10K1 Say Y or M if you have a PCI sound card using the EMU10K1 chipset, such as the Creative SBLive!, SB PCI512 or Emu-APS. For more information on this driver and the degree of support for the different card models please check: It is now possible to load dsp microcode patches into the EMU10K1 chip. These patches are used to implement real time sound processing effects which include for example: signal routing, bass/treble control, AC3 passthrough, ... Userspace tools to create new patches and load/unload them can be found in the emu-tools package at the above URL. Creative SBLive! (EMU10K1) MIDI CONFIG_MIDI_EMU10K1 Say Y if you want to be able to use the OSS /dev/sequencer interface. This code is still experimental. Crystal SoundFusion (CS4280/461x) CONFIG_SOUND_FUSION This module drives the Crystal SoundFusion devices (CS4280/46xx series) when wired as native sound drivers with AC97 codecs. If this driver does not work try the CS4232 driver. Ensoniq AudioPCI (ES1370) based PCI sound cards CONFIG_SOUND_ES1370 Say Y or M if you have a PCI sound card utilizing the Ensoniq ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find out if your sound card uses an ES1370 without removing your computer's cover, use lspci -n and look for the PCI ID 1274:5000. Since Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI models are either ES1370 or ES1371 based. This driver differs slightly from OSS/Free, so PLEASE READ . Ensoniq AudioPCI 97 (ES1371) based sound cards CONFIG_SOUND_ES1371 Say Y or M if you have a PCI sound card utilizing the Ensoniq ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if your sound card uses an ES1371 without removing your computer's cover, use lspci -n and look for the PCI ID 1274:1371. Since Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI models are either ES1370 or ES1371 based. This driver differs slightly from OSS/Free, so PLEASE READ . ESS Solo1 based PCI sound cards (eg. SC1938) CONFIG_SOUND_ESSSOLO1 Say Y or M if you have a PCI sound card utilizing the ESS Technology Solo1 chip. To find out if your sound card uses a Solo1 chip without removing your computer's cover, use lspci -n and look for the PCI ID 125D:1969. This driver differs slightly from OSS/Free, so PLEASE READ . S3 SonicVibes based PCI sound cards CONFIG_SOUND_SONICVIBES Say Y or M if you have a PCI sound card utilizing the S3 SonicVibes chipset. To find out if your sound card uses a SonicVibes chip without removing your computer's cover, use lspci -n and look for the PCI ID 5333:CA00. This driver differs slightly from OSS/Free, so PLEASE READ . Trident 4DWave DX/NX, SiS 7018 or ALi 5451 PCI Audio Core CONFIG_SOUND_TRIDENT Say Y or M if you have a PCI sound card utilizing the Trident 4DWave-DX/NX chipset or your mother board chipset has SiS 7018 or ALi 5451 built-in. The SiS 7018 PCI Audio Core is embedded in SiS960 Super South Bridge and SiS540/630 Single Chipset. The ALi 5451 PCI Audio Core is embedded in ALi M1535, M1535D, M1535+ or M1535D+ South Bridge. Use lspci -n to find out if your sound card or chipset uses Trident 4DWave or SiS 7018. PCI ID 1023:2000 or 1023:2001 stands for Trident 4Dwave. PCI ID 1039:7018 stands for SiS7018. PCI ID 10B9:5451 stands for ALi5451. This driver supports S/PDIF in/out (record/playback) for ALi 5451 embedded in ALi M1535+ and M1535D+. Note that they aren't all enabled by default; you can enable them by saying Y to "/proc file system support" and "Sysctl support", and after the /proc file system has been mounted, executing the command command what is enabled echo 0>/proc/ALi5451 pcm out is also set to S/PDIF out. (Default). echo 1>/proc/ALi5451 use S/PDIF out to output pcm data. echo 2>/proc/ALi5451 use S/PDIF out to output non-pcm data. (AC3...). echo 3>/proc/ALi5451 record from Ac97 in(MIC, Line in...). (Default). echo 4>/proc/ALi5451 no matter Ac97 settings, record from S/PDIF in. This driver differs slightly from OSS/Free, so PLEASE READ the comments at the top of . Rockwell WaveArtist CONFIG_SOUND_WAVEARTIST Say Y here to include support for the Rockwell WaveArtist sound system. This driver is mainly for the NetWinder. VIA 82Cxxx Audio Codec CONFIG_SOUND_VIA82CXXX Say Y here to include support for the audio codec found on VIA 82Cxxx-based chips. Typically these are built into a motherboard. DO NOT select Sound Blaster or Adlib with this driver, unless you have a Sound Blaster or Adlib card in addition to your VIA audio chip. VIA 82C686 MIDI CONFIG_MIDI_VIA82CXXX Answer Y to use the MIDI interface of the Via686. You may need to enable this in the BIOS before it will work. This is for connection to external MIDI hardware, and is not required for software playback of MIDI files. NeoMagic 256AV/256ZX sound chipsets CONFIG_SOUND_NM256 Say M here to include audio support for the NeoMagic 256AV/256ZX chipsets. These are the audio chipsets found in the Sony Z505S/SX/DX, some Sony F-series, and the Dell Latitude CPi and CPt laptops. It includes support for an AC97-compatible mixer and an apparently proprietary sound engine. See for further information. ESS Maestro, Maestro2, Maestro2E driver CONFIG_SOUND_MAESTRO Say Y or M if you have a sound system driven by ESS's Maestro line of PCI sound chips. These include the Maestro 1, Maestro 2, and Maestro 2E. See for more details. ESS Maestro3/Allegro driver CONFIG_SOUND_MAESTRO3 Say Y or M if you have a sound system driven by ESS's Maestro 3 PCI sound chip. ForteMedia FM801 driver CONFIG_SOUND_FORTE Say Y or M if you want driver support for the ForteMedia FM801 PCI audio controller (Abit AU10, Genius Sound Maker, HP Workstation zx2000, and others). Adlib Cards CONFIG_SOUND_ADLIB Includes ASB 64 4D. Information on programming AdLib cards is available at . Crystal Sound CS4281 CONFIG_SOUND_CS4281 Picture and feature list at . 16 bit sampling option of GUS (_NOT_ GUS MAX) CONFIG_SOUND_GUS16 Support for Gravis Ulstrasound (GUS) cards (other than the GUS), sampling at 16-bit width. GUS MAX support CONFIG_SOUND_GUSMAX Support for Gravis Ulstrasound MAX. Intel ICH audio support CONFIG_SOUND_ICH Supports the following chipsets: Intel ICH 82801AA Intel ICH 82901AB Intel 440 MX Intel ICH2 Intel ICH3 SiS 7012 NVidia nForce AMD 768 These are audio drivers for integral audio in chipsets of motherboards. Intel's I/O Controller Hub (ICH) is used on 810/815/820/840/845/845D/850 motherboards. SiS 7012 is used on 645/735/745 motherboards. Verbose initialization CONFIG_SOUND_TRACEINIT Verbose soundcard initialization -- affects the format of autoprobe and initialization messages at boot time. TV card (bt848) mixer support CONFIG_SOUND_TVMIXER Support for audio mixer facilities on the BT848 TV frame-grabber card. VIDC 16-bit sound CONFIG_SOUND_VIDC 16-bit support for the VIDC onboard sound hardware found on Acorn machines. Loopback MIDI device support CONFIG_SOUND_VMIDI Support for MIDI loopback on port 1 or 2. Yamaha YMF7xx PCI audio (native mode) CONFIG_SOUND_YMFPCI Support for Yamaha cards with the following chipsets: YMF724, YMF724F, YMF740, YMF740C, YMF744, and YMF754. Two common cards that use this type of chip are Waveforce 192XG, and Waveforce 192 Digital. Yamaha PCI legacy ports support CONFIG_SOUND_YMFPCI_LEGACY Support for YMF7xx PCI cards emulating an MP401. RME Hammerfall (RME96XX) support CONFIG_SOUND_RME96XX Say Y or M if you have a Hammerfall or Hammerfall light multichannel card from RME. If you want to acess advanced features of the card, read Documentation/sound/rme96xx. Are you using a crosscompiler CONFIG_CROSSCOMPILE Say Y here if you are compiling the kernel on a different architecture than the one it is intended to run on. Kernel support for Linux/MIPS 32-bit binary compatibility CONFIG_MIPS32_COMPAT Select this option if you want Linux/MIPS 32-bit binary compatibility. Since all software available for Linux/MIPS is currently 32-bit you should say Y here. Kernel support for o32 binaries CONFIG_MIPS32_O32 Select this option if you want to run o32 binaries. These are pure 32-bit binaries as used by the 32-bit Linux/MIPS port. Most of existing binaries are in this format. If unsure, say Y. Kernel support for n32 binaries CONFIG_MIPS32_N32 Select this option if you want to run n32 binaries. These are 64-bit binaries using 32-bit quantities for addressing and certain data that would normally be 64-bit. They are used in special cases. If unsure, say N. Build fp exception handler module CONFIG_MIPS_FPE_MODULE Build the floating point exception handler module. This option is only useful for people working on the floating point exception handler. If you don't, say N. Galileo EV64120 Evaluation board CONFIG_MIPS_EV64120 This is an evaluation board based on the Galileo GT-64120 single-chip system controller that contains a MIPS R5000 compatible core running at 75/100MHz. Their website is located at . Say Y here if you wish to build a kernel for this platform. Galileo EV96100 Evaluation board CONFIG_MIPS_EV96100 This is an evaluation board based on the Galielo GT-96100 LAN/WAN communications controllers containing a MIPS R5000 compatible core running at 83MHz. Their website is . Say Y here if you wish to build a kernel for this platform. Support for ITE 8172G board CONFIG_MIPS_ITE8172 Ths is an evaluation board made by ITE with ATX form factor that utilizes a MIPS R5000 to work with its ITE8172G companion internet appliance chip. The MIPS core can be either a NEC Vr5432 or QED RM5231. Say Y here if you wish to build a kernel for this platform. Support for Globespan IVR board CONFIG_MIPS_IVR This is an evaluation board built by Globespan to showcase their iVR (Internet Video Recorder) design. It utilizes a QED RM5231 R5000 MIPS core. More information can be found out their website located at P. Say Y here if you wish to build a kernel for this platform. Support for Alchemy Semi PB1000 board CONFIG_MIPS_PB1000 This is an evaluation board built by Alchemy Semiconductor to showcase their Au1000 Internet Edge Processor. It is SOC design containing a MIPS32 core running at 266/400/500MHz with many integrated peripherals. Further information can be found at their website, . Say Y here if you wish to build a kernel for this platform. Support for Philips Nino CONFIG_NINO Say Y here to select a kernel for the Philips Nino Palm PC. The website at will have more information. # Choice: nino_model CONFIG_NINO_4MB Say Y here to build a kernel specifically for Nino Palm PCs with 4MB of memory. These include models 300/301/302/319. Model-200/210/312/320/325/350/390 CONFIG_NINO_8MB Say Y here to build a kernel specifically for Nino Palm PCs with 8MB of memory. These include models 200/210/312/320/325/350/390. Model-500/510 CONFIG_NINO_16MB Say Y here to build a kernel specifically for Nino 500/501 color Palm PCs from Philips (INCOMPLETE). Model-300/301/302/319 Low-level debugging CONFIG_LL_DEBUG Enable low-level debugging assertion macros in the kernel code. Currently used only by the time services code in the MIPS port. Don't turn this on unless you know what you are doing. Remote GDB kernel debugging CONFIG_REMOTE_DEBUG If you say Y here, it will be possible to remotely debug the MIPS kernel using gdb. This enlarges your kernel image disk size by several megabytes and requires a machine with more than 16 MB, better 32 MB RAM to avoid excessive linking time. This is only useful for kernel hackers. If unsure, say N. Run uncached CONFIG_MIPS_UNCACHED If you say Y here there kernel will disable all CPU caches. This will reduce the system's performance dramatically but can help finding otherwise hard to track bugs. It can also useful if you're doing hardware debugging with a logic analyzer and need to see all traffic on the bus. AU1000 ethernet controller on SGI MIPS system CONFIG_MIPS_AU1000_ENET If you have an Alchemy Semi AU1000 ethernet controller on an SGI MIPS system, say Y. Otherwise, say N. WD93 SCSI Controller on SGI MIPS system CONFIG_SGIWD93_SCSI If you have a Western Digital WD93 SCSI controller on an SGI MIPS system, say Y. Otherwise, say N. Magic System Request Key support CONFIG_MAGIC_SYSRQ If you say Y here, you will have some control over the system even if the system crashes for example during kernel debugging (e.g., you will be able to flush the buffer cache to disk, reboot the system immediately or dump some status information). This is accomplished by pressing various keys while holding SysRq (Alt+PrintScreen). It also works on a serial console (on PC hardware at least), if you send a BREAK and then within 5 seconds a command keypress. The keys are documented in . Don't say Y unless you really know what this hack does. ISDN support CONFIG_ISDN ISDN ("Integrated Services Digital Networks", called RNIS in France) is a special type of fully digital telephone service; it's mostly used to connect to your Internet service provider (with SLIP or PPP). The main advantage is that the speed is higher than ordinary modem/telephone connections, and that you can have voice conversations while downloading stuff. It only works if your computer is equipped with an ISDN card and both you and your service provider purchased an ISDN line from the phone company. For details, read on the WWW. This driver allows you to use an ISDN-card for networking connections and as dialin/out device. The isdn-tty's have a built in AT-compatible modem emulator. Network devices support autodial, channel-bundling, callback and caller-authentication without having a daemon running. A reduced T.70 protocol is supported with tty's suitable for German BTX. On D-Channel, the protocols EDSS1 (Euro-ISDN) and 1TR6 (German style) are supported. See for more information. If you want to compile the ISDN code as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called isdn.o. If unsure, say N. Support synchronous PPP CONFIG_ISDN_PPP Over digital connections such as ISDN, there is no need to synchronize sender and recipient's clocks with start and stop bits as is done over analog telephone lines. Instead, one can use "synchronous PPP". Saying Y here will include this protocol. This protocol is used by Cisco and Sun for example. So you want to say Y here if the other end of your ISDN connection supports it. You will need a special version of pppd (called ipppd) for using this feature. See and for more information. Support generic MP (RFC 1717) CONFIG_ISDN_MPP With synchronous PPP enabled, it is possible to increase throughput by bundling several ISDN-connections, using this protocol. See for more information. Use VJ-compression with synchronous PPP CONFIG_ISDN_PPP_VJ This enables Van Jacobson header compression for synchronous PPP. Say Y if the other end of the connection supports it. Support BSD compression CONFIG_ISDN_PPP_BSDCOMP Support for the BSD-Compress compression method for PPP, which uses the LZW compression method to compress each PPP packet before it is sent over the wire. The machine at the other end of the PPP link (usually your ISP) has to support the BSD-Compress compression method as well for this to be useful. Even if they don't support it, it is safe to say Y here. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called isdn_bsdcomp.o. Support audio via ISDN CONFIG_ISDN_AUDIO If you say Y here, the modem-emulator will support a subset of the EIA Class 8 Voice commands. Using a getty with voice-support (mgetty+sendfax by gert@greenie.muc.de with an extension, available with the ISDN utility package for example), you will be able to use your Linux box as an ISDN-answering machine. Of course, this must be supported by the lowlevel driver also. Currently, the HiSax driver is the only voice-supporting driver. See for more information. X.25 PLP on top of ISDN CONFIG_ISDN_X25 This feature provides the X.25 protocol over ISDN connections. See for more information if you are thinking about using this. ISDN diversion services support CONFIG_ISDN_DIVERSION This option allows you to use some supplementary diversion services in conjunction with the HiSax driver on an EURO/DSS1 line. Supported options are CD (call deflection), CFU (Call forward unconditional), CFB (Call forward when busy) and CFNR (call forward not reachable). Additionally the actual CFU, CFB and CFNR state may be interrogated. The use of CFU, CFB, CFNR and interrogation may be limited to some countries. The keypad protocol is still not implemented. CD should work in all countries if the service has been subscribed to. Please read the file . If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called dss1_divert.o. ICN 2B and 4B support CONFIG_ISDN_DRV_ICN This enables support for two kinds of ISDN-cards made by a German company called ICN. 2B is the standard version for a single ISDN line with two B-channels, 4B supports two ISDN lines. For running this card, additional firmware is necessary, which has to be downloaded into the card using a utility which is distributed separately. See and for more information. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called icn.o. isdnloop support CONFIG_ISDN_DRV_LOOP This driver provides a virtual ISDN card. Its primary purpose is testing of linklevel features or configuration without getting charged by your service-provider for lots of phone calls. You need will need the loopctrl utility from the latest isdn4k-utils package to set up this driver. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called isdnloop.o. HiSax SiemensChipSet driver support CONFIG_ISDN_DRV_HISAX This is a driver supporting the Siemens chipset on various ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many compatibles). HiSax is just the name of this driver, not the name of any hardware. If you have a card with such a chipset, you should say Y here and also to the configuration option of the driver for your particular card, below. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called hisax.o. See for more information on using this driver. HiSax Support for EURO/DSS1 CONFIG_HISAX_EURO Say Y or N according to the D-channel protocol which your local telephone service company provides. The call control protocol E-DSS1 is used in most European countries. If unsure, say Y. Support for German chargeinfo CONFIG_DE_AOC If you want that the HiSax hardware driver sends messages to the upper level of the isdn code on each AOCD (Advice Of Charge, During the call -- transmission of the fee information during a call) and on each AOCE (Advice Of Charge, at the End of the call -- transmission of fee information at the end of the call), say Y here. This works only in Germany. Disable sending complete CONFIG_HISAX_NO_SENDCOMPLETE If you have trouble with some ugly exchanges or you live in Australia select this option. Disable sending low layer compatibility CONFIG_HISAX_NO_LLC If you have trouble with some ugly exchanges try to select this option. Disable keypad protocol option CONFIG_HISAX_NO_KEYPAD If you like to send special dial strings including * or # without using the keypad protocol, select this option. HiSax Support for German 1TR6 CONFIG_HISAX_1TR6 Say Y or N according to the D-channel protocol which your local telephone service company provides. 1TR6 is an old call control protocol which was used in Germany before E-DSS1 was established. Nowadays, all new lines in Germany use E-DSS1. HiSax Support for US NI1 CONFIG_HISAX_NI1 Enable this if you like to use ISDN in US on a NI1 basic rate interface. Maximum number of cards supported by HiSax CONFIG_HISAX_MAX_CARDS This is used to allocate a driver-internal structure array with one entry for each HiSax card on your system. Teles 16.0/8.0 CONFIG_HISAX_16_0 This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8 and many compatibles. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port/shmem settings. Teles 16.3 or PNP or PCMCIA CONFIG_HISAX_16_3 This enables HiSax support for the Teles ISDN-cards S0-16.3 the Teles/Creatix PnP and the Teles PCMCIA. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. Teles PCI CONFIG_HISAX_TELESPCI This enables HiSax support for the Teles PCI. See on how to configure it. Teles S0Box CONFIG_HISAX_S0BOX This enables HiSax support for the Teles/Creatix parallel port S0BOX. See on how to configure it. AVM A1 (Fritz) CONFIG_HISAX_AVM_A1 This enables HiSax support for the AVM A1 (aka "Fritz"). See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. AVM PnP/PCI (Fritz!PnP/PCI) CONFIG_HISAX_FRITZPCI This enables HiSax support for the AVM "Fritz!PnP" and "Fritz!PCI". See on how to configure it. AVM A1 PCMCIA (Fritz) CONFIG_HISAX_AVM_A1_PCMCIA This enables HiSax support for the AVM A1 "Fritz!PCMCIA"). See on how to configure it. Elsa cards CONFIG_HISAX_ELSA This enables HiSax support for the Elsa Mircolink ISA cards, for the Elsa Quickstep series cards and Elsa PCMCIA. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. ITK ix1-micro Revision 2 CONFIG_HISAX_IX1MICROR2 This enables HiSax support for the ITK ix1-micro Revision 2 card. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. Eicon.Diehl Diva cards CONFIG_HISAX_DIEHLDIVA This enables HiSax support for the Eicon.Diehl Diva none PRO versions passive ISDN cards. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. ASUSCOM ISA cards CONFIG_HISAX_ASUSCOM This enables HiSax support for the AsusCom and their OEM versions passive ISDN ISA cards. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. TELEINT cards CONFIG_HISAX_TELEINT This enables HiSax support for the TELEINT SA1 semiactiv ISDN card. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. HFC-S based cards CONFIG_HISAX_HFCS This enables HiSax support for the HFC-S 2BDS0 based cards, like teles 16.3c. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. Sedlbauer cards CONFIG_HISAX_SEDLBAUER This enables HiSax support for the Sedlbauer passive ISDN cards. See on how to configure it using the different cards, a different D-channel protocol, or non-standard IRQ/port settings. USR Sportster internal TA CONFIG_HISAX_SPORTSTER This enables HiSax support for the USR Sportster internal TA card. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. MIC card CONFIG_HISAX_MIC This enables HiSax support for the ITH MIC card. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. NETjet card CONFIG_HISAX_NETJET This enables HiSax support for the NetJet from Traverse Technologies. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. NETspider U card CONFIG_HISAX_NETJET_U This enables HiSax support for the Netspider U interface ISDN card from Traverse Technologies. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. Niccy PnP/PCI card CONFIG_HISAX_NICCY This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. Siemens I-Surf card CONFIG_HISAX_ISURF This enables HiSax support for the Siemens I-Talk/I-Surf card with ISAR chip. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. HST Saphir card CONFIG_HISAX_HSTSAPHIR This enables HiSax support for the HST Saphir card. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. Telekom A4T card CONFIG_HISAX_BKM_A4T This enables HiSax support for the Telekom A4T card. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. Scitel Quadro card CONFIG_HISAX_SCT_QUADRO This enables HiSax support for the Scitel Quadro card. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. Gazel cards CONFIG_HISAX_GAZEL This enables HiSax support for the Gazel cards. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. HFC PCI-Bus cards CONFIG_HISAX_HFC_PCI This enables HiSax support for the HFC-S PCI 2BDS0 based cards. For more informations see under . Winbond W6692 based cards CONFIG_HISAX_W6692 This enables HiSax support for Winbond W6692 based PCI ISDN cards. See on how to configure it using a different D-channel protocol, or non-standard IRQ/port settings. HFC-S+, HFC-SP, HFC-PCMCIA cards CONFIG_HISAX_HFC_SX This enables HiSax support for the HFC-S+, HFC-SP and HFC-PCMCIA cards. This code is not finished yet. Am7930 CONFIG_HISAX_AMD7930 This enables HiSax support for the AMD7930 chips on some SPARCs. This code is not finished yet. HiSax debugging CONFIG_HISAX_DEBUG This enables debugging code in the new-style HiSax drivers, i.e. the ST5481 USB driver currently. If in doubt, say yes. ELSA PCMCIA MicroLink cards CONFIG_HISAX_ELSA_CS This enables the PCMCIA client driver for the Elsa PCMCIA MicroLink card. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called elsa_cs.o. Sedlbauer PCMCIA cards CONFIG_HISAX_SEDLBAUER_CS This enables the PCMCIA client driver for the Sedlbauer Speed Star and Speed Star II cards. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called sedlbauer_cs.o. CONFIG_HISAX_AVM_A1_CS This enables the PCMCIA client driver for the AVM A1 / Fritz!Card PCMCIA cards. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called avma1_cs.o. ST5481 USB ISDN modem CONFIG_HISAX_ST5481 This enables the driver for ST5481 based USB ISDN adapters, e.g. the BeWan Gazel 128 USB PCBIT-D support CONFIG_ISDN_DRV_PCBIT This enables support for the PCBIT ISDN-card. This card is manufactured in Portugal by Octal. For running this card, additional firmware is necessary, which has to be downloaded into the card using a utility which is distributed separately. See and for more information. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called pcbit.o. Spellcaster support CONFIG_ISDN_DRV_SC This enables support for the Spellcaster BRI ISDN boards. This driver currently builds only in a modularized version ( = code which can be inserted in and removed from the running kernel whenever you want, details in ); the module will be called sc.o. See and for more information. Eicon active card support CONFIG_ISDN_DRV_EICON Say Y here if you have an Eicon active ISDN card. In order to use this card, additional firmware is necessary, which has to be loaded into the card using the eiconctrl utility which is part of the latest isdn4k-utils package. Please read the file for more information. Legacy Eicon driver CONFIG_ISDN_DRV_EICON_OLD Say Y here to use your Eicon active ISDN card with ISDN4Linux isdn module. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called eicon.o. Eicon PCI DIVA Server BRI/PRI/4BRI support CONFIG_ISDN_DRV_EICON_PCI Say Y here if you have an Eicon Diva Server (BRI/PRI/4BRI) ISDN card. Please read for more information. Eicon old-type (S,SX,SCOM,Quadro,S2M) card support CONFIG_ISDN_DRV_EICON_ISA Say Y here if you have an old-type Eicon active ISDN card. In order to use this card, additional firmware is necessary, which has to be loaded into the card using the eiconctrl utility which is part of the latest isdn4k-utils package. Please read the file for more information. Eicon driver type standalone CONFIG_ISDN_DRV_EICON_DIVAS Enable this option if you want the eicon driver as standalone version with no interface to the ISDN4Linux isdn module. If you say Y here, the eicon module only supports the Diva Server PCI cards and will provide its own IDI interface. You should say N here. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called divas.o. Support AT-Fax Class 1 and 2 commands CONFIG_ISDN_TTY_FAX If you say Y here, the modem-emulator will support a subset of the Fax Class 1 and 2 commands. Using a getty with fax-support (mgetty+sendfax, hylafax), you will be able to use your Linux box as an ISDN-fax-machine. This must be supported by the lowlevel driver also. See for more information. CAPI2.0 support CONFIG_ISDN_CAPI This provides the CAPI (Common ISDN Application Programming Interface, a standard making it easy for programs to access ISDN hardware, see . This is needed for AVM's set of active ISDN controllers like B1, T1, M1. This code is also available as a module ( = code which can be inserted in and removed from the running kernel whenever you want). The modules will be called capi.o and kernelcapi.o. If you want to compile it as a module, say M here and read . CAPI2.0 /dev/capi20 support CONFIG_ISDN_CAPI_CAPI20 This option will provide the CAPI 2.0 interface to userspace applications via /dev/capi20. Applications should use the standardized libcapi20 to access this functionality. You should say Y/M here. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called capi.o. CAPI2.0 Middleware support CONFIG_ISDN_CAPI_MIDDLEWARE This option will enhance the capabilities of the /dev/capi20 interface. It will provide a means of moving a data connection, established via the usual /dev/capi20 interface to a special tty device. If you want to use pppd with pppdcapiplugin to dial up to your ISP, say Y here. CAPI2.0 filesystem support CONFIG_ISDN_CAPI_CAPIFS This option provides a special file system, similar to /dev/pts with device nodes for the special ttys established by using the middleware extension above. If you want to use pppd with pppdcapiplugin to dial up to your ISP, say Y here. CAPI2.0 capidrv interface support CONFIG_ISDN_CAPI_CAPIDRV This option provides the glue code to hook up CAPI driven cards to the legacy isdn4linux link layer. If you have a card which is supported by a CAPI driver, but still want to use old features like ippp interfaces or ttyI emulation, say Y/M here. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called capidrv.o. AVM B1 ISA support CONFIG_ISDN_DRV_AVMB1_B1ISA Enable support for the ISA version of the AVM B1 card. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called b1isa.o. AVM B1 PCI support CONFIG_ISDN_DRV_AVMB1_B1CICI Enable support for the PCI version of the AVM B1 card. AVM B1 PCI V4 support CONFIG_ISDN_DRV_AVMB1_B1PCIV4 Enable support for the V4 version of AVM B1 PCI card. AVM T1/T1-B ISA support CONFIG_ISDN_DRV_AVMB1_T1ISA Enable support for the AVM T1 T1B card. Note: This is a PRI card and handle 30 B-channels. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called t1isa.o. AVM B1/M1/M2 PCMCIA support CONFIG_ISDN_DRV_AVMB1_B1PCMCIA Enable support for the PCMCIA version of the AVM B1 card. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called b1pcmcia.o. AVM B1/M1/M2 PCMCIA cs module CONFIG_ISDN_DRV_AVMB1_AVM_CS Enable the PCMCIA client driver for the AVM B1/M1/M2 PCMCIA cards. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called avm_cs.o. AVM T1/T1-B PCI support CONFIG_ISDN_DRV_AVMB1_T1PCI Enable support for the AVM T1 T1B card. Note: This is a PRI card and handle 30 B-channels. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called t1pci.o. AVM C4/C2 support CONFIG_ISDN_DRV_AVMB1_C4 Enable support for the AVM C4/C2 PCI cards. These cards handle 4/2 BRI ISDN lines (8/4 channels). If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called c4.o. Verbose reason code reporting (kernel size +=7K) CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON If you say Y here, the AVM B1 driver will give verbose reasons for disconnecting. This will increase the size of the kernel by 7 KB. If unsure, say Y. IBM Active 2000 support CONFIG_ISDN_DRV_ACT2000 Say Y here if you have an IBM Active 2000 ISDN card. In order to use this card, additional firmware is necessary, which has to be loaded into the card using a utility which is part of the latest isdn4k-utils package. Please read the file for more information. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called act2000.o. Auvertech TurboPAM support CONFIG_ISDN_DRV_TPAM This enables support for the Auvertech TurboPAM ISDN-card. For running this card, additional firmware is necessary, which has to be downloaded into the card using a utility which is distributed separately from the Auvertech's web site: . Please redirect all support questions to support@auvertech.fr. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called tpam.o. Hypercope HYSDN cards (Champ, Ergo, Metro) support (module) CONFIG_HYSDN Say Y here if you have one of Hypercope's active PCI ISDN cards Champ, Ergo and Metro. You will then get a module called hysdn.o. Please read the file for more information. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called hysdn.o. HYSDN CAPI 2.0 support CONFIG_HYSDN_CAPI Say Y here if you like to use Hypercope's CAPI 2.0 interface. Support for SUN4 machines (disables SUN4[CDM] support) CONFIG_SUN4 Say Y here if, and only if, your machine is a Sun4. Note that a kernel compiled with this option will run only on Sun4. (And the current version will probably work only on sun4/330.) SPARC ESP SCSI support CONFIG_SCSI_SUNESP This is the driver for the Sun ESP SCSI host adapter. The ESP chipset is present in most SPARC SBUS-based computers. This support is also available as a module called esp.o ( = 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 . PTI Qlogic, ISP Driver CONFIG_SCSI_QLOGICPTI This driver supports SBUS SCSI controllers from PTI or QLogic. These controllers are known under Solaris as qpti and in the openprom as PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are driven by a different driver. This support is also available as a module called qlogicpti.o ( = 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 . Sun PROM console CONFIG_PROM_CONSOLE Say Y to build a console driver for Sun machines that uses the terminal emulation built into their console PROMS. /dev/openprom device support CONFIG_SUN_OPENPROMIO This driver provides user programs with an interface to the SPARC PROM device tree. The driver implements a SunOS-compatible interface and a NetBSD-compatible interface. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M and read . If unsure, say Y. Openprom tree appears in /proc/openprom CONFIG_SUN_OPENPROMFS If you say Y, the OpenPROM device tree will be available as a virtual file system, which you can mount to /proc/openprom by "mount -t openpromfs none /proc/openprom". If you want to compile the /proc/openprom support as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called openpromfs.o. If unsure, say M. Kernel support for Linux/Sparc 32bit binary compatibility CONFIG_SPARC32_COMPAT This allows you to run 32-bit binaries on your Ultra. Everybody wants this; say Y. Kernel support for 32-bit ELF binaries CONFIG_BINFMT_ELF32 This allows you to run 32-bit Linux/ELF binaries on your machine. Everybody wants this; say Y. Kernel support for 32-bit (ie. SunOS) a.out binaries CONFIG_BINFMT_AOUT32 This allows you to run 32-bit a.out format binaries on your Ultra. If you want to run SunOS binaries (see SunOS binary emulation below) or other a.out binaries, say Y. If unsure, say N. SunOS binary emulation CONFIG_SUNOS_EMUL This allows you to run most SunOS binaries. If you want to do this, say Y here and place appropriate files in /usr/gnemul/sunos. See for more information. If you want to run SunOS binaries on an Ultra you must also say Y to "Kernel support for 32-bit a.out binaries" above. Mostek real time clock support CONFIG_SUN_MOSTEK_RTC The Mostek RTC chip is used on all known Sun computers except some JavaStations. For a JavaStation you need to say Y both here and to "Enhanced Real Time Clock Support". Say Y here unless you are building a special purpose kernel. OBP Flash Device support CONFIG_OBP_FLASH The OpenBoot PROM on Ultra systems is flashable. If you want to be able to upgrade the OBP firmware, say Y here. JavaStation OS Flash SIMM CONFIG_SUN_JSFLASH If you say Y here, you will be able to boot from your JavaStation's Flash memory. Siemens SAB82532 serial support CONFIG_SAB82532 This driver supports the serial ports on newer (PCI) Ultra systems. Say Y if you want to be able to use your serial ports. Videopix Frame Grabber CONFIG_SUN_VIDEOPIX Say Y here to support the Videopix Frame Grabber from Sun Microsystems, commonly found on SPARCstations. This card, which is based on the Phillips SAA9051, can handle NTSC and PAL/SECAM and SVIDEO signals. Sun bidirectional parallel port support CONFIG_SUN_BPP Say Y here to support Sun's obsolete variant of IEEE1284 bidirectional parallel port protocol as /dev/bppX. Can be built on x86 machines. Aurora Multiboard 1600se CONFIG_SUN_AURORA The Aurora Multiboard is a multi-port high-speed serial controller. If you have one of these, say Y. Tadpole TS102 Microcontroller support CONFIG_TADPOLE_TS102_UCTRL Say Y here to directly support the TS102 Microcontroller interface on the Tadpole Sparcbook 3. This device handles power-management events, and can also notice the attachment/detachment of external monitors and mice. Audio support CONFIG_SPARCAUDIO This driver provides support for the build-in sound devices on most Sun machines. If you want to be able to use this, select this option and one or more of the lowlevel drivers below. See for more information. AMD7930 Lowlevel Driver CONFIG_SPARCAUDIO_AMD7930 This driver supports the AMD 7930 chip found on sun4c, 4/6xx, and SparcClassic systems. CS4231 Lowlevel Driver CONFIG_SPARCAUDIO_CS4231 This driver supports the Crystal Semiconductor CS4231 chip found on the SS4, SS5, and Ultras. DBRI Lowlevel Driver CONFIG_SPARCAUDIO_DBRI This driver supports the DBRI audio interface found on the SS10, SS20, LX, Sparcbook 3, and Voyager systems. Dummy Lowlevel Driver CONFIG_SPARCAUDIO_DUMMY This is a pseudo-driver used for debugging and testing the sparcaudio subsystem. Say N unless you want to work on this subsystem. Sparc hardware CONFIG_PARPORT_SUNBPP This driver provides support for the bidirectional parallel port found on many Sun machines. Note that many of the newer Ultras actually have pc style hardware instead. SPARC power management support CONFIG_SUN_PM Enable power management and CPU standby features on supported SPARC platforms. /proc/hardware support CONFIG_PROC_HARDWARE Say Y here to support the /proc/hardware file, which gives you access to information about the machine you're running on, including the model, CPU, MMU, clock speed, BogoMIPS rating, and memory size. Bluetooth subsystem support CONFIG_BLUEZ Bluetooth is low-cost, low-power, short-range wireless technology. It was designed as a replacement for cables and other short-range technologies like IrDA. Bluetooth operates in personal area range that typically extends up to 10 meters. More information about Bluetooth can be found at . Linux Bluetooth subsystem consist of several layers: BlueZ Core (HCI device and connection manager, scheduler) HCI Device drivers (interface to the hardware) L2CAP Module (L2CAP protocol) SCO Module (SCO links) Say Y here to enable Linux Bluetooth support and to build BlueZ Core layer. To use Linux Bluetooth subsystem, you will need several user-space utilities like hciconfig and hcid. These utilities and updates to Bluetooth kernel modules are provided in the BlueZ package. For more information, see . If you want to compile BlueZ Core as module (bluez.o) say M here. L2CAP protocol support CONFIG_BLUEZ_L2CAP L2CAP (Logical Link Control and Adaptation Protocol) provides connection oriented and connection-less data transport. L2CAP support is required for most Bluetooth applications. Say Y here to compile L2CAP support into the kernel or say M to compile it as module (l2cap.o). SCO links support CONFIG_BLUEZ_SCO SCO link provides voice transport over Bluetooth. SCO support is required for voice applications like Headset and Audio. Say Y here to compile SCO support into the kernel or say M to compile it as module (sco.o). BNEP protocol support CONFIG_BLUEZ_BNEP BNEP (Bluetooth Network Encapsulation Protocol) is Ethernet emulation layer on top of Bluetooth. BNEP is required for Bluetooth PAN (Personal Area Network). To use BNEP, you will need user-space utilities provided in the BlueZ-PAN package. For more information, see . Say Y here to compile BNEP support into the kernel or say M to compile it as module (bnep.o). HCI UART driver CONFIG_BLUEZ_HCIUART Bluetooth HCI UART driver. This driver is required if you want to use Bluetooth devices with serial port interface. You will also need this driver if you have UART based Bluetooth PCMCIA and CF devices like Xircom Credit Card adapter and BrainBoxes Bluetooth PC Card. Say Y here to compile support for Bluetooth UART devices into the kernel or say M to compile it as module (hci_uart.o). HCI UART (H4) protocol support CONFIG_BLUEZ_HCIUART_H4 UART (H4) is serial protocol for communication between Bluetooth device and host. This protocol is required for most UART based Bluetooth device (including PCMCIA and CF). Say Y here to compile support for HCI UART (H4) protocol. HCI USB driver CONFIG_BLUEZ_HCIUSB Bluetooth HCI USB driver. This driver is required if you want to use Bluetooth devices with USB interface. Say Y here to compile support for Bluetooth USB devices into the kernel or say M to compile it as module (hci_usb.o). HCI USB zero packet support CONFIG_BLUEZ_USB_ZERO_PACKET Support for USB zero packets. This option is provided only as a work around for buggy Bluetooth USB devices. Do _not_ enable it unless you know for sure that your device requires zero packets. Most people should say N here. HCI VHCI Virtual HCI device driver CONFIG_BLUEZ_HCIVHCI Bluetooth Virtual HCI device driver. This driver is required if you want to use HCI Emulation software. Say Y here to compile support for virtual HCI devices into the kernel or say M to compile it as module (hci_vhci.o). HCI DTL1 (PC Card) device driver CONFIG_BLUEZ_HCIDTL1 Bluetooth HCI DTL1 (PC Card) driver. This driver provides support for Bluetooth PCMCIA devices with Nokia DTL1 interface: Nokia Bluetooth Card Socket Bluetooth CF Card Say Y here to compile support for HCI DTL1 devices into the kernel or say M to compile it as module (dtl1_cs.o). HCI BT3C (PC Card) device driver CONFIG_BLUEZ_HCIBT3C Bluetooth HCI BT3C (PC Card) driver. This driver provides support for Bluetooth PCMCIA devices with 3Com BT3C interface: 3Com Bluetooth Card (3CRWB6096) HP Bluetooth Card The HCI BT3C driver uses external firmware loader program provided in the BlueFW package. For more information, see . Say Y here to compile support for HCI BT3C devices into the kernel or say M to compile it as module (bt3c_cs.o). HCI BlueCard (PC Card) device driver CONFIG_BLUEZ_HCIBLUECARD Bluetooth HCI BlueCard (PC Card) driver. This driver provides support for Bluetooth PCMCIA devices with Anycom BlueCard interface: Anycom Bluetooth PC Card Anycom Bluetooth CF Card Say Y here to compile support for HCI BlueCard devices into the kernel or say M to compile it as module (bluecard_cs.o). # The following options are for Linux when running on the Hitachi # SuperH family of RISC microprocessors. SuperH RTC support CONFIG_SH_RTC Selecting this option will allow the Linux kernel to emulate PC's RTC. If unsure, say N. SuperH DMAC support CONFIG_SH_DMA Selecting this option will provide same API as PC's Direct Memory Access Controller(8237A) for SuperH DMAC. If unsure, say N. # Choice: cf_area CompactFlash Connection Area CONFIG_CF_AREA5 If your board has "Directly Connected" CompactFlash, You should select the area where your CF is connected to. - "Area5" if CompactFlash is connected to Area 5 (0x14000000) - "Area6" if it is connected to Area 6 (0x18000000) "Area6" will work for most boards. For ADX, select "Area5". Disable data cache CONFIG_DCACHE_DISABLE This option allows you to run the kernel with data cache disabled. Say Y if you experience CPM lock-ups. # # m68k-specific kernel options # Documented by Chris Lawrence et al. # Amiga support CONFIG_AMIGA This option enables support for the Amiga series of computers. If you plan to use this kernel on an Amiga, say Y here and browse the material available in ; otherwise say N. Commodore A2232 serial support CONFIG_A2232 This option supports the 2232 7-port serial card shipped with the Amiga 2000 and other Zorro-bus machines, dating from 1989. At a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The ports were connected with 8 pin DIN connectors on the card bracket, for which 8 pin to DB25 adapters were supplied. The card also had jumpers internally to toggle various pinning configurations. This driver can be built as a module; but then "generic_serial.o" will also be built as a module. This has to be loaded before "ser_a2232.o". If you want to do this, answer M here and read "". A4000T SCSI support CONFIG_A4000T_SCSI Support for the NCR53C710 SCSI controller on the Amiga 4000T. A4091 SCSI support CONFIG_A4091_SCSI Support for the NCR53C710 chip on the Amiga 4091 Z3 SCSI2 controller (1993). Very obscure -- the 4091 was part of an Amiga 4000 upgrade plan at the time the Amiga business was sold to DKB. Atari support CONFIG_ATARI This option enables support for the 68000-based Atari series of computers (including the TT, Falcon and Medusa). If you plan to use this kernel on an Atari, say Y here and browse the material available in ; otherwise say N. Hades support CONFIG_HADES This option enables support for the Hades Atari clone. If you plan to use this kernel on a Hades, say Y here; otherwise say N. Macintosh support CONFIG_MAC This option enables support for the Apple Macintosh series of computers (yes, there is experimental support now, at least for part of the series). Say N unless you're willing to code the remaining necessary support. ;) HP9000/300 support CONFIG_HP300 This option enables support for the HP9000/300 series of workstations. Support for these machines is still very experimental. If you plan to try to use the kernel on such a machine say Y here. Everybody else says N. Q40/Q60 support CONFIG_Q40 The Q40 is a Motorola 68040-based successor to the Sinclair QL manufactured in Germany. There is an official Q40 home page at . This option enables support for the Q40 and Q60. Select your CPU below. For 68LC060 don't forget to enable FPU emulation. Q40/Q60 IDE interface support CONFIG_BLK_DEV_Q40IDE Enable the on-board IDE controller in the Q40/Q60. This should normally be on; disable it only if you are running a custom hard drive subsystem through an expansion card. Sun 3 support CONFIG_SUN3 This option enables support for the Sun 3 series of workstations. Note that if this option is enabled, support for all other m68k platforms above must be disabled in order to produce a working kernel. Also, you will want to enable 68020 support below, and disable all other CPU types. General Linux information on the Sun 3x series (now discontinued) is at . If you don't want to compile a kernel for a Sun 3, say N. Sun 3X support CONFIG_SUN3X This option enables support for the Sun 3x series of workstations. Currently, only the Sun 3/80 is supported within the Sun 3x family. You will also want to enable 68030 support below General Linux information on the Sun 3x series (now discontinued) is at . If you don't want to compile a kernel for a Sun 3x, say N. Sun3x builtin serial support CONFIG_SUN3X_ZS ZS refers to a type of asynchronous serial port built in to the Sun3 and Sun3x workstations; if you have a Sun 3, you probably have these. Say 'Y' to support ZS ports directly. This option must be enabled in order to support the keyboard and mouse ports. Sun keyboard support CONFIG_SUN_KEYBOARD Say Y here to support the keyboard found on Sun 3 and 3x workstations. It can also be used support Sun Type-5 keyboards through an adaptor. See and for details on the latter. 68020 support CONFIG_M68020 If you anticipate running this kernel on a computer with a MC68020 processor, say Y. Otherwise, say N. Note that the 68020 requires a 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the Sun 3, which provides its own version. 68030 support CONFIG_M68030 If you anticipate running this kernel on a computer with a MC68030 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not work, as it does not include an MMU (Memory Management Unit). 68040 support CONFIG_M68040 If you anticipate running this kernel on a computer with a MC68LC040 or MC68040 processor, say Y. Otherwise, say N. Note that an MC68EC040 will not work, as it does not include an MMU (Memory Management Unit). 68060 support CONFIG_M68060 If you anticipate running this kernel on a computer with a MC68060 processor, say Y. Otherwise, say N. Math emulation support CONFIG_M68KFPU_EMU At some point in the future, this will cause floating-point math instructions to be emulated by the kernel on machines that lack a floating-point math coprocessor. Thrill-seekers and chronically sleep-deprived psychotic hacker types can say Y now, everyone else should probably wait a while. Math emulation only kernel CONFIG_M68KFPU_EMU_ONLY This option prevents any floating-point instructions from being compiled into the kernel, thereby the kernel doesn't save any floating point context anymore during task switches, so this kernel will only be usable on machines without a floating-point math coprocessor. This makes the kernel a bit faster as no tests needs to be executed whether a floating-point instruction in the kernel should be executed or not. Math emulation extra precision CONFIG_M68KFPU_EMU_EXTRAPREC The fpu uses normally a few bit more during calculations for correct rounding, the emulator can (often) do the same but this extra calculation can cost quite some time, so you can disable it here. The emulator will then "only" calculate with a 64 bit mantissa and round slightly incorrect, what is more then enough for normal usage. Advanced configuration options CONFIG_ADVANCED This gives you access to some advanced options for the CPU. The defaults should be fine for most users, but these options may make it possible for you to improve performance somewhat if you know what you are doing. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about these options. Most users should say N to this question. Use one physical chunk of memory only CONFIG_SINGLE_MEMORY_CHUNK Ignore all but the first contiguous chunk of physical memory for VM purposes. This will save a few bytes kernel size and may speed up some operations. Say N if not sure. Use read-modify-write instructions CONFIG_RMW_INSNS This allows to use certain instructions that work with indivisible read-modify-write bus cycles. While this is faster than the workaround of disabling interrupts, it can conflict with DMA ( = direct memory access) on many Amiga systems, and it is also said to destabilize other machines. It is very likely that this will cause serious problems on any Amiga or Atari Medusa if set. The only configuration where it should work are 68030-based Ataris, where it apparently improves performance. But you've been warned! Unless you really know what you are doing, say N. Try Y only if you're quite adventurous. Amiga Zorro (AutoConfig) bus support CONFIG_ZORRO This enables support for the Zorro bus in the Amiga. If you have expansion cards in your Amiga that conform to the Amiga AutoConfig(tm) specification, say Y, otherwise N. Note that even expansion cards that do not fit in the Zorro slots but fit in e.g. the CPU slot may fall in this category, so you have to say Y to let Linux use these. Zorro device name database CONFIG_ZORRO_NAMES By default, the kernel contains a database of all known Zorro device names to make the information in /proc/iomem comprehensible to the user. This database increases the size of the kernel image by about 15KB, but it gets freed after the system boots up, so it doesn't take up kernel memory. Anyway, if you are building an installation floppy or kernel for an embedded system where kernel image size really matters, you can disable this feature and you'll get device ID numbers instead of names. When in doubt, say Y. Amiga 1200/600 PCMCIA support CONFIG_AMIGA_PCMCIA Include support in the kernel for pcmcia on Amiga 1200 and Amiga 600. If you intend to use pcmcia cards say Y; otherwise say N. Hisoft Whippet PCMCIA serial support CONFIG_WHIPPET_SERIAL HiSoft has a web page at , but there is no listing for the Whippet in their Amiga section. Amiga Zorro II ramdisk support CONFIG_AMIGA_Z2RAM This enables support for using Chip RAM and Zorro II RAM as a ramdisk or as a swap partition. Say Y if you want to include this driver in the kernel. 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 is called z2ram.o. If you want to compile it as a module, say M here and read . Support for ST-RAM as swap space CONFIG_STRAM_SWAP Some Atari 68k machines (including the 520STF and 1020STE) divide their addressable memory into ST and TT sections. The TT section (up to 512MB) is the main memory; the ST section (up to 4MB) is accessible to the built-in graphics board, runs slower, and is present mainly for backward compatibility with older machines. This enables support for using (parts of) ST-RAM as swap space, instead of as normal system memory. This can first enhance system performance if you have lots of alternate RAM (compared to the size of ST-RAM), because executable code always will reside in faster memory. ST-RAM will remain as ultra-fast swap space. On the other hand, it allows much improved dynamic allocations of ST-RAM buffers for device driver modules (e.g. floppy, ACSI, SLM printer, DMA sound). The probability that such allocations at module load time fail is drastically reduced. ST-RAM statistics in /proc CONFIG_STRAM_PROC Say Y here to report ST-RAM usage statistics in /proc/stram. See the help for CONFIG_STRAM_SWAP for discussion of ST-RAM and its uses. Atari ACSI support CONFIG_ATARI_ACSI This enables support for the Atari ACSI interface. The driver supports hard disks and CD-ROMs, which have 512-byte sectors, or can be switched to that mode. Due to the ACSI command format, only disks up to 1 GB are supported. Special support for certain ACSI to SCSI adapters, which could relax that, isn't included yet. The ACSI driver is also the basis for certain other drivers for devices attached to the ACSI bus: Atari SLM laser printer, BioNet-100 Ethernet, and PAMsNet Ethernet. If you want to use one of these devices, you need ACSI support, too. 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 acsi.o. Probe all LUNs on each ACSI device CONFIG_ACSI_MULTI_LUN If you have a ACSI device that supports more than one LUN (Logical Unit Number), e.g. a CD jukebox, you should say Y here so that all will be found by the ACSI driver. An ACSI device with multiple LUNs acts logically like multiple ACSI devices. The vast majority of ACSI devices have only one LUN, and so most people can say N here and should in fact do so, because it is safer. Atari SLM laser printer support CONFIG_ATARI_SLM If you have an Atari SLM laser printer, say Y to include support for it in the kernel. Otherwise, say N. 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 acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause problems due to that fact! A3000 WD33C93A support CONFIG_A3000_SCSI If you have an Amiga 3000 and have SCSI devices connected to the built-in SCSI controller, say Y. Otherwise, say N. 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 is called wd33c93.o. If you want to compile it as a module, say M here and read . A2091 WD33C93A support CONFIG_A2091_SCSI If you have a Commodore A2091 SCSI controller, say Y. Otherwise, say N. 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 is called wd33c93.o. If you want to compile it as a module, say M here and read . GVP Series II WD33C93A support CONFIG_GVP11_SCSI If you have a Great Valley Products Series II SCSI controller, answer Y. Also say Y if you have a later model of GVP SCSI controller (such as the GVP A4008 or a Combo board). Otherwise, answer N. This driver does NOT work for the T-Rex series of accelerators from TekMagic and GVP-M. 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 gvp11.o. If you want to compile it as a module, say M here and read . CyberStorm SCSI support CONFIG_CYBERSTORM_SCSI If you have an Amiga with an original (MkI) Phase5 Cyberstorm accelerator board and the optional Cyberstorm SCSI controller, answer Y. Otherwise, say N. CyberStorm II SCSI support CONFIG_CYBERSTORMII_SCSI If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board and the optional Cyberstorm SCSI controller, say Y. Otherwise, answer N. Blizzard 2060 SCSI support CONFIG_BLZ2060_SCSI If you have an Amiga with a Phase5 Blizzard 2060 accelerator board and want to use the onboard SCSI controller, say Y. Otherwise, answer N. Blizzard 1230IV/1260 SCSI support CONFIG_BLZ1230_SCSI If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard 1260 accelerator, and the optional SCSI module, say Y. Otherwise, say N. Blizzard PowerUP 603e+ SCSI support CONFIG_BLZ603EPLUS_SCSI If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+ accelerator, say Y. Otherwise, say N. Fastlane SCSI support CONFIG_FASTLANE_SCSI If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use one in the near future, say Y to this question. Otherwise, say N. BSC Oktagon SCSI support CONFIG_OKTAGON_SCSI If you have the BSC Oktagon SCSI disk controller for the Amiga, say Y to this question. If you're in doubt about whether you have one, see the picture at . Atari native SCSI support CONFIG_ATARI_SCSI If you have an Atari with built-in NCR5380 SCSI controller (TT, Falcon, ...) say Y to get it supported. Of course also, if you have a compatible SCSI controller (e.g. for Medusa). 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 is called atari_scsi.o. If you want to compile it as a module, say M here and read . This driver supports both styles of NCR integration into the system: the TT style (separate DMA), and the Falcon style (via ST-DMA, replacing ACSI). It does NOT support other schemes, like in the Hades (without DMA). Long delays for Toshiba CD-ROMs CONFIG_ATARI_SCSI_TOSHIBA_DELAY This option increases the delay after a SCSI arbitration to accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to use a Toshiba CD-ROM drive; otherwise, the option is not needed and would impact performance a bit, so say N. Reset SCSI-devices at boottime CONFIG_ATARI_SCSI_RESET_BOOT Reset the devices on your Atari whenever it boots. This makes the boot process fractionally longer but may assist recovery from errors that leave the devices with SCSI operations partway completed. Hades SCSI DMA emulator CONFIG_TT_DMA_EMUL This option enables code which emulates the TT SCSI DMA chip on the Hades. This increases the SCSI transfer rates at least ten times compared to PIO transfers. Sun3x ESP SCSI CONFIG_SUN3X_ESP This option will enable support for the ESP SCSI controller found onboard the Sun 3/80. Ariadne support CONFIG_ARIADNE If you have a Village Tronic Ariadne Ethernet adapter, say Y. Otherwise, say N. 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 is called ariadne.o. If you want to compile it as a module, say M here and read . Ariadne II and X-Surf support CONFIG_ARIADNE2 This driver is for the Village Tronic Ariadne II and the Individual Computers X-Surf Ethernet cards. If you have such a card, say Y. Otherwise, say N. 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 ariadne2.o. If you want to compile it as a module, say M here and read . A2065 support CONFIG_A2065 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise, say N. 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 is called a2065.o. If you want to compile it as a module, say M here and read . Hydra support CONFIG_HYDRA If you have a Hydra Ethernet adapter, say Y. Otherwise, say N. 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 is called hydra.o. If you want to compile it as a module, say M here and read . Sun3 NCR5380 SCSI CONFIG_SUN3_SCSI This option will enable support for the OBIO (onboard io) NCR5380 SCSI controller found in the Sun 3/50 and 3/60. Note that this driver does not provide support for VME SCSI boards. General Linux information on the Sun 3 series (now discontinued) is at . PCMCIA NE2000 and compatibles support CONFIG_APNE If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise, say N. 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 is called apne.o. If you want to compile it as a module, say M here and read . Atari Lance support CONFIG_ATARILANCE Say Y to include support for several Atari Ethernet adapters based on the AMD Lance chipset: RieblCard (with or without battery), or PAMCard VME (also the version by Rhotron, with different addresses). BioNet-100 support CONFIG_ATARI_BIONET Say Y to include support for BioData's BioNet-100 Ethernet adapter for the ACSI port. The driver works (has to work...) with a polled I/O scheme, so it's rather slow :-( PAMsNet support CONFIG_ATARI_PAMSNET Say Y to include support for the PAMsNet Ethernet adapter for the ACSI port ("ACSI node"). The driver works (has to work...) with a polled I/O scheme, so it's rather slow :-( Amiga mouse support CONFIG_AMIGAMOUSE If you want to be able to use an Amiga mouse in Linux, say Y. 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 is called amigamouse.o. If you want to compile it as a module, say M here and read . Atari mouse support CONFIG_ATARIMOUSE If you want to be able to use an Atari mouse in Linux, say Y. 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 is called atarimouse.o. If you want to compile it as a module, say M here and read . Atari MFP serial support CONFIG_ATARI_MFPSER If you like to use the MFP serial ports ("Modem1", "Serial1") under Linux, say Y. The driver equally supports all kinds of MFP serial ports and automatically detects whether Serial1 is available. 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 . Note for Falcon users: You also have an MFP port, it's just not wired to the outside... But you could use the port under Linux. Atari SCC serial support CONFIG_ATARI_SCC If you have serial ports based on a Zilog SCC chip (Modem2, Serial2, LAN) and like to use them under Linux, say Y. All built-in SCC's are supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have two connectors for channel A (Serial2 and LAN), they are visible as two separate devices. 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 . Atari SCC serial DMA support CONFIG_ATARI_SCC_DMA This enables DMA support for receiving data on channel A of the SCC. If you have a TT you may say Y here and read drivers/char/atari_SCC.README. All other users should say N here, because only the TT has SCC-DMA, even if your machine keeps claiming so at boot time. Atari MIDI serial support CONFIG_ATARI_MIDI If you want to use your Atari's MIDI port in Linux, say Y. 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 . Atari DSP56k Digital Signal Processor support CONFIG_ATARI_DSP56K If you want to be able to use the DSP56001 in Falcons, say Y. This driver is still experimental, and if you don't know what it is, or if you don't have this processor, just say N. 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 . Support for early boot text console CONFIG_BOOTX_TEXT Say Y here to see progress messages from the boot firmware in text mode. Requires either BootX or Open Firmware. Amiga builtin serial support CONFIG_AMIGA_BUILTIN_SERIAL If you want to use your Amiga's built-in serial port in Linux, answer Y. 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 . GVP IO-Extender support CONFIG_GVPIOEXT If you want to use a GVP IO-Extender serial card in Linux, say Y. Otherwise, say N. GVP IO-Extender parallel printer support CONFIG_GVPIOEXT_LP Say Y to enable driving a printer from the parallel port on your GVP IO-Extender card, N otherwise. GVP IO-Extender PLIP support CONFIG_GVPIOEXT_PLIP Say Y to enable doing IP over the parallel port on your GVP IO-Extender card, N otherwise. Multiface Card III serial support CONFIG_MULTIFACE_III_TTY If you want to use a Multiface III card's serial port in Linux, answer Y. 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 . Amiga/Atari/PowerMac DMA sound support CONFIG_DMASOUND Support built-in audio chips accessible by DMA on various machines that have them. Note that this symbol does not affect the kernel directly; rather, it controls whether configuration questions enabling DMA sound drivers for various specific machine architectures will be used. Atari DMA sound support CONFIG_DMASOUND_ATARI If you want to use the internal audio of your Atari 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. 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 . PowerMac DMA sound support 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. 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 . Amiga DMA sound support CONFIG_DMASOUND_PAULA If you want to use the internal audio of your Amiga 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. 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 . Q40 sound support CONFIG_DMASOUND_Q40 If you want to use the internal audio of your Q40 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. 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 . HP DCA serial support CONFIG_HPDCA If you want to use the internal "DCA" serial ports on an HP300 machine, say Y here. HP on-board LANCE support CONFIG_HPLANCE If you want to use the builtin "LANCE" Ethernet controller on an HP300 machine, say Y here. DIO bus support CONFIG_DIO Say Y here to enable support for the "DIO" expansion bus used in HP300 machines. If you are using such a system you almost certainly want this. # Choice: ppctype Processor Type CONFIG_6xx There are four types of PowerPC chips supported. The more common types (601, 603, 604, 740, 750, 7400), the Motorola embedded versions (821, 823, 850, 855, 860, 8260), the IBM embedded versions (403 and 405) and the high end 64 bit Power processors (Power 3, Power 4). Unless you are building a kernel for one of the embedded processor systems, or a 64 bit IBM RS/6000, choose 6xx. Note that the kernel runs in 32-bit mode even on 64-bit chips. Also note that because the 82xx family has a 603e core, specific support for that chipset is asked later on. Motorola MPC8260 CPM support CONFIG_8260 The MPC8260 CPM (Communications Processor Module) is a typical embedded CPU made by Motorola. Selecting this option means that you wish to build a kernel for a machine with specifically an 8260 for a CPU. If in doubt, say N. # Choice: ppc4xxtype Oak CONFIG_OAK Select Oak if you have an IBM 403GCX "Oak" Evaluation Board. Select Walnut if you have an IBM 405GP "Walnut" Evaluation Board. More information on these boards is available at: . Walnut CONFIG_WALNUT Select Walnut if you have an IBM 405GP "Walnut" Evaluation Board. Workarounds for PPC601 bugs CONFIG_PPC601_SYNC_FIX 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. 8xx Cache (Copy-Back or Writethrough) CONFIG_8xx_COPYBACK Saying Y here will cause the cache on an MPC8xx processor to be used in Copy-Back mode. If you say N here, it is used in Writethrough mode. If in doubt, say Y here. MPC860 (Pre Rev. C) CPU6 Silicon Errata CONFIG_8xx_CPU6 MPC860 CPUs, prior to Rev C have some bugs in the silicon, which require workarounds for Linux (and most other OSes to work). If you get a BUG() very early in boot, this might fix the problem. For more details read the document entitled "MPC860 Family Device Errata Reference" on Motorola's website. This option also incurs a performance hit. If in doubt, say N here. MPC8xx direct IDE support on PCMCIA port CONFIG_BLK_DEV_MPC8xx_IDE This option provides support for IDE on Motorola MPC8xx Systems. Please see 'Type of MPC8xx IDE interface' for details. If unsure, say N. # Choice: mpc8xxtype Type of MPC8xx IDE interface CONFIG_IDE_8xx_PCCARD Select how the IDE devices are connected to the MPC8xx system: 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination with a PC Card (e.g. ARGOSY portable Hard Disk Adapter), ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL systems) 8xx_DIRECT is used for directly connected IDE devices using the 8xx internal PCMCIA interface (example: IVMS8 systems) EXT_DIRECT is used for IDE devices directly connected to the 8xx bus using some glue logic, but _not_ the 8xx internal PCMCIA interface (example: IDIF860 systems) Use SMC2 for UART CONFIG_SMC2_UART If you would like to use SMC2 as a serial port, say Y here. If in doubt, say Y here. Use SMC2 for Console CONFIG_CONS_SMC2 If you are going to have a serial console on your device and are using SMC2 for your serial port, say Y here, else say N. Use the alternate SMC2 I/O CONFIG_ALTSMC2 If you have an MPC823 or MPC850 and would like to use the alternate SMC2 for I/O, say Y here. If in doubt, say N here. 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. If in doubt, say N here. # Choice: ppc6xxtype Machine Type CONFIG_ALL_PPC Linux currently supports several different kinds of PowerPC-based machines: Apple Power Macintoshes and clones (such as the Motorola Starmax series), PReP (PowerPC Reference Platform) machines (such as the Motorola PowerStacks, Motorola cPCI/VME embedded systems, and some IBM RS/6000 systems), CHRP (Common Hardware Reference Platform), and several embedded PowerPC systems containing 4xx, 6xx, 7xx, 8xx, 74xx, and 82xx processors. Currently, the default option is to build a kernel which works on the first three. Select PowerMac/PReP/MTX/CHRP if configuring for any of the above. Select Gemini if configuring for a Synergy Microsystems' Gemini series Single Board Computer. More information is available at: . Select APUS if configuring for a PowerUP Amiga. More information is available at: . Note that Total Impact briQ is handled as a CHRP machine. Synergy-Gemini CONFIG_GEMINI Select Gemini if configuring for a Synergy Microsystems' Gemini series Single Board Computer. More information is available at: . Amiga-Apus CONFIG_APUS Select APUS if configuring for a PowerUP Amiga. More information is available at: . AltiVec kernel support CONFIG_ALTIVEC 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. Thermal Management Support CONFIG_TAU 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. Interrupt driven TAU driver CONFIG_TAU_INT 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. Average high and low temp CONFIG_TAU_AVERAGE The TAU hardware can compare the temperature to an upper and lower bound. The default behaviour 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. Power management support for PowerBooks CONFIG_PMAC_PBOOK This provides support for putting a PowerBook to sleep; it also enables media bay support. Power management works on the PB2400/3400/3500, Wallstreet, Lombard, and Bronze PowerBook G3. You must get the power management daemon, pmud, to make it work and you must have the /dev/pmu device (see the pmud README). Get pmud from . If you have a PowerBook, you should say Y. You may also want to compile the dma sound driver as a module and 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 Macintosh PowerBook. With this code, the backlight will be turned on and off appropriately on power-management and lid-open/lid-closed events; also, the PowerBook button device will be enabled so you can change the screen brightness. # Choice: ppc8xxtype Embedded 8xx Board Type CONFIG_RPXLITE Single-board computers based around the PowerPC MPC8xx chips and intended for embedded applications. The following types are supported: RPX-Lite: Embedded Planet RPX Lite. PC104 form-factor SBC based on the MPC823. RPX-Classic: Embedded Planet RPX Classic Low-fat. Credit-card-size SBC based on the MPC 860 BSE-IP: Bright Star Engineering ip-Engine. 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: - starter kit: - images: FPS850L: FingerPrint Sensor System (based on TQM850L) Manufacturer: IKENDI AG, 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, Date of Release: Mid 2000 (?) End of life: - URL: 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, Date of Release: December 2000 (?) End of life: - URL: IVML24: MPC860 based board used in the "Integrated Voice Mail System", Large Version (24 voice channels) Manufacturer: Speech Design, Date of Release: March 2001 (?) End of life: - URL: SM850: Service Module (based on TQM850L) Manufacturer: Dependable Computer Systems, Date of Release: end 2000 (?) End of life: mid 2001 (?) URL: HERMES_PRO: Hermes-Pro ISDN/LAN router with integrated 8 x hub Manufacturer: Multidata Gesellschaft für Datentechnik und Informatik Date of Release: 2000 (?) End of life: - URL: IP860: VMEBus IP (Industry Pack) carrier board with MPC860 Manufacturer: MicroSys GmbH, Date of Release: ? End of life: - URL: PCU_E: PCU = Peripheral Controller Unit, Extended Manufacturer: Siemens AG, ICN (Information and Communication Networks) Date of Release: April 2001 End of life: August 2001 URL: n. a. RPX-Classic CONFIG_RPXCLASSIC The RPX-Classic is a single-board computer based on the Motorola MPC860. It features 16MB of DRAM and a variable amount of flash, I2C EEPROM, thermal monitoring, a PCMCIA slot, a DIP switch and two LEDs. Variants with Ethernet ports exist. Say Y here to support it directly. BSE-IP CONFIG_BSEIP Say Y here to support the Bright Star Engineering ipEngine SBC. This is a credit-card-sized device featuring a MPC823 processor, 26MB DRAM, 4MB flash, Ethernet, a 16K-gate FPGA, USB, an LCD/video controller, and two RS232 ports. TQM823L CONFIG_TQM823L Say Y here to support the TQM823L, one of an MPC8xx-based family of mini SBCs (half credit-card size) from TQ Components first released in late 1999. Technical references are at , and , and an image at . TQM850L CONFIG_TQM850L Say Y here to support the TQM850L, one of an MPC8xx-based family of mini SBCs (half credit-card size) from TQ Components first released in late 1999. Technical references are at , and , and an image at . TQM855L CONFIG_TQM855L Say Y here to support the TQM855L, one of an MPC8xx-based family of mini SBCs (half credit-card size) from TQ Components first released in late 1999. Technical references are at , and , and an image at . TQM860L CONFIG_TQM860L Say Y here to support the TQM860L, one of an MPC8xx-based family of mini SBCs (half credit-card size) from TQ Components first released in late 1999. Technical references are at , and , and an image at . FPS850 CONFIG_FPS850 Say Y here to support the FingerPrint Sensor from AKENDI IG, based on the TQ Components TQM850L module, released November 1999 and discontinued a year later. TQM860 CONFIG_TQM860 Say Y here to support the TQM860, one of an MPC8xx-based family of SBCs (credit-card size) from TQ Components first released in mid-1999 and discontinued mid-2000. SM850 CONFIG_SM850 Say Y here to support the Service Module 850 from Dependable Computer Systems, an SBC based on the TQM850L module by TQ Components. This board is no longer in production. The manufacturer's website is at . SPD823TS CONFIG_SPD823TS Say Y here to support the Speech Design 823 Tele-Server from Speech Design, released in 2000. The manufacturer's website is at . IVMS8 CONFIG_IVMS8 Say Y here to support the Integrated Voice-Mail Small 8-channel SBC from Speech Design, released March 2001. The manufacturer's website is at . # IVML24 is not yet active IVML24 CONFIG_IVML24 Say Y here to support the Integrated Voice-Mail Large 24-channel SBC from Speech Design, released March 2001. The manufacturer's website is at . MBX CONFIG_MBX MBX is a line of Motorola single-board computer based around the MPC821 and MPC860 processors, and intended for embedded-controller applications. Say Y here to support these boards directly. WinCept CONFIG_WINCEPT The Wincept 100/110 is a Motorola single-board computer based on the MPC821 PowerPC, introduced in 1998 and designed to be used in thin-client machines. Say Y to support it directly. # More systems that will be supported soon, according to # Wolfgang Denk : # # TQM8260: # MPC8260 based module # # Manufacturer: TQ Components, www.tq-group.de # Date of Release: June 2001 # End of Life: not yet :-) # URL: # # IP860: # VMEBus IP (Industry Pack) carrier board with MPC860 # # Manufacturer: MicroSys GmbH, # Date of Release: ? # End of life: - # URL: # # CU824: # VMEBus Board with PCI extension with MPC8240 CPU # # Manufacturer: MicroSys GmbH, # Date of Release: early 2001 (?) # End of life: - # URL: # # PM826: # Modular system with MPC8260 CPU # # Manufacturer: MicroSys GmbH, # Date of Release: mid 2001 # End of life: - # URL: # # PCU_E: # PCU = Peripheral Controller Unit; E = extended (?) # # Mfr: Siemens AG, ICN (Information and Communication Networks) # # Date of Release: April 2001 # End of life: - # URL: n. a.o # Choice: ppc82xxtype Embedded 82xx Board Type CONFIG_EST8260 EST8260: The EST8260 is a single-board computer manufactured by Wind River Systems, Inc. (formerly Embedded Support Tools Corp.) and based on the MPC8260. Wind River Systems has a website at , but the EST8260 cannot be found on it and has probably been discontinued or rebadged. 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: PM826: Modular system with MPC8260 CPU Manufacturer: MicroSys GmbH, Date of Release: mid 2001 End of life: - URL: CU824: VMEBus Board with PCI extension with MPC8240 CPU Manufacturer: MicroSys GmbH, Date of Release: early 2001 (?) End of life: - URL: ADB raw keycode support CONFIG_MAC_ADBKEYCODES This provides support for sending raw ADB keycodes to console devices. This is the default up to 2.4.0, but in future this may be phased out in favor of generic Linux keycodes. If you say Y here, you can dynamically switch via the /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes sysctl and with the "keyboard_sends_linux_keycodes=" kernel argument. If unsure, say Y here. I2C/SPI 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. Mouse button 2+3 emulation support CONFIG_MAC_EMUMOUSEBTN This provides generic support for emulating the 2nd and 3rd mouse button with keypresses. If you say Y here, the emulation is still disabled by default. The emulation is controlled by these sysctl entries: /proc/sys/dev/mac_hid/mouse_button_emulation /proc/sys/dev/mac_hid/mouse_button2_keycode /proc/sys/dev/mac_hid/mouse_button3_keycode Enhanced Real Time Clock Support (/dev/rtc) CONFIG_PPC_RTC If you say Y here and create a character special file /dev/rtc with major number 10 and minor number 135 using mknod ("man mknod"), you will get access to the real time clock (or hardware clock) built into your computer. If unsure, say Y here. Support for Open Firmware device tree in /proc CONFIG_PROC_DEVICETREE This option adds a device-tree directory under /proc which contains an image of the device tree that the kernel copies from Open Firmware. If unsure, say Y here. RTAS (RunTime Abstraction Services) in /proc CONFIG_PPC_RTAS When you use this option, you will be able to use RTAS from userspace. RTAS stands for RunTime Abstraction Services and should provide a portable way to access and set system information. This is commonly used on RS/6000 (pSeries) computers. You can access RTAS via the special proc file system entry rtas. Don't confuse this rtas entry with the one in /proc/device-tree/rtas which is readonly. If you don't know if you can use RTAS look into /proc/device-tree/rtas. If there are some entries, it is very likely that you will be able to use RTAS. You can do cool things with rtas. To print out information about various sensors in the system, just do a $ cat /proc/rtas/sensors or if you power off your machine at night but want it running when you enter your office at 7:45 am, do a # date -d 'tomorrow 7:30' +%s > /proc/rtas/poweron and shutdown. If unsure, say Y. MESH (Power Mac internal SCSI) support CONFIG_SCSI_MESH Many Power Macintoshes and clones have a MESH (Macintosh Enhanced SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the other Power Macintoshes do). Say Y to include support for this SCSI adaptor. This driver is also available as a module called mesh.o ( = 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 . Maximum synchronous transfer rate (MB/s) (0 = async) CONFIG_SCSI_MESH_SYNC_RATE On Power Macintoshes (and clones) where the MESH SCSI bus adaptor drives a bus which is entirely internal to the machine (such as the 7500, 7600, 8500, etc.), the MESH is capable of synchronous operation at up to 10 MB/s. On machines where the SCSI bus controlled by the MESH can have external devices connected, it is usually rated at 5 MB/s. 5 is a safe value here unless you know the MESH SCSI bus is internal only; in that case you can say 10. Say 0 to disable synchronous operation. 53C94 (Power Mac external SCSI) support CONFIG_SCSI_MAC53C94 On Power Macintoshes (and clones) with two SCSI buses, the external SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older machines which only have one SCSI bus, such as the 7200, also use the 53C94. Say Y to include support for the 53C94. This driver is also available as a module called mac53c94.o ( = 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 . MACE (Power Mac Ethernet) support CONFIG_MACE Power Macintoshes and clones with Ethernet built-in on the motherboard will usually use a MACE (Medium Access Control for Ethernet) interface. Say Y to include support for the MACE chip. This driver is also available as a module called mace.o ( = 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 . Use AAUI port instead of TP by default CONFIG_MACE_AAUI_PORT Some Apple machines (notably the Apple Network Server) which use the MACE ethernet chip have an Apple AUI port (small 15-pin connector), instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say Y here if you have such a machine. If unsure, say N. The driver will default to AAUI on ANS anyway, and if you use it as a module, you can provide the port_aaui=0|1 to force the driver. BMAC (G3 Ethernet) support CONFIG_BMAC Say Y for support of BMAC Ethernet interfaces. These are used on G3 computers. This driver is also available as a module called bmac.o ( = 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 . GMAC (G4/iBook Ethernet) support CONFIG_GMAC Say Y for support of GMAC Ethernet interfaces. These are used on G4 and iBook computers. This driver is also available as a module called gmac.o ( = 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 . National DP83902AV (Oak Ethernet) support CONFIG_OAKNET Say Y if your machine has this type of Ethernet network card. This driver is also available as a module called oaknet.o ( = 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 . Video For Linux CONFIG_VIDEO_DEV Support for audio/video capture and overlay devices and FM radio cards. The exact capabilities of each device vary. User tools for this are available from . If you are interested in writing a driver for such an audio/video device or user software interacting with such a driver, please read the file . This driver is also available as a module called videodev.o ( = 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 . Video For Linux /proc file system information CONFIG_VIDEO_PROC_FS If you say Y here, you are able to access video device information in /proc/video. To use this option, you have to check, that the "/proc file system support" (CONFIG_PROC_FS) is enabled too. AIMSlab RadioTrack (aka RadioReveal) support CONFIG_RADIO_RTRACK Choose Y here if you have one of these FM radio cards, and then fill in the port address below. Note that newer AIMSlab RadioTrack cards have a different chipset and are not supported by this driver. For these cards, use the RadioTrack II driver below. If you have a GemTeks combined (PnP) sound- and radio card you must use this driver as a module and setup the card with isapnptools. You must also pass the module a suitable io parameter, 0x248 has been reported to be used by these cards. In order to control your radio card, you will need to use programs that are compatible with the Video For Linux API. Information on this API and pointers to "v4l" programs may be found on the WWW at . More information is contained in the file . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called radio-aimslab.o. RadioTrack I/O port CONFIG_RADIO_RTRACK_PORT Enter either 0x30f or 0x20f here. The card default is 0x30f, if you haven't changed the jumper setting on the card. AIMSlab RadioTrack II support CONFIG_RADIO_RTRACK2 Choose Y here if you have this FM radio card, and then fill in the port address below. In order to control your radio card, you will need to use programs that are compatible with the Video For Linux API. Information on this API and pointers to "v4l" programs may be found on the WWW at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called radio-rtrack2.o. RadioTrack II I/O port CONFIG_RADIO_RTRACK2_PORT Enter either 0x30c or 0x20c here. The card default is 0x30c, if you haven't changed the jumper setting on the card. Aztech/Packard Bell Radio CONFIG_RADIO_AZTECH Choose Y here if you have one of these FM radio cards, and then fill in the port address below. In order to control your radio card, you will need to use programs that are compatible with the Video For Linux API. Information on this API and pointers to "v4l" programs may be found on the WWW at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called radio-aztech.o. Aztech/Packard Bell radio card I/O port CONFIG_RADIO_AZTECH_PORT Enter either 0x350 or 0x358 here. The card default is 0x350, if you haven't changed the setting of jumper JP3 on the card. Removing the jumper sets the card to 0x358. ADS Cadet AM/FM Radio Tuner Card CONFIG_RADIO_CADET Choose Y here if you have one of these AM/FM radio cards, and then fill in the port address below. In order to control your radio card, you will need to use programs that are compatible with the Video For Linux API. Information on this API and pointers to "v4l" programs may be found on the WWW at . Further documentation on this driver can be found on the WWW at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called radio-cadet.o. SF16FMI Radio CONFIG_RADIO_SF16FMI Choose Y here if you have one of these FM radio cards. If you compile the driver into the kernel and your card is not PnP one, you have to add "sf16fm=" to the kernel command line (I/O address is 0x284 or 0x384). In order to control your radio card, you will need to use programs that are compatible with the Video For Linux API. Information on this API and pointers to "v4l" programs may be found on the WWW at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called radio-sf16fmi.o. Typhoon Radio (a.k.a. EcoRadio) CONFIG_RADIO_TYPHOON Choose Y here if you have one of these FM radio cards, and then fill in the port address and the frequency used for muting below. In order to control your radio card, you will need to use programs that are compatible with the Video For Linux API. Information on this API and pointers to "v4l" programs may be found on the WWW at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called radio-typhoon.o. Support for /proc/radio-typhoon CONFIG_RADIO_TYPHOON_PROC_FS Say Y here if you want the typhoon radio card driver to write status information (frequency, volume, muted, mute frequency, base address) to /proc/radio-typhoon. The file can be viewed with your favorite pager (i.e. use "more /proc/radio-typhoon" or "less /proc/radio-typhoon" or simply "cat /proc/radio-typhoon"). Typhoon I/O port (0x316 or 0x336) CONFIG_RADIO_TYPHOON_PORT Enter the I/O port of your Typhoon or EcoRadio radio card. Typhoon frequency set when muting the device (kHz) CONFIG_RADIO_TYPHOON_MUTEFREQ Enter the frequency used for muting the radio. The device is never completely silent. If the volume is just turned down, you can still hear silent voices and music. For that reason, the frequency of the radio device is set to the frequency you can enter here whenever the device is muted. There should be no local radio station at that frequency. Zoltrix Radio CONFIG_RADIO_ZOLTRIX Choose Y here if you have one of these FM radio cards, and then fill in the port address below. In order to control your radio card, you will need to use programs that are compatible with the Video For Linux API. Information on this API and pointers to "v4l" programs may be found on the WWW at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called radio-zoltrix.o. ZOLTRIX I/O port (0x20c or 0x30c) CONFIG_RADIO_ZOLTRIX_PORT Enter the I/O port of your Zoltrix radio card. I2C on parallel port CONFIG_I2C_PARPORT I2C is a simple serial bus system used in many micro controller applications. Saying Y here will allow you to use your parallel port as an I2C interface. If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called i2c-parport.o. miroSOUND PCM20 radio CONFIG_RADIO_MIROPCM20 Choose Y here if you have this FM radio card. You also need to say Y to "ACI mixer (miroSOUND PCM1-pro/PCM12/PCM20 radio)" (in "Sound") for this to work. In order to control your radio card, you will need to use programs that are compatible with the Video For Linux API. Information on this API and pointers to "v4l" programs may be found on the WWW at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called miropcm20.o. miroSOUND PCM20 radio RDS user interface (EXPERIMENTAL) CONFIG_RADIO_MIROPCM20_RDS Choose Y here if you want to see RDS/RBDS information like RadioText, Programme Service name, Clock Time and date, Programme TYpe and Traffic Announcement/Programme identification. You also need to say Y to "miroSOUND PCM20 radio" and devfs! It's not possible to read the raw RDS packets from the device, so the driver cant provide an V4L interface for this. But the availability of RDS is reported over V4L by the basic driver already. Here RDS can be read from files in /dev/v4l/rds. As module the driver will be called miropcm20-rds.o. Maestro on board radio CONFIG_RADIO_MAESTRO Say Y here to directly support the on-board radio tuner on the Maestro 2 or 2E sound card. In order to control your radio card, you will need to use programs that are compatible with the Video For Linux API. Information on this API and pointers to "v4l" programs may be found on the WWW at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called radio-maestro.o. Guillemot MAXI Radio FM 2000 Radio Card CONFIG_RADIO_MAXIRADIO Choose Y here if you have this radio card. This card may also be found as GemTek PCI FM. In order to control your radio card, you will need to use programs that are compatible with the Video For Linux API. Information on this API and pointers to "v4l" programs may be found on the WWW at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called radio-maxiradio.o. GemTek Radio Card support CONFIG_RADIO_GEMTEK Choose Y here if you have this FM radio card, and then fill in the port address below. In order to control your radio card, you will need to use programs that are compatible with the Video For Linux API. Information on this API and pointers to "v4l" programs may be found on the WWW at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called radio-gemtek.o. GemTek I/O port CONFIG_RADIO_GEMTEK_PORT Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is 0x34c, if you haven't changed the jumper setting on the card. On Sound Vision 16 Gold PnP with FM Radio (ESS1869+FM GemTek), the I/O port is 0x28c. GemTek PCI Radio Card support CONFIG_RADIO_GEMTEK_PCI Choose Y here if you have this PCI FM radio card. In order to control your radio card, you will need to use programs that are compatible with the Video for Linux API. Information on this API and pointers to "v4l" programs may be found on the WWW at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called radio-gemtek-pci.o. PlanB Video-In for PowerMacs CONFIG_VIDEO_PLANB PlanB is the V4L driver for the PowerMac 7x00/8x00 series video input hardware. If you want to experiment with this, say Y. Otherwise, or if you don't understand a word, say N. See for more info. Saying M will compile this driver as a module (planb.o). TerraTec ActiveRadio CONFIG_RADIO_TERRATEC Choose Y here if you have this FM radio card, and then fill in the port address below. (TODO) Note: This driver is in its early stages. Right now volume and frequency control and muting works at least for me, but unfortunately I have not found anybody who wants to use this card with Linux. So if it is this what YOU are trying to do right now, PLEASE DROP ME A NOTE!! Rolf Offermanns (rolf@offermanns.de) In order to control your radio card, you will need to use programs that are compatible with the Video For Linux API. Information on this API and pointers to "v4l" programs may be found on the WWW at . If you want to compile this driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called radio-terratec.o. Terratec I/O port (normally 0x590) CONFIG_RADIO_TERRATEC_PORT Fill in the I/O port of your TerraTec FM radio card. If unsure, go with the default. Trust FM radio card CONFIG_RADIO_TRUST This is a driver for the Trust FM radio cards. Say Y if you have such a card and want to use it under Linux. This driver is also available as a module called radio-trust.o ( = 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 . Trust I/O port (usually 0x350 or 0x358) CONFIG_RADIO_TRUST_PORT Enter the I/O port of your Trust FM radio card. If unsure, try the values "0x350" or "0x358". BT848 Video For Linux CONFIG_VIDEO_BT848 Support for BT848 based frame grabber/overlay boards. This includes the Miro, Hauppauge and STB boards. Please read the material in for more information. If you say Y or M here, you need to say Y or M to "I2C support" and "I2C bit-banging interfaces" in the character device section. This driver is available as a module called bttv.o ( = 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 . BT878 audio DMA CONFIG_SOUND_BT878 Audio DMA support for bt878 based grabber boards. As you might have already noticed, bt878 is listed with two functions in /proc/pci. Function 0 does the video stuff (bt848 compatible), function 1 does the same for audio data. This is a driver for the audio part of the chip. If you say 'Y' here you get a oss-compatible dsp device where you can record from. If you want just watch TV you probably don't need this driver as most TV cards handle sound with a short cable from the TV card to your sound card's line-in. This driver is available as a module called btaudio.o ( = 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 . SGI Vino Video For Linux CONFIG_VIDEO_VINO Say Y here to build in support for the Vino video input system found on SGI Indy machines. Stradis 4:2:2 MPEG-2 video driver CONFIG_VIDEO_STRADIS Say Y here to enable support for the Stradis 4:2:2 MPEG-2 video driver for PCI. There is a product page at . Zoran ZR36057/36060 Video For Linux CONFIG_VIDEO_ZORAN Say Y here to include support for video cards based on the Zoran ZR36057/36060 encoder/decoder chip (including the Iomega Buz and the Miro DC10 and DC30 video capture cards). Include support for Iomega Buz CONFIG_VIDEO_ZORAN_BUZ Say Y here to include support for the Iomega Buz video card. There is a Buz/Linux homepage at . Miro DC10(+) support CONFIG_VIDEO_ZORAN_DC10 Say Y to support the Pinnacle Systems Studio DC10 plus TV/Video card. Linux page at . Vendor page at . Linux Media Labs LML33 support CONFIG_VIDEO_ZORAN_LML33 Say Y here to support the Linux Media Labs LML33 TV/Video card. Resources page is at . Zoran ZR36120/36125 Video For Linux CONFIG_VIDEO_ZR36120 Support for ZR36120/ZR36125 based frame grabber/overlay boards. This includes the Victor II, WaveWatcher, Video Wonder, Maxi-TV, and Buster boards. Please read the material in for more information. This driver is also available as a module called zr36120.o ( = 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 . SAA5249 Teletext processor CONFIG_VIDEO_SAA5249 Support for I2C bus based teletext using the SAA5249 chip. At the moment this is only useful on some European WinTV cards. This driver is also available as a module called saa5249.o ( = 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 . QuickCam BW Video For Linux CONFIG_VIDEO_BWQCAM Say Y have if you the black and white version of the QuickCam camera. See the next option for the color version. This driver is also available as a module called bw-qcam.o ( = 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 . QuickCam Colour Video For Linux CONFIG_VIDEO_CQCAM This is the video4linux driver for the colour version of the Connectix QuickCam. If you have one of these cameras, say Y here, otherwise say N. This driver does not work with the original monochrome QuickCam, QuickCam VC or QuickClip. It is also available as a module (c-qcam.o). Read for more information. W9966 Webcam (FlyCam Supra and others) Video For Linux CONFIG_VIDEO_W9966 Video4linux driver for Winbond's w9966 based Webcams. Currently tested with the LifeView FlyCam Supra. If you have one of these cameras, say Y here otherwise say N. This driver is also available as a module (w9966.o). Check out and for more information. CPiA Video For Linux CONFIG_VIDEO_CPIA This is the video4linux driver for cameras based on Vision's CPiA (Colour Processor Interface ASIC), such as the Creative Labs Video Blaster Webcam II. If you have one of these cameras, say Y here and select parallel port and/or USB lowlevel support below, otherwise say N. This will not work with the Creative Webcam III. Please read for more information. This driver is also available as a module (cpia.o). CPiA Parallel Port Lowlevel Support CONFIG_VIDEO_CPIA_PP This is the lowlevel parallel port support for cameras based on Vision's CPiA (Colour Processor Interface ASIC), such as the Creative Webcam II. If you have the parallel port version of one of these cameras, say Y here, otherwise say N. It is also available as a module (cpia_pp.o). CPiA USB Lowlevel Support CONFIG_VIDEO_CPIA_USB This is the lowlevel USB support for cameras based on Vision's CPiA (Colour Processor Interface ASIC), such as the Creative Webcam II. If you have the USB version of one of these cameras, say Y here, otherwise say N. This will not work with the Creative Webcam III. It is also available as a module (cpia_usb.o). Mediavision Pro Movie Studio Video For Linux CONFIG_VIDEO_PMS Say Y if you have such a thing. This driver is also available as a module called pms.o ( = 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 . Sony Vaio Picturebook Motion Eye Video For Linux CONFIG_VIDEO_MEYE This is the video4linux driver for the Motion Eye camera found in the Vaio Picturebook laptops. Please read the material in for more information. If you say Y or M here, you need to say Y or M to "Sony Programmable I/O Control Device" in the character device section. This driver is available as a module called meye.o ( = 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 . IBM's S/390 architecture CONFIG_ARCH_S390 Select this option, if you want to run the Kernel on one of IBM's mainframes of the S/390 generation. You should have installed the s390-compiler released by IBM (based on gcc-2.95.1) before. Merge some code into the kernel to make the image IPLable CONFIG_IPL If you want to use the produced kernel to IPL directly from a device, you have to merge a bootsector specific to the device into the first bytes of the kernel. You will have to select the IPL device on another question, that pops up, when you select CONFIG_IPL. IPL from a S/390 tape unit CONFIG_IPL_TAPE Select this option if you want to IPL the image from a Tape. IPL from a virtual card reader emulated by VM/ESA CONFIG_IPL_VM Select this option if you are running under VM/ESA and want to IPL the image from the emulated card reader. CONFIG_PFAULT Select this option, if you want to use PFAULT pseudo page fault handling under VM. If running native or in LPAR, this option has no effect. If your VM does not support PFAULT, PAGEEX pseudo page fault handling will be used. Note that VM 4.2 supports PFAULT but has a bug in its implementation that causes some problems. Everybody who wants to run Linux under VM != VM4.2 should select this option. CONFIG_SHARED_KERNEL Select this option, if you want to share the text segment of the Linux kernel between different VM guests. This reduces memory usage with lots of guests but greatly increases kernel size. You should only select this option if you know what you are doing and want to exploit this feature. Support for IBM-style disk-labels (S/390) CONFIG_S390_PARTITION Enable this option to assure standard IBM labels on the DASDs. You must enable it, if you are planning to access DASDs also attached to another IBM mainframe operation system (OS/390, VM/ESA, VSE/ESA). Support for DASD hard disks CONFIG_DASD Enable this option if you want to access DASDs directly utilizing S/390s channel subsystem commands. This is necessary for running natively on a single image or an LPAR. Support for ECKD hard disks CONFIG_DASD_ECKD ECKD (Extended Count Key Data) devices are the most commonly used devices on S/390s. You should enable this option unless you are very sure you have no ECKD device. ECKD demand loading CONFIG_DASD_AUTO_ECKD This option enables demand loading of the ECKD module. Support for FBA hard disks CONFIG_DASD_FBA Select this option if you want to use FBA (Fixed Block) devices. If you are not sure what it is, say "Y". FBA demand loading CONFIG_DASD_AUTO_FBA This option enables demand loading of the FBA module. Support for DIAG access to CMS reserved Disks CONFIG_DASD_DIAG Select this option if you want to use CMS reserved Disks under VM with the Diagnose250 command. If you are not running under VM or unsure what it is, say "N". DIAG demand loading CONFIG_DASD_AUTO_DIAG This option enables demand loading of the DIAG module. Merge some code into the kernel to make the image IPLable CONFIG_IPLABLE If you want to use the produced kernel to IPL directly from a device, you have to merge a bootsector specific to the device into the first bytes of the kernel. You will have to select the IPL device on another question, that pops up, when you select CONFIG_IPLABE. Support for 3215 line mode terminal CONFIG_TN3215 Include support for IBM 3215 line-mode terminals. Support for console on 3215 line mode terminal CONFIG_TN3215_CONSOLE Include support for using an IBM 3215 line-mode terminal as a Linux system console. Support for 3270 line mode terminal CONFIG_TN3270 Include support for IBM 3270 line-mode terminals. Support for console on 3270 line mode terminal CONFIG_TN3270_CONSOLE Include support for using an IBM 3270 line-mode terminal as a Linux system console. Available only if 3270 support is compiled in statically. Support for HWC line mode terminal CONFIG_HWC Include support for IBM HWC line-mode terminals. Console on HWC line mode terminal CONFIG_HWC_CONSOLE Include support for using an IBM HWC line-mode terminal as the Linux system console. Control Program Identification CONFIG_HWC_CPI Allows for Control Program Identification via the HWC interface, i.e. provides a mean to pass an OS instance name (system name) to the machine. This option should only be selected as a module since the system name has to be passed as module parameter. The module will be called hwc_cpi.o. S/390 tape device support CONFIG_S390_TAPE Select this option if you want to access channel-attached tape devices on IBM S/390 or zSeries. If you select this option you will also want to select at least one of the tape interface options and one of the tape hardware options in order to access a tape device. This option is also available as a module. The module will be called tape390.o and include all selected interfaces. The hardware drivers will be seperate modules. If unsure, say "Y". Support for tape character devices CONFIG_S390_TAPE_CHAR Select this option if you want to access your channel-attached tape devices using the character device interface. This interface is similar to other Linux tape devices like SCSI-Tapes (st) and the floppy tape device (ftape). If unsure, say "Y". Support for tape block devices CONFIG_S390_TAPE_BLOCK Select this option if you want to access your channel-attached tape devices using the block device interface. This interface is similar to CD-ROM devices on other platforms. The tapes can only be accessed read-only when using this interface. Have a look at Documentation/s390/TAPE for further information about creating volumes for and using this interface. It is safe to say "Y" here. Support for 3490 tape hardware CONFIG_S390_TAPE_3490 Select this option if you want to access IBM 3490 magnetic tape subsystems and 100% compatibles. This option is also available as a module. The module will be called tape3490.o. If CONFIG_S390_TAPE is selected as a module, this hardware driver cannot be built-in but is only available as a module. It is safe to say "Y" here. Support for 3480 tape hardware CONFIG_S390_TAPE_3480 Select this option if you want to access IBM 3480 magnetic tape subsystems and 100% compatibles. This option is also available as a module. The module will be called tape3480.o. If CONFIG_S390_TAPE is selected as a module, this hardware driver cannot be built-in but is only available as a module. It is safe to say "Y" here. CTC device support CONFIG_CTC Select this option if you want to use channel-to-channel networking on IBM S/390 or zSeries. This device driver supports real CTC coupling using ESCON. It also supports virtual CTCs when running under VM. It will use the channel device configuration if this is available. This option is also available as a module which will be called ctc.o. If you do not know what it is, it's safe to say "Y". XPRAM disk support CONFIG_BLK_DEV_XPRAM Select this option if you want to use your expanded storage on S/390 or zSeries as a disk. This is useful as a _fast_ swap device if you want to access more than 2G of memory when running in 31 bit mode. This option is also available as a module which will be called xpram.o. If unsure, say "N". Fast IRQ handling CONFIG_FAST_IRQ Select this option in order to get the interrupts processed faster on your S/390 or zSeries machine. If selected, after an interrupt is processed, the channel subsystem will be asked for other pending interrupts which will also be processed before leaving the interrupt context. This speeds up the I/O a lot. Say "Y". IUCV device support (VM only) CONFIG_IUCV Select this option if you want to use inter-user communication vehicle networking under VM or VIF. This option is also available as a module which will be called iucv.o. If unsure, say "Y". Process warning machine checks CONFIG_MACHCHK_WARNING Select this option if you want the machine check handler on IBM S/390 or zSeries to process warning machine checks (e.g. on power failures). If unsure, say "Y". Use chscs for Common I/O CONFIG_CHSC Select this option if you want the s390 common I/O layer to use information obtained by channel subsystem calls. This will enable Linux to process link failures and resource accessibility events. Moreover, if you have procfs enabled, you'll be able to toggle chpids logically offline and online. Even if you don't understand what this means, you should say "Y". Kernel support for 31 bit ELF binaries CONFIG_S390_SUPPORT Select this option if you want to enable your system kernel to handle system-calls from ELF binaries for 31 bit ESA. This option (and some other stuff like libraries and such) is needed for executing 31 bit applications. It is safe to say "Y". Channel Device Configuration CONFIG_CHANDEV The channel device layer is a layer to provide a consistent interface for configuration & default machine check (devices appearing & disappearing) handling on Linux for s/390 & z/Series channel devices. s/390 & z/Series channel devices include among others lcs (the most common ethernet/token ring/fddi standard on zSeries) ctc/escon hi speed like serial link standard on zSeries claw used to talk to cisco routers. qeth gigabit ethernet. These devices use two channels one read & one write for configuration & communication (& a third channel, the data channel the case of gigabit ethernet). The motivation behind developing this layer was that there was a lot of duplicate code among the channel device drivers for configuration. Also the lcs & ctc drivers tended to fight over 3088/08's & 3088/1F's which could be either 2216/3172 channel attached lcs compatible devices or escon/ctc pipes had to be configured separately as they couldn't autodetect, this is now simplified by doing the configuration in a single place (the channel device layer). This layer isn't invasive & it is quite okay to use channel drivers which don't use the channel device layer in conjunction with drivers which do. For more info see the chandev manpage usually distributed in in the Linux source tree. SAB3036 tuner support CONFIG_TUNER_3036 Say Y here to include support for Philips SAB3036 compatible tuners. If in doubt, say N. Compaq SMART2 support CONFIG_BLK_CPQ_DA This is the driver for Compaq Smart Array controllers. Everyone using these boards should say Y here. See the file for the current list of boards supported by this driver, and for further information on the use of this driver. 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 . The module will be called cpqarray.o Show crashed user process info CONFIG_PROCESS_DEBUG Say Y to print all process fault locations to the console. This is a debugging option; you probably do not want to set it unless you are an S390 port maintainer. # # ARM options # # CML2 transition note: CML1 asks ARCH_ARCA5K, then has ARCH_A5K and ARCH_ARK # as subquestions. CML2 asks the subquestions in the armtype menu and makes # ARCH_ARCA5K a derived symbol. ARM System type CONFIG_ARCH_ARCA5K This selects what ARM system you wish to build the kernel for. It also selects to some extent the CPU type. If you are unsure what to set this option to, please consult any information supplied with your system. # Choice: armtype A5000 CONFIG_ARCH_A5K Say Y here to to support the Acorn A5000. Linux can support the internal IDE disk and CD-ROM interface, serial and parallel port, and the floppy drive. Note that on some A5000s the floppy is plugged into the wrong socket on the motherboard. Archimedes CONFIG_ARCH_ARC The Acorn Archimedes was an personal computer based on an 8K ARM2 processor, released in 1987. It supported 512K of RAM and 2 800K floppy disks. Picture and more detailed specifications at . EBSA-110 CONFIG_ARCH_EBSA110 This is an evaluation board for the StrongARM processor available from Digital. It has limited hardware on-board, including an onboard Ethernet interface, two PCMCIA sockets, two serial ports and a parallel port. RiscPC CONFIG_ARCH_RPC On the Acorn Risc-PC, Linux can support the internal IDE disk and CD-ROM interface, serial and parallel port, and the floppy drive. 2MB physical memory CONFIG_PAGESIZE_16 Say Y here if your Archimedes or A5000 system has only 2MB of memory, otherwise say N. The resulting kernel will not run on a machine with 4MB of memory. CATS CONFIG_ARCH_CATS Say Y here if you intend to run this kernel on the CATS. Saying N will reduce the size of the Footbridge kernel. EBSA285 (addin mode) CONFIG_ARCH_EBSA285_ADDIN Say Y here if you intend to run this kernel on the EBSA285 card in addin mode. Saying N will reduce the size of the Footbridge kernel. EBSA285 (host mode) CONFIG_ARCH_EBSA285_HOST Say Y here if you intend to run this kernel on the EBSA285 card in host ("central function") mode. Saying N will reduce the size of the Footbridge kernel. LinkUp Systems L7200 SDB CONFIG_ARCH_L7200 Say Y here if you intend to run this kernel on a LinkUp Systems L7200 Software Development Board which uses an ARM720T processor. Information on this board can be obtained at: If you have any questions or comments about the Linux kernel port to this board, send e-mail to sjhill@cotw.com. NetWinder CONFIG_ARCH_NETWINDER Say Y here if you intend to run this kernel on the Rebel.COM NetWinder. Information about this machine can be found at: Saying N will reduce the size of the Footbridge kernel. P720T CONFIG_ARCH_P720T Say Y here if you intend to run this kernel on the ARM Prospector 720T. Compaq Personal Server CONFIG_ARCH_PERSONAL_SERVER Say Y here if you intend to run this kernel on the Compaq Personal Server. Saying N will reduce the size of the Footbridge kernel. The Compaq Personal Server is not available for purchase. There are no product plans beyond the current research prototypes at this time. Information is available at: If you have any questions or comments about the Compaq Personal Server, send e-mail to skiff@crl.dec.com. Cirrus Logic EDB-7211 evaluation board CONFIG_ARCH_EDB7211 Say Y here if you intend to run this kernel on a Cirrus Logic EDB-7211 evaluation board. EP7211 infrared support CONFIG_EP7211_IR Say Y here if you wish to use the infrared port on the EP7211. Note that you can't use the first UART and the infrared port at the same time, and that the EP7211 only supports SIR mode, at speeds up to 115.2 kbps. To use the I/R port, you will need to get the source to irda-utils and apply the patch at . Assabet CONFIG_SA1100_ASSABET Say Y here if you are using the Intel(R) StrongARM(R) SA-1110 Microprocessor Development Board (also known as the Assabet). Neponset CONFIG_ASSABET_NEPONSET Say Y here if you are using the Intel(R) StrongARM(R) SA-1110 Microprocessor Development Board (Assabet) with the SA-1111 Development Board (Nepon). Compaq iPAQ H3600 CONFIG_SA1100_H3600 Say Y here if you intend to run this kernel on the Compaq iPAQ H3600 handheld computer. Information about this machine and the Linux port to this machine can be found at: Brutus CONFIG_SA1100_BRUTUS Say Y here if you are using the Intel(R) StrongARM(R) SA-1100 Microprocessor Development Board (also known as the Brutus). LART CONFIG_SA1100_LART Say Y here if you are using the Linux Advanced Radio Terminal (also known as the LART). See for information on the LART. GraphicsClient CONFIG_SA1100_GRAPHICSCLIENT Say Y here if you are using an Applied Data Systems Intel(R) StrongARM(R) SA-1100 based Graphics Client SBC. See for information on this system. GraphicsMaster CONFIG_SA1100_GRAPHICSMASTER Say Y here if you are using an Applied Data Systems Intel(R) StrongARM(R) SA-1100 based Graphics Master SBC with SA-1111 StrongARM companion chip. See for information on this system. ADSBitsy CONFIG_SA1100_ADSBITSY Say Y here if you are using Applied Data Systems Intel(R) StrongARM(R) 1110 based Bitsy, 3 x 5 inches in size, Compaq - IPAQ - like platform. See for more information. ITSY CONFIG_SA1100_ITSY Say Y here if you are using the Compaq Itsy experimental pocket computer. See for more information. PLEB CONFIG_SA1100_PLEB Say Y here if you are using a Portable Linux Embedded Board (also known as PLEB). See for more information. CerfBoard CONFIG_SA1100_CERF The Intrinsyc CerfBoard is based on the StrongARM 1110. More information is available at: . Say Y if configuring for an Intrinsyc CerfBoard. Say N otherwise. FlexaNet CONFIG_SA1100_FLEXANET Say Y here if you intend to run this kernel on the FlexaNet handheld instruments. Information about this machine can be found at: . nanoEngine CONFIG_SA1100_NANOENGINE The nanoEngine is a StrongARM 1110-based single board computer from Bright Star Engineering. More information is available at: . Say Y if configuring for a nanoEngine. Say N otherwise. Pangolin CONFIG_SA1100_PANGOLIN Pangolin is a StrongARM 1110-based evaluation platform produced by Dialogue Technology. It has EISA slots for ease of configuration with SDRAM/Flash memory card, USB/Serial/Audio card, Compact Flash card, and TFT-LCD card. Say Y if configuring for a Pangolin. Say N otherwise. Victor CONFIG_SA1100_VICTOR Say Y here if you are using a Visu Aide Intel(R) StrongARM(R) SA-1100 based Victor Digital Talking Book Reader. See for information on this system. # Choice: cerf_ram Cerf on-board RAM size CONFIG_SA1100_CERF_8MB Declare the size of the CerfBoard's on-board RAM. Alternatives are 8, 16, 32, and 64MB. 16MB CONFIG_SA1100_CERF_16MB Declare that the CerfBoard has 16MB RAM. 32MB CONFIG_SA1100_CERF_32MB Declare that the CerfBoard has 32MB RAM. 64MB CONFIG_SA1100_CERF_64MB Declare that the CerfBoard has 64MB RAM. # Choice: cerf_flash Cerf flash memory size CONFIG_SA1100_CERF_FLASH_8MB Tell the Cerf kernel the size of on-board memory. The choices are 8MB, 16MB, or 32MB. 16MB CONFIG_SA1100_CERF_FLASH_16MB Configure the Cerf kernel to expect 16MB of flash memory. 32MB CONFIG_SA1100_CERF_FLASH_32MB Configure the Cerf kernel to expect 32MB of flash memory. Support ARM610 processor CONFIG_CPU_ARM610 The ARM610 is the successor to the ARM3 processor and was produced by VLSI Technology Inc. Say Y if you want support for the ARM610 processor. Otherwise, say N. Support ARM710 processor CONFIG_CPU_ARM710 A 32-bit RISC microprocessor based on the ARM7 processor core designed by Advanced RISC Machines Ltd. The ARM710 is the successor to the ARM610 processor. It was released in July 1994 by VLSI Technology Inc. Say Y if you want support for the ARM710 processor. Otherwise, say N. Support ARM720T processor CONFIG_CPU_ARM720T A 32-bit RISC processor with 8kByte Cache, Write Buffer and MMU built around an ARM7TDMI core. Say Y if you want support for the ARM720T processor. Otherwise, say N. Support ARM920T processor CONFIG_CPU_ARM920T The ARM920T is licensed to be produced by numerous vendors, and is used in the Maverick EP9312. More information at . Say Y if you want support for the ARM920T processor. Otherwise, say N. Support ARM1020 processor CONFIG_CPU_ARM1020 The ARM1020 is the cached version of the ARM10 processor, with an addition of a floating-point unit. Say Y if you want support for the ARM1020 processor. Otherwise, say N. Support StrongARM SA-110 processor CONFIG_CPU_SA110 The Intel StrongARM(R) SA-110 is a 32-bit microprocessor and is available at five speeds ranging from 100 MHz to 233 MHz. More information is available at . Say Y if you want support for the SA-110 processor. Otherwise, say N. Tulsa CONFIG_SA1100_PFS168 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 this target. HP Jornada 720 CONFIG_SA1100_JORNADA720 Say Y here if you want to build a kernel for the HP Jornada 720 handheld computer. See for details. InHand Electronics OmniMeter CONFIG_SA1100_OMNIMETER Say Y here if you are using the inhand electronics OmniMeter. See for details. Load kernel using Angel Debug Monitor CONFIG_ANGELBOOT Say Y if you plan to load the kernel using Angel, ARM Ltd's target debug stub. If you are not using Angel, you must say N. It is important to get this setting correct. CDB89712 CONFIG_ARCH_CDB89712 This is an evaluation board from Cirrus for the CS89712 processor. The board includes 2 serial ports, Ethernet, IRDA, and expansion headers. It comes with 16 MB SDRAM and 8 MB flash ROM. CLPS-711X internal ROM bootstrap CONFIG_EP72XX_ROM_BOOT If you say Y here, your CLPS711x-based kernel will use the bootstrap mode memory map instead of the normal memory map. Processors derived from the Cirrus CLPS-711X core support two boot modes. Normal mode boots from the external memory device at CS0. Bootstrap mode rearranges parts of the memory map, placing an internal 128 byte bootstrap ROM at CS0. This option performs the address map changes required to support booting in this mode. You almost surely want to say N here. Math emulation CONFIG_FPE_NWFPE Say Y to include the NWFPE floating point emulator in the kernel. This is necessary to run most binaries. Linux does not currently support floating point hardware so you need to say Y here even if your machine has an FPA or floating point co-processor podule. It is also possible to say M to build the emulator as a module (nwfpe.o) or indeed to leave it out altogether. However, unless you know what you are doing this can easily render your machine unbootable. Saying Y is the safe option. You may say N here if you are going to load the Acorn FPEmulator early in the bootup. FastFPE math emulation CONFIG_FPE_FASTFPE Say Y here to include the FAST floating point emulator in the kernel. This is an experimental much faster emulator which has only 32 bit precision for the mantissa. It does not support any exceptions. This makes it very simple, it is approximately 4-8 times faster than NWFPE. It should be sufficient for most programs. It is definitely not suitable if you do scientific calculations that need double precision for iteration formulas that sum up lots of very small numbers. If you do not feel you need a faster FP emulation you should better choose NWFPE. It is also possible to say M to build the emulator as a module (fastfpe.o). But keep in mind that you should only load the FP emulator early in the bootup. You should never change from NWFPE to FASTFPE or vice versa in an active system! DS1620 thermometer support CONFIG_DS1620 Say Y here to include support for the thermal management hardware found in the NetWinder. This driver allows the user to control the temperature set points and to read the current temperature. It is also possible to say M here to build it as a module (ds1620.o) It is recommended to be used on a NetWinder, but it is not a necessity. Check for stack overflows CONFIG_DEBUG_STACKOVERFLOW This option make do_IRQ() check for enough stack space beeing left. This is safe to enable. Debug high memory support CONFIG_DEBUG_HIGHMEM This options enables addition error checking for high memory systems. Disable for production systems. Verbose kernel error messages CONFIG_DEBUG_ERRORS This option controls verbose debugging information which can be printed when the kernel detects an internal error. This debugging information is useful to kernel hackers when tracking down problems, but mostly meaningless to other people. It's safe to say Y unless you are concerned with the code size or don't want to see these messages. Compile kernel with frame pointer CONFIG_FRAME_POINTER If you say Y here, the resulting kernel will be slightly larger and slower, but it will give very useful debugging information. If you don't debug the kernel, you can say N, but we may not be able to solve problems without frame pointers. Verbose user fault messages CONFIG_DEBUG_USER When a user program crashes due to an exception, the kernel can print a brief message explaining what the problem was. This is sometimes helpful for debugging but serves no purpose on a production system. Most people should say N here. Include gdb debugging information in kernel binary CONFIG_DEBUG_INFO Say Y here to include source-level debugging information in the `vmlinux' binary image. This is handy if you want to use gdb or addr2line to debug the kernel. It has no impact on the in-memory footprint of the running kernel but it can increase the amount of time and disk space needed for compilation of the kernel. If in doubt say N. Kernel low-level debugging functions CONFIG_DEBUG_LL Say Y here to include definitions of printascii, printchar, printhex in the kernel. This is helpful if you are debugging code that executes before the console is initialized. Kernel low-level debugging messages via footbridge serial port CONFIG_DEBUG_DC21285_PORT Say Y here if you want the debug print routines to direct their output to the serial port in the DC21285 (Footbridge). Saying N will cause the debug messages to appear on the first 16550 serial port. Kernel low-level debugging messages via UART2 CONFIG_DEBUG_CLPS711X_UART2 Say Y here if you want the debug print routines to direct their output to the second serial port on these devices. Saying N will cause the debug messages to appear on the first serial port. Disable pgtable cache CONFIG_NO_PGT_CACHE Normally the kernel maintains a `quicklist' of preallocated pagetable structures in order to increase performance. On machines with very few pages this may however be a loss. Say Y here to disable the pgtable cache. RISC OS personality CONFIG_ARTHUR Say Y here to include the kernel code necessary if you want to run Acorn RISC OS/Arthur binaries under Linux. This code is still very experimental; if this sounds frightening, say N and sleep in peace. You can also say M here to compile this support as a module (which will be called arthur.o). Initial kernel command line CONFIG_CMDLINE On some architectures (EBSA110 and CATS), there is currently no way for the boot loader to pass arguments to the kernel. For these architectures, you should supply some command-line options at build time by entering them here. As a minimum, you should specify the memory size and the root device (e.g., mem=64M root=/dev/nfs). Kernel-mode alignment trap handler CONFIG_ALIGNMENT_TRAP ARM processors can not fetch/store information which is not naturally aligned on the bus, i.e., a 4 byte fetch must start at an address divisible by 4. On 32-bit ARM processors, these non-aligned fetch/store instructions will be emulated in software if you say here, which has a severe performance impact. This is necessary for correct operation of some network protocols. With an IP-only configuration it is safe to say N, otherwise say Y. DC21285 serial port support CONFIG_SERIAL_21285 If you have a machine based on a 21285 (Footbridge) StrongARM(R)/ PCI bridge you can enable its onboard serial port by enabling this option. The device has major ID 4, minor 64. Console on DC21285 serial port CONFIG_SERIAL_21285_CONSOLE If you have enabled the serial port on the 21285 footbridge you can make it the console by answering Y to this option. SA1100 serial port support CONFIG_SERIAL_SA1100 * Orphaned entry retained 20 April 2001 by Russell King * * If you read this note from the configurator, please contact * * the Configure.help maintainers. * If you have a machine based on a SA1100/SA1110 StrongARM CPU you can enable its onboard serial port by enabling this option. Please read for further info. Console on SA1100 serial port CONFIG_SERIAL_SA1100_CONSOLE * Orphaned entry retained 20 April 2001 by Russell King * * If you read this note from the configurator, please contact * * the Configure.help maintainers. * If you have enabled the serial port on the SA1100/SA1110 StrongARM CPU you can make it the console by answering Y to this option. L7200 serial port support CONFIG_SERIAL_L7200 * Orphaned entry retained 20 April 2001 by Russell King * * If you read this note from the configurator, please contact * * the Configure.help maintainers. * If you have a LinkUp Systems L7200 board you can enable its two onboard serial ports by enabling this option. The device numbers are major ID 4 with minor 64 and 65 respectively. Console on L7200 serial port CONFIG_SERIAL_L7200_CONSOLE * Orphaned entry retained 20 April 2001 by Russell King * * If you read this note from the configurator, please contact * * the Configure.help maintainers. * If you have enabled the serial ports on the L7200 development board you can make the first serial port the console by answering Y to this option. L7200 SDB keyboard support CONFIG_KEYBOARD_L7200 * Orphaned entry retained 20 April 2001 by Russell King * * If you read this note from the configurator, please contact * * the Configure.help maintainers. * Enable this option if you would like to be able to use a keyboard on a LinkUp Systems L7200 board. L7200 SDB Fujitsu keyboard support CONFIG_KEYBOARD_L7200_NORM * Orphaned entry retained 20 April 2001 by Russell King * * If you read this note from the configurator, please contact * * the Configure.help maintainers. * Select the Fujitsu keyboard if you want a normal QWERTY style keyboard on the LinkUp SDB. L7200 SDB Prototype keyboard support CONFIG_KEYBOARD_L7200_DEMO * Orphaned entry retained 20 April 2001 by Russell King * * If you read this note from the configurator, please contact * * the Configure.help maintainers. * Select the prototype keyboard if you want to play with the LCD/keyboard combination on the LinkUp SDB. Footbridge Mode CONFIG_HOST_FOOTBRIDGE * Orphaned entry retained 20 April 2001 by Russell King * * If you read this note from the configurator, please contact * * the Configure.help maintainers. * The 21285 Footbridge chip can operate in either `host mode' or `add-in' mode. Say Y if your 21285 is in host mode, and therefore is the configuration master, otherwise say N. This must not be set to Y if the card is used in 'add-in' mode. MFM hard disk support CONFIG_BLK_DEV_MFM Support the MFM hard drives on the Acorn Archimedes both on-board the A4x0 motherboards and via the Acorn MFM modules. Drives up to 64MB are supported. If you haven't got one of these machines or drives just say N. Old Archimedes floppy (1772) support CONFIG_BLK_DEV_FD1772 Support the floppy drive on the Acorn Archimedes (A300, A4x0, A540, R140 and R260) series of computers; it supports only 720K floppies at the moment. If you don't have one of these machines just answer N. Autodetect hard drive geometry CONFIG_BLK_DEV_MFM_AUTODETECT If you answer Y, the MFM code will attempt to automatically detect the cylinders/heads/sectors count on your hard drive. WARNING: This sometimes doesn't work and it also does some dodgy stuff which potentially might damage your drive. NetWinder /dev/flash support CONFIG_NWFLASH If you say Y here and create a character device /dev/flash with major 10 and minor 160 you can manipulate the flash ROM containing the NetWinder firmware. Be careful as accidentally overwriting the flash contents can render your computer unbootable. On no account allow random users access to this device. :-) 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 nwflash.o. If you want to compile it as a module, say M here and read . If you're not sure, say N. SRM environment variables in procfs CONFIG_SRM_ENV If you enable this option, a subdirectory inside /proc called /proc/srm_environment will give you access to the all important SRM environment variables (those which have a name) and also to all others (by their internal number). SRM is something like a BIOS for Alpha machines. There are some other such BIOSes, like AlphaBIOS, which this driver cannot support (hey, that's not SRM!). Despite the fact that this driver doesn't work on all Alphas (but only on those which have SRM as their firmware), it's save to build it even if your particular machine doesn't know about SRM (or if you intend to compile a generic kernel). It will simply not create those subdirectory in /proc (and give you some warning, of course). This driver is also available as a module and will be called srm_env.o then. Footbridge internal watchdog CONFIG_21285_WATCHDOG The Intel Footbridge chip contains a builtin watchdog circuit. Say Y here if you wish to use this. Alternatively say M to compile the driver as a module, which will be called wdt285.o. This driver does not work on all machines. In particular, early CATS boards have hardware problems that will cause the machine to simply lock up if the watchdog fires. "If in doubt, leave it out" - say N. NetWinder WB83C977 watchdog CONFIG_977_WATCHDOG Say Y here to include support for the WB977 watchdog included in NetWinder machines. Alternatively say M to compile the driver as a module, which will be called wdt977.o. Not sure? It's safe to say N. IrDA subsystem support CONFIG_IRDA Say Y here if you want to build support for the IrDA (TM) protocols. The Infrared Data Associations (tm) specifies standards for wireless infrared communication and is supported by most laptops and PDA's. To use Linux support for the IrDA (tm) protocols, you will also need some user-space utilities like irattach. For more information, see the file . You also want to read the IR-HOWTO, available at . If you want to exchange bits of data (vCal, vCard) with a PDA, you will need to install some OBEX application, such as OpenObex : This support is also available as a module called irda.o. If you want to compile it as a module, say M here and read . Ultra (connectionless) protocol CONFIG_IRDA_ULTRA Say Y here to support the connectionless Ultra IRDA protocol. Ultra allows to exchange data over IrDA with really simple devices (watch, beacon) without the overhead of the IrDA protocol (no handshaking, no management frames, simple fixed header). Ultra is available as a special socket : socket(AF_IRDA, SOCK_DGRAM, 1); IrDA cache last LSAP CONFIG_IRDA_CACHE_LAST_LSAP Say Y here if you want IrLMP to cache the last LSAP used. This makes sense since most frames will be sent/received on the same connection. Enabling this option will save a hash-lookup per frame. If unsure, say Y. IrDA Fast RRs CONFIG_IRDA_FAST_RR Say Y here is you want IrLAP to send fast RR (Receive Ready) frames when acting as a primary station. Disabling this option will make latency over IrDA very bad. Enabling this option will make the IrDA stack send more packet than strictly necessary, thus reduce your battery life (but not that much). Fast RR will make IrLAP send out a RR frame immediately when receiving a frame if its own transmit queue is currently empty. This will give a lot of speed improvement when receiving much data since the secondary station will not have to wait the max. turn around time (usually 500ms) before it is allowed to transmit the next time. If the transmit queue of the secondary is also empty, the primary will start backing-off before sending another RR frame, waiting longer each time until the back-off reaches the max. turn around time. This back-off increase in controlled via /proc/sys/net/irda/fast_poll_increase If unsure, say Y. IrDA debugging information CONFIG_IRDA_DEBUG Say Y here if you want the IrDA subsystem to write debug information to your syslog. You can change the debug level in /proc/sys/net/irda/debug . When this option is enabled, the IrDA also perform many extra internal verifications which will usually prevent the kernel to crash in case of bugs. If unsure, say Y (since it makes it easier to find the bugs). IrLAN protocol CONFIG_IRLAN Say Y here if you want to build support for the IrLAN protocol. If you want to compile it as a module (irlan.o), say M here and read . IrLAN emulates an Ethernet and makes it possible to put up a wireless LAN using infrared beams. The IrLAN protocol can be used to talk with infrared access points like the HP NetbeamIR, or the ESI JetEye NET. You can also connect to another Linux machine running the IrLAN protocol for ad-hoc networking! IrNET protocol CONFIG_IRNET Say Y here if you want to build support for the IrNET protocol. If you want to compile it as a module (irnet.o), say M here and read . IrNET is a PPP driver, so you will also need a working PPP subsystem (driver, daemon and config)... IrNET is an alternate way to transfer TCP/IP traffic over IrDA. It uses synchronous PPP over a set of point to point IrDA sockets. You can use it between Linux machine or with W2k. IrCOMM protocol CONFIG_IRCOMM Say Y here if you want to build support for the IrCOMM protocol. If you want to compile it as a module (you will get ircomm.o and ircomm-tty.o), say M here and read . IrCOMM implements serial port emulation, and makes it possible to use all existing applications that understands TTY's with an infrared link. Thus you should be able to use application like PPP, minicom and others. Enabling this option will create two modules called ircomm and ircomm_tty. IrTTY IrDA Device Driver CONFIG_IRTTY_SIR Say Y here if you want to build support for the IrTTY line discipline. If you want to compile it as a module (irtty.o), say M here and read . IrTTY makes it possible to use Linux's own serial driver for all IrDA ports that are 16550 compatible. Most IrDA chips are 16550 compatible so you should probably say Y to this option. Using IrTTY will however limit the speed of the connection to 115200 bps (IrDA SIR mode). If unsure, say Y. IrPORT IrDA serial driver CONFIG_IRPORT_SIR Say Y here if you want to build support for the IrPORT IrDA device driver. If you want to compile it as a module (irport.o), say M here and read . IrPORT can be used instead of IrTTY and sometimes this can be better. One example is if your IrDA port does not have echo-canceling, which will work OK with IrPORT since this driver is working in half-duplex mode only. You don't need to use irattach with IrPORT, but you just insert it the same way as FIR drivers (insmod irport io=0x3e8 irq=11). Notice that IrPORT is a SIR device driver which means that speed is limited to 115200 bps. If unsure, say Y. USB IrDA FIR dongle Device Driver CONFIG_USB_IRDA Say Y here if you want to build support for the USB IrDA FIR Dongle device driver. If you want to compile it as a module (irda-usb.o), say M here and read . IrDA-USB support the various IrDA USB dongles available and most of their peculiarities. Those dongles plug in the USB port of your computer, are plug and play, and support SIR and FIR (4Mbps) speeds. On the other hand, those dongles tend to be less efficient than a FIR chipset. Please note that the driver is still experimental. And of course, you will need both USB and IrDA support in your kernel... Datafab MDCFE-B Compact Flash Reader support CONFIG_USB_STORAGE_DATAFAB This option enables a sub-driver of the USB Mass Storage driver. These sub-drivers are considered experimental, and should only be used by very brave people. System crashes and other bad things are likely to occur if you use this driver. If in doubt, select N. HP CD-Writer 82xx support CONFIG_USB_STORAGE_HP8200e This option enables a sub-driver of the USB Mass Storage driver. These sub-drivers are considered experimental, and should only be used by very brave people. System crashes and other bad things are likely to occur if you use this driver. If in doubt, select N. Lexar Jumpshot Compact Flash Reader CONFIG_USB_STORAGE_JUMPSHOT This option enables a sub-driver of the USB Mass Storage driver. These sub-drivers are considered experimental, and should only be used by very brave people. System crashes and other bad things are likely to occur if you use this driver. If in doubt, select N. Winbond W83977AF IrDA Device Driver CONFIG_WINBOND_FIR Say Y here if you want to build IrDA support for the Winbond W83977AF super-io chipset. This driver should be used for the IrDA chipset in the Corel NetWinder. The driver supports SIR, MIR and FIR (4Mbps) speeds. If you want to compile it as a module, say M here and read . The module will be called w83977af_ir.o. NSC PC87108/PC87338 IrDA Device Driver CONFIG_NSC_FIR Say Y here if you want to build support for the NSC PC87108 and PC87338 IrDA chipsets. This driver supports SIR, MIR and FIR (4Mbps) speeds. If you want to compile it as a module, say M here and read . The module will be called nsc-ircc.o. National Semiconductor DP83820 support CONFIG_NS83820 This is a driver for the National Semiconductor DP83820 series of gigabit ethernet MACs. Cards using this chipset include: SMC 9452TX SMC SMC9462TX D-Link DGE-500T PureData PDP8023Z-TG SOHO-GA2000T SOHO-GA2500T. NetGear GA621 This driver supports the use of zero copy on tx, checksum validation on rx, and 64 bit addressing. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called ns83820.o. Toshiba Type-O IR Port device driver CONFIG_TOSHIBA_FIR Say Y here if you want to build support for the Toshiba Type-O IR chipset. This chipset is used by the Toshiba Libretto 100CT, and many more laptops. If you want to compile it as a module, say M here and read . The module will be called toshoboe.o. SMC IrCC CONFIG_SMC_IRCC_FIR Say Y here if you want to build support for the SMC Infrared Communications Controller. It is used in the Fujitsu Lifebook 635t and Sony PCG-505TX. If you want to compile it as a module, say M here and read . The module will be called smc-ircc.o. ALi M5123 FIR controller driver CONFIG_ALI_FIR Say Y here if you want to build support for the ALi M5123 FIR Controller. The ALi M5123 FIR Controller is embedded in ALi M1543C, M1535, M1535D, M1535+, M1535D Sourth Bridge. This driver supports SIR, MIR and FIR (4Mbps) speeds. If you want to compile it as a module, say M here and read . The module will be called ali-ircc.o. VLSI 82C147 PCI-IrDA SIR/MIR/FIR Controller driver CONFIG_VLSI_FIR Say Y here if you want to build support for the VLSI 82C147 PCI-IrDA Controller. This controller is used by the HP OmniBook 800 and 5500 notebooks. The driver provides support for SIR, MIR and FIR (4Mbps) speeds. If you want to compile it as a module, say M here and read . The module will be called vlsi_ir.o. Serial dongle support CONFIG_DONGLE Say Y here if you have an infrared device that connects to your computer's serial port. These devices are called dongles. Then say Y or M to the driver for your particular dongle below. Note that the answer to this question won't directly affect the kernel: saying N will just cause the configurator to skip all the questions about serial dongles. ESI JetEye PC dongle CONFIG_ESI_DONGLE Say Y here if you want to build support for the Extended Systems JetEye PC dongle. If you want to compile it as a module, say M here and read . The ESI dongle attaches to the normal 9-pin serial port connector, and can currently only be used by IrTTY. To activate support for ESI dongles you will have to start irattach like this: "irattach -d esi". If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called esi.o. ACTiSYS IR-220L and IR220L+ dongle CONFIG_ACTISYS_DONGLE Say Y here if you want to build support for the ACTiSYS IR-220L and IR220L+ dongles. If you want to compile it as a module, say M here and read . The ACTiSYS dongles attaches to the normal 9-pin serial port connector, and can currently only be used by IrTTY. To activate support for ACTiSYS dongles you will have to start irattach like this: "irattach -d actisys" or "irattach -d actisys+". If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called actisys.o. Tekram IrMate 210B dongle CONFIG_TEKRAM_DONGLE Say Y here if you want to build support for the Tekram IrMate 210B dongle. If you want to compile it as a module, say M here and read . The Tekram dongle attaches to the normal 9-pin serial port connector, and can currently only be used by IrTTY. To activate support for Tekram dongles you will have to start irattach like this: "irattach -d tekram". If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called tekram.o. Greenwich GIrBIL dongle CONFIG_GIRBIL_DONGLE Say Y here if you want to build support for the Greenwich GIrBIL dongle. If you want to compile it as a module, say M here and read . The Greenwich dongle attaches to the normal 9-pin serial port connector, and can currently only be used by IrTTY. To activate support for Greenwich dongles you will have to insert "irattach -d girbil" in the /etc/irda/drivers script. If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called girbil.o. Parallax LiteLink dongle CONFIG_LITELINK_DONGLE Say Y here if you want to build support for the Parallax Litelink dongle. If you want to compile it as a module, say M here and read . The Parallax dongle attaches to the normal 9-pin serial port connector, and can currently only be used by IrTTY. To activate support for Parallax dongles you will have to start irattach like this "irattach -d litelink". If you want to compile the driver as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read . The module will be called litelink.o. Microchip MCP2120 dongle CONFIG_MCP2120_DONGLE Say Y here if you want to build support for the Microchip MCP2120 dongle. If you want to compile it as a module, say M here and read . The MCP2120 dongle attaches to the normal 9-pin serial port connector, and can currently only be used by IrTTY. To activate support for MCP2120 dongles you will have to insert "irattach -d mcp2120" in the /etc/irda/drivers script. You must build this dongle yourself. For more information see: Old Belkin dongle CONFIG_OLD_BELKIN_DONGLE Say Y here if you want to build support for the Adaptec Airport 1000 and 2000 dongles. If you want to compile it as a module, say M here and read . The module will be called old_belkin.o. Some information is contained in the comments at the top of . ACTiSYS IR-200L dongle (Experimental) CONFIG_ACT200L_DONGLE Say Y here if you want to build support for the ACTiSYS IR-200L dongle. If you want to compile it as a module, say M here and read Documentation/modules.txt. The ACTiSYS IR-200L dongle attaches to the normal 9-pin serial port connector, and can currently only be used by IrTTY. To activate support for ACTiSYS IR-200L dongles you will have to start irattach like this: "irattach -d act200l". Mobile Action MA600 dongle (Experimental) CONFIG_MA600_DONGLE Say Y here if you want to build support for the Mobile Action MA600 dongle. If you want to compile it as a module, say M here and read . The MA600 dongle attaches to the normal 9-pin serial port connector, and can currently only be tested on IrCOMM. To activate support for MA600 dongles you will have to insert "irattach -d ma600" in the /etc/irda/drivers script. Note: irutils 0.9.15 requires no modification. irutils 0.9.9 needs modification. For more information, download the following tar gzip file. There is a pre-compiled module on VME (Motorola and BVM) support CONFIG_VME Say Y here if you want to build a kernel for a 680x0 based VME board. Boards currently supported include Motorola boards MVME147, MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and BVME6000 boards from BVM Ltd are also supported. MVME147 support CONFIG_MVME147 Say Y to include support for early Motorola VME boards. This will build a kernel which can run on MVME147 single-board computers. If you select this option you will have to select the appropriate drivers for SCSI, Ethernet and serial ports later on. MVME162, 166 and 167 support CONFIG_MVME16x Say Y to include support for Motorola VME boards. This will build a kernel which can run on MVME162, MVME166, MVME167, MVME172, and MVME177 boards. If you select this option you will have to select the appropriate drivers for SCSI, Ethernet and serial ports later on. BVME4000 and BVME6000 support CONFIG_BVME6000 Say Y to include support for VME boards from BVM Ltd. This will build a kernel which can run on BVME4000 and BVME6000 boards. If you select this option you will have to select the appropriate drivers for SCSI, Ethernet and serial ports later on. Use write-through caching for 68060 supervisor accesses CONFIG_060_WRITETHROUGH The 68060 generally uses copyback caching of recently accessed data. Copyback caching means that memory writes will be held in an on-chip cache and only written back to memory some time later. Saying Y here will force supervisor (kernel) accesses to use writethrough caching. Writethrough caching means that data is written to memory straight away, so that cache and memory data always agree. Writethrough caching is less efficient, but is needed for some drivers on 68060 based systems where the 68060 bus snooping signal is hardwired on. The 53c710 SCSI driver is known to suffer from this problem. WD33C93 SCSI driver for MVME147 CONFIG_MVME147_SCSI Support for the on-board SCSI controller on the Motorola MVME147 single-board computer. SCC support for MVME147 serial ports CONFIG_MVME147_SCC This is the driver for the serial ports on the Motorola MVME147 boards. Everyone using one of these boards should say Y here. NCR53C710 SCSI driver for MVME16x CONFIG_MVME16x_SCSI The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710 SCSI controller chip. Almost everyone using one of these boards will want to say Y to this question. NCR53C710 SCSI driver for BVME6000 CONFIG_BVME6000_SCSI The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710 SCSI controller chip. Almost everyone using one of these boards will want to say Y to this question. MVME147 (Lance) Ethernet support CONFIG_MVME147_NET Support for the on-board Ethernet interface on the Motorola MVME147 single-board computer. Say Y here to include the driver for this chip in your kernel. If you want to compile it as a module, say M here and read . MVME16x Ethernet support CONFIG_MVME16x_NET This is the driver for the Ethernet interface on the Motorola MVME162, 166, 167, 172 and 177 boards. Say Y here to include the driver for this chip in your kernel. If you want to compile it as a module, say M here and read . BVME6000 Ethernet support CONFIG_BVME6000_NET This is the driver for the Ethernet interface on BVME4000 and BVME6000 VME boards. Say Y here to include the driver for this chip in your kernel. If you want to compile it as a module, say M here and read . CD2401 support for MVME166/7 serial ports CONFIG_SERIAL167 This is the driver for the serial ports on the Motorola MVME166, 167, and 172 boards. Everyone using one of these boards should say Y here. SCC support for MVME162 serial ports CONFIG_MVME162_SCC This is the driver for the serial ports on the Motorola MVME162 and 172 boards. Everyone using one of these boards should say Y here. SCC support for BVME6000 serial ports CONFIG_BVME6000_SCC This is the driver for the serial ports on the BVME4000 and BVME6000 boards from BVM Ltd. Everyone using one of these boards should say Y here. 7-Segment Display support CONFIG_DISPLAY7SEG This is the driver for the 7-segment display and LED present on Sun Microsystems CompactPCI models CP1400 and CP1500. 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 display7seg.o. If you want to compile it as a module, say M here and read . If you do not have a CompactPCI model CP1400 or CP1500, or another UltraSPARC-IIi-cEngine boardset with a 7-segment display, you should say N to this option. # Choice: cristype Etrax-100-LX-v1 CONFIG_ETRAX100LX Support version 1 of the Etrax 100LX. Etrax-100-LX-v2 CONFIG_ETRAX100LX_V2 Support version 2 of the Etrax 100LX. Etrax-100-LX-for-xsim-simulator CONFIG_SVINTO_SIM Support the xsim ETRAX Simulator. DRAM size (dec, in MB) CONFIG_ETRAX_DRAM_SIZE Size of DRAM (decimal in MB) typically 2, 8 or 16. ETRAX Flash Memory configuration CONFIG_ETRAX_FLASH_BUSWIDTH Width in bytes of the Flash bus (1, 2 or 4). Is usually 2. # Choice: crisleds LED configuration on PA CONFIG_ETRAX_PA_LEDS The Etrax network driver is responsible for flashing LED's when packets arrive and are sent. It uses macros defined in , and those macros are defined after what YOU choose in this option. The actual bits used are configured separately. Select this if the LEDs are on port PA. Some products put the leds on PB or a memory-mapped latch (CSP0) instead. LED configuration on PB CONFIG_ETRAX_PB_LEDS The Etrax network driver is responsible for flashing LED's when packets arrive and are sent. It uses macros defined in , and those macros are defined after what YOU choose in this option. The actual bits used are configured separately. Select this if the LEDs are on port PB. Some products put the leds on PA or a memory-mapped latch (CSP0) instead. LED configuration on CSP0 CONFIG_ETRAX_CSP0_LEDS The Etrax network driver is responsible for flashing LED's when packets arrive and are sent. It uses macros defined in , and those macros are defined after what YOU choose in this option. The actual bits used are configured separately. Select this if the LEDs are on a memory-mapped latch using chip select CSP0, this is mapped at 0x90000000. Some products put the leds on PA or PB instead. No LED at all CONFIG_ETRAX_NO_LEDS Select this option if you don't have any LED at all. First green LED bit CONFIG_ETRAX_LED1G Bit to use for the first green LED. Most Axis products use bit 2 here. First red LED bit CONFIG_ETRAX_LED1R Bit to use for the first red LED. Most Axis products use bit 3 here. For products with only one controllable LED, set this to same as CONFIG_ETRAX_LED1G (normally 2). Second green LED bit CONFIG_ETRAX_LED2G Bit to use for the second green LED. The "Active" LED. Most Axis products use bit 4 here. For products with only one controllable LED, set this to same as CONFIG_ETRAX_LED1G (normally 2). Second red LED bit CONFIG_ETRAX_LED2R Bit to use for the second red LED. Most Axis products use bit 5 here. For products with only one controllable LED, set this to same as CONFIG_ETRAX_LED1G (normally 2). Third green LED bit CONFIG_ETRAX_LED3G Bit to use for the third green LED. The "Drive" LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Third red LED bit CONFIG_ETRAX_LED3R Bit to use for the third red LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Fourth green LED bit CONFIG_ETRAX_LED4G Bit to use for the fourth green LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Fourth red LED bit CONFIG_ETRAX_LED4R Bit to use for the fourth red LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Fifth green LED bit CONFIG_ETRAX_LED5G Bit to use for the fifth green LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Fifth red LED bit CONFIG_ETRAX_LED5R Bit to use for the fifth red LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Sixth green LED bit CONFIG_ETRAX_LED6G Bit to use for the sixth green LED. The "Drive" LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Sixth red LED bit CONFIG_ETRAX_LED6R Bit to use for the sixth red LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Seventh green LED bit CONFIG_ETRAX_LED7G Bit to use for the seventh green LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Seventh red LED bit CONFIG_ETRAX_LED7R Bit to use for the seventh red LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Eighth yellow LED bit CONFIG_ETRAX_LED8Y Bit to use for the eighth yellow LED. The "Drive" LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Ninth yellow LED bit CONFIG_ETRAX_LED9Y Bit to use for the ninth yellow LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Tenth yellow LED bit CONFIG_ETRAX_LED10Y Bit to use for the tenth yellow LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Eleventh yellow LED bit CONFIG_ETRAX_LED11Y Bit to use for the eleventh yellow LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Twelfth red LED bit CONFIG_ETRAX_LED12R Bit to use for the twelfth red LED. For products with only one or two controllable LEDs, set this to same as CONFIG_ETRAX_LED1G (normally 2). Flash LED off during activity CONFIG_ETRAX_LED_OFF_DURING_ACTIVITY This option allows you to decide whether the network LED (and Bluetooth LED in case you use Bluetooth) will be on or off when the network is connected, and whether it should flash off or on when there is activity. If you say y to this option the network LED will be lit when there is a connection, and will flash off when there is activity. PA button configuration CONFIG_ETRAX_PA_BUTTON_BITMASK This is a bitmask with information about what bits on PA that are used for buttons. Most products has a so called TEST button on PA1, if that's true use 02 here. Use 00 if there are no buttons on PA. If the bitmask is <> 00 a button driver will be included in the gpio driver. Etrax general I/O support must be enabled. PA changeable direction bits CONFIG_ETRAX_PA_CHANGEABLE_DIR This is a bitmask with information of what bits in PA that a user can change direction on using ioctl's. Bit set = changeable. You probably want 00 here. PA changeable data bits CONFIG_ETRAX_PA_CHANGEABLE_BITS This is a bitmask with information of what bits in PA that a user can change change the value on using ioctl's. Bit set = changeable. You probably want 00 here. PA changeable direction bits CONFIG_ETRAX_PB_CHANGEABLE_DIR This is a bitmask with information of what bits in PB that a user can change direction on using ioctl's. Bit set = changeable. You probably want 00 here. PB changeable data bits CONFIG_ETRAX_PB_CHANGEABLE_BITS This is a bitmask with information of what bits in PB that a user can change the value on using ioctl's. Bit set = changeable. You probably want 00 here. Kernel debugger (kgdb) CONFIG_ETRAX_KGDB The CRIS version of gdb can be used to remotely debug a running Linux kernel via the serial debug port. Provided you have gdb-cris installed, run gdb-cris vmlinux, then type (gdb) set remotebaud 115200 <- kgdb uses 115200 as default (gdb) target remote /dev/ttyS0 <- maybe you use another port This should connect you to your booted kernel (or boot it now if you didn't before). The kernel halts when it boots, waiting for gdb if this option is turned on! Etrax bus waitstates CONFIG_ETRAX_DEF_R_WAITSTATES Waitstates for SRAM, Flash and peripherals (not DRAM). 95f8 is a good choice for most Axis products... Etrax bus configuration CONFIG_ETRAX_DEF_R_BUS_CONFIG Assorted bits controlling write mode, DMA burst length etc. 104 is a good choice for most Axis products... Etrax SDRAM configuration CONFIG_ETRAX_SDRAM Enable this if you use SDRAM chips and configure R_SDRAM_CONFIG and R_SDRAM_TIMING as well. DRAM size (dec, in MB) CONFIG_ETRAX_DEF_R_DRAM_CONFIG The R_DRAM_CONFIG register specifies everything on how the DRAM chips in the system are connected to the Etrax CPU. This is different depending on the manufacturer, chip type and number of chips. So this value often needs to be different for each Axis product. Etrax DRAM timing CONFIG_ETRAX_DEF_R_DRAM_TIMING Different DRAM chips have different speeds. Current Axis products use 50ns DRAM chips which can use the timing: 5611. Etrax SDRAM configuration CONFIG_ETRAX_DEF_R_SDRAM_CONFIG The R_SDRAM_CONFIG register specifies everything on how the SDRAM chips in the system are connected to the Etrax CPU. This is different depending on the manufacturer, chip type and number of chips. So this value often needs to be different for each Axis product. Etrax SDRAM timing CONFIG_ETRAX_DEF_R_SDRAM_TIMING Different SDRAM chips have different timing. Etrax General port A direction CONFIG_ETRAX_DEF_R_PORT_PA_DIR Configures the direction of general port A bits. 1 is out, 0 is in. This is often totally different depending on the product used. There are some guidelines though - if you know that only LED's are connected to port PA, then they are usually connected to bits 2-4 and you can therefore use 1c. On other boards which don't have the LED's at the general ports, these bits are used for all kinds of stuff. If you don't know what to use, it is always safe to put all as inputs, although floating inputs isn't good. Etrax General port A data CONFIG_ETRAX_DEF_R_PORT_PA_DATA Configures the initial data for the general port A bits. Most products should use 00 here. Etrax General port B config CONFIG_ETRAX_DEF_R_PORT_PB_CONFIG Configures the type of the general port B bits. 1 is chip select, 0 is port. Most products should use 00 here. Etrax General port B direction CONFIG_ETRAX_DEF_R_PORT_PB_DIR Configures the direction of general port B bits. 1 is out, 0 is in. This is often totally different depending on the product used. Bits 0 and 1 on port PB are usually used for I2C communication, but the kernel I2C driver sets the appropriate directions itself so you don't need to take that into consideration when setting this option. If you don't know what to use, it is always safe to put all as inputs. Etrax General port B data CONFIG_ETRAX_DEF_R_PORT_PB_DATA Configures the initial data for the general port A bits. Most products should use FF here. Etrax General port device CONFIG_ETRAX_GPIO Enables the Etrax general port device (major 120, minors 0 and 1). You can use this driver to access the general port bits. It supports these ioctl's: #include fd = open("/dev/gpioa", O_RDWR); // or /dev/gpiob ioctl(fd, _IO(ETRAXGPIO_IOCTYPE, IO_SETBITS), bits_to_set); ioctl(fd, _IO(ETRAXGPIO_IOCTYPE, IO_CLRBITS), bits_to_clear); val = ioctl(fd, _IO(ETRAXGPIO_IOCTYPE, IO_READBITS), NULL); Remember that you need to setup the port directions appropriately in the General configuration. Etrax parallel data support CONFIG_ETRAX_PARDATA Adds support for writing data to the parallel port par0 of the ETRAX 100. If you create a character special file with major number 126, you can write to the data bits of par0. Note: you need to disable Etrax100 parallel port support. Etrax parallel LCD (HD44780) Driver CONFIG_ETRAX_LCD_HD44780 Adds support for a HD44780 controlled LCD connected to the parallel port par0 of the Etrax. Etrax Serial port ser0 support CONFIG_ETRAX_SERIAL Enables the ETRAX 100 serial driver for ser0 (ttyS0) You probably want this enabled. /proc/serial entry CONFIG_ETRAX_SERIAL_PROC_ENTRY Enables /proc/serial entry where errors and statistics can be viewed. CONFIG_PROC_FS must also be set for this to work. Etrax Serial port fast flush of DMA using fast timer API CONFIG_ETRAX_SERIAL_FAST_TIMER Select this to have the serial DMAs flushed at a higher rate than normally, possible by using the fast timer API, the timeout is approx. 4 character times. If unsure, say N. Etrax Serial port fast flush of DMA CONFIG_ETRAX_SERIAL_FLUSH_DMA_FAST Select this to have the serial DMAs flushed at a higher rate than normally possible through a fast timer interrupt (currently at 15360 Hz). If unsure, say N. Etrax Serial port receive flush timeout CONFIG_ETRAX_SERIAL_RX_TIMEOUT_TICKS Number of timer ticks between flush of receive fifo (1 tick = 10ms). Try 0-3 for low latency applications. Approx 5 for high load applications (e.g. PPP). Maybe this should be more adaptive some day... Etrax Serial port ser0 DTR, RI, DSR and CD support on PB CONFIG_ETRAX_SER0_DTR_RI_DSR_CD_ON_PB Enables the status and control signals DTR, RI, DSR and CD on PB for ser0. Serial port 1 enabled CONFIG_ETRAX_SERIAL_PORT1 Enables the ETRAX 100 serial driver for ser1 (ttyS1). Etrax Serial port ser1 DTR, RI, DSR and CD support on PB CONFIG_ETRAX_SER1_DTR_RI_DSR_CD_ON_PB Enables the status and control signals DTR, RI, DSR and CD on PB for ser1. Serial port 2 enabled CONFIG_ETRAX_SERIAL_PORT2 Enables the ETRAX 100 serial driver for ser2 (ttyS2). Etrax Serial port ser2 DTR, RI, DSR and CD support on PA CONFIG_ETRAX_SER2_DTR_RI_DSR_CD_ON_PA Enables the status and control signals DTR, RI, DSR and CD on PA for ser2. Serial port 3 enabled CONFIG_ETRAX_SERIAL_PORT3 Enables the ETRAX 100 serial driver for ser3 (ttyS3). Etrax100 RS-485 support CONFIG_ETRAX_RS485 Enables support for RS-485 serial communication. For a primer on RS-485, see . Etrax100 RS-485 mode on PA CONFIG_ETRAX_RS485_ON_PA Control Driver Output Enable on RS485 transceiver using a pin on PA port: Axis 2400/2401 uses PA 3. Etrax100 RS-485 mode on PA bit CONFIG_ETRAX_RS485_ON_PA_BIT Control Driver Output Enable on RS485 transceiver using a this bit on PA port. Ser0 DTR on PB bit CONFIG_ETRAX_SER0_DTR_ON_PB_BIT Specify the pin of the PB port to carry the DTR signal for serial port 0. Ser0 RI on PB bit CONFIG_ETRAX_SER0_RI_ON_PB_BIT Specify the pin of the PB port to carry the RI signal for serial port 0. Ser0 DSR on PB bit CONFIG_ETRAX_SER0_DSR_ON_PB_BIT Specify the pin of the PB port to carry the DSR signal for serial port 0. Ser0 CD on PB bit CONFIG_ETRAX_SER0_CD_ON_PB_BIT Specify the pin of the PB port to carry the CD signal for serial port 0. Ser1 DTR on PB bit CONFIG_ETRAX_SER1_DTR_ON_PB_BIT Specify the pin of the PB port to carry the DTR signal for serial port 1. Ser1 RI on PB bit CONFIG_ETRAX_SER1_RI_ON_PB_BIT Specify the pin of the PB port to carry the RI signal for serial port 1. Ser1 DSR on PB bit CONFIG_ETRAX_SER1_DSR_ON_PB_BIT Specify the pin of the PB port to carry the DSR signal for serial port 1. Ser1 CD on PB bit CONFIG_ETRAX_SER1_CD_ON_PB_BIT Specify the pin of the PB port to carry the CD signal for serial port 1. Ser2 DTR on PA bit CONFIG_ETRAX_SER2_DTR_ON_PA_BIT Specify the pin of the PA port to carry the DTR signal for serial port 2. Ser2 RI on PA bit CONFIG_ETRAX_SER2_RI_ON_PA_BIT Specify the pin of the PA port to carry the RI signal for serial port 2. Ser2 DSR on PA bit CONFIG_ETRAX_SER2_DSR_ON_PA_BIT Specify the pin of the PA port to carry the DTR signal for serial port 2. Ser2 CD on PA bit CONFIG_ETRAX_SER2_CD_ON_PA_BIT Specify the pin of the PA port to carry the CD signal for serial port 2. Etrax100 RS-485 disable receiver CONFIG_ETRAX_RS485_DISABLE_RECEIVER It's necessary to disable the serial receiver to avoid serial loopback. Not all products are able to do this in software only. Axis 2400/2401 must disable receiver. Etrax100 I2C Support CONFIG_ETRAX_I2C Enables an I2C driver on PB0 and PB1 on ETRAX100. EXAMPLE usage: i2c_arg = I2C_WRITEARG(STA013_WRITE_ADDR, reg, val); ioctl(fd, _IO(ETRAXI2C_IOCTYPE, I2C_WRITEREG), i2c_arg); i2c_arg = I2C_READARG(STA013_READ_ADDR, reg); val = ioctl(fd, _IO(ETRAXI2C_IOCTYPE, I2C_READREG), i2c_arg); Etrax100 I2C configuration CONFIG_ETRAX_I2C_USES_PB_NOT_PB_I2C Select whether to use the special I2C mode in the PB I/O register or not. This option needs to be selected in order to use some drivers that access the I2C I/O pins directly instead of going through the I2C driver, like the DS1302 realtime-clock driver. If you are uncertain, choose Y here. Etrax100 I2C EEPROM (NVRAM) support CONFIG_ETRAX_I2C_EEPROM Enables I2C EEPROM (non-volatile RAM) on PB0 and PB1 using the I2C driver. Select size option: Probed, 2k, 8k, 16k. (Probing works for 2k and 8k but not that well for 16k) Etrax100 I2C EEPROM (NVRAM) size/16kB CONFIG_ETRAX_I2C_EEPROM_16KB Use a 16kB EEPROM. Etrax100 I2C EEPROM (NVRAM) size/2kB CONFIG_ETRAX_I2C_EEPROM_2KB Use a 2kB EEPROM. Etrax100 I2C EEPROM (NVRAM) size/8kB CONFIG_ETRAX_I2C_EEPROM_8KB Use a 8kB EEPROM. # Choice: etrax_eeprom Etrax100 I2C EEPROM (NVRAM) size/probe CONFIG_ETRAX_I2C_EEPROM_PROBE Specifies size or auto probe of the EEPROM size. Options: Probed, 2k, 8k, 16k. (Probing works for 2k and 8k but not that well for 16k) Etrax DS1302 Real-Time Clock driver CONFIG_ETRAX_DS1302 Enables the driver for the DS1302 Real-Time Clock battery-backed chip on some products. The kernel reads the time when booting, and the date can be set using ioctl(fd, RTC_SET_TIME, &rt) with rt a rtc_time struct (see ) on the /dev/rtc device, major 121. You can check the time with cat /proc/rtc, but normal time reading should be done using libc function time and friends. Etrax DS1302 RST on the Generic Port CONFIG_ETRAX_DS1302_RST_ON_GENERIC_PORT If your product has the RST signal line for the DS1302 RTC on the Generic Port then say Y here, otherwise leave it as N in which case the RST signal line is assumed to be connected to Port PB (just like the SCL and SDA lines). Etrax DS1302 RST bit number CONFIG_ETRAX_DS1302_RSTBIT This is the bit number for the RST signal line of the DS1302 RTC on the selected port. If you have selected the generic port then it should be bit 27, otherwise your best bet is bit 5. Etrax DS1302 SCL bit number CONFIG_ETRAX_DS1302_SCLBIT This is the bit number for the SCL signal line of the DS1302 RTC on Port PB. This is probably best left at 3. Etrax DS1302 SDA bit number CONFIG_ETRAX_DS1302_SDABIT This is the bit number for the SDA signal line of the DS1302 RTC on Port PB. This is probably best left at 2. Etrax 100 IDE Reset CONFIG_ETRAX_IDE_CSP0_8_RESET Configures the pin used to reset the IDE bus. Etrax 100 IDE Reset CONFIG_ETRAX_IDE_CSPE1_16_RESET Configures the pin used to reset the IDE bus. Delay for drives to regain consciousness CONFIG_ETRAX_IDE_DELAY Sets the time to wait for disks to regain consciousness after reset. Etrax 100 IDE Reset CONFIG_ETRAX_IDE_G27_RESET Configures the pin used to reset the IDE bus. # Choice: ide_reset IDE reset on PB Bit 7 CONFIG_ETRAX_IDE_PB7_RESET Configures the pin used to reset the IDE bus. USB 1.1 host CONFIG_ETRAX_USB_HOST This option enables the host functionality of the ETRAX 100LX built-in USB controller. In host mode the controller is designed for CTRL and BULK traffic only, INTR traffic may work as well however (depending on the requirements of timeliness). USB 1.1 host port 1 enabled CONFIG_ETRAX_USB_HOST_PORT1 This option enables port 1 of the ETRAX 100LX USB root hub (RH). USB 1.1 host port 2 enabled CONFIG_ETRAX_USB_HOST_PORT2 This option enables port 2 of the ETRAX 100LX USB root hub (RH). ETRAX 100LX 10/100Mbit Ethernet controller CONFIG_ETRAX_ETHERNET This option enables the ETRAX 100LX built-in 10/100Mbit Ethernet controller. ETRAX 100LX Synchronous serial ports CONFIG_ETRAX_SYNCHRONOUS_SERIAL This option enables support for the ETRAX 100LX built-in synchronous serial ports. These ports are used for continuous streamed data like audio. The default setting is compatible with the STA 013 MP3 decoder, but can easily be tuned to fit any other audio encoder/decoder and SPI. ETRAX 100LX Synchronous serial port 0 enabled CONFIG_ETRAX_SYNCHRONOUS_SERIAL_PORT0 Enables the ETRAX 100LX synchronous serial port 0 (syncser0). ETRAX 100LX Synchronous serial port 0 uses DMA CONFIG_ETRAX_SYNCHRONOUS_SERIAL0_DMA Makes synchronous serial port 0 use DMA. ETRAX 100LX Synchronous serial port 1 enabled CONFIG_ETRAX_SYNCHRONOUS_SERIAL_PORT1 Enables the ETRAX 100LX synchronous serial port 1 (syncser1). ETRAX 100LX Synchronous serial port 1 uses DMA CONFIG_ETRAX_SYNCHRONOUS_SERIAL1_DMA Makes synchronous serial port 1 use DMA. Delay for drives to regain consciousness CONFIG_IDE_DELAY Number of seconds to wait for IDE drives to spin up after an IDE reset. ARTPEC-1 support CONFIG_JULIETTE The ARTPEC-1 is a video-compression chip used in the AXIS 2100 network camera, which is built around an ETRAX-100 board. With this option selected, the ETRAX kernel configures a DMA channel at boot time to talk to the chip. Axis flash-map support CONFIG_ETRAX_AXISFLASHMAP This option enables MTD mapping of flash devices. Needed to use flash memories. If unsure, say Y. Byte-offset of partition table sector CONFIG_ETRAX_PTABLE_SECTOR Byte-offset of the partition table in the first flash chip. The default value is 64kB and should not be changed unless you know exactly what you are doing. The only valid reason for changing this is when the flash block size is bigger than 64kB (e.g. when using two parallel 16 bit flashes). Enable Etrax100 watchdog CONFIG_ETRAX_WATCHDOG Enable the built-in watchdog timer support on Etrax100 embedded network computers. # Choice: crisdebug Serial-0 CONFIG_ETRAX_DEBUG_PORT0 Choose a serial port for the ETRAX debug console. Default to port 0. Etrax debug port on ser1 CONFIG_ETRAX_DEBUG_PORT1 Use serial port 1 for the console. Etrax debug port on ser2 CONFIG_ETRAX_DEBUG_PORT2 Use serial port 2 for the console. Etrax debug port on ser3 CONFIG_ETRAX_DEBUG_PORT3 Use serial port 3 for the console. No Etrax debug port CONFIG_ETRAX_DEBUG_PORT_NULL Disable serial-port debugging. Parallel port support CONFIG_ETRAX_PARPORT Say Y here to enable the ETRAX on-board parallel ports. Parallel port 0 enabled CONFIG_ETRAX_PARALLEL_PORT0 Say Y here to enable parallel port 0. Parallel port 1 enabled CONFIG_ETRAX_PARALLEL_PORT1 Say Y here to enable parallel port 1. # Choice: crisrescue Select a product rescue port CONFIG_ETRAX_RESCUE_SER0 Select one of the four serial ports as a rescue port. The default is port 0. Serial-1 CONFIG_ETRAX_RESCUE_SER1 Use serial port 1 as the rescue port. Serial-2 CONFIG_ETRAX_RESCUE_SER2 Use serial port 2 as the rescue port. Serial-3 CONFIG_ETRAX_RESCUE_SER3 Use serial port 3 as the rescue port. RIO Hardware Watchdog support CONFIG_WATCHDOG_RIO Say Y here to support the hardware watchdog capability on Sun RIO machines. The watchdog timeout period is normally one minute but can be changed with a boot-time parameter. CP1XXX Hardware Watchdog support CONFIG_WATCHDOG_CP1XXX This is the driver for the hardware watchdog timers present on Sun Microsystems CompactPCI models CP1400 and CP1500. 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 cpwatchdog.o. If you want to compile it as a module, say M here and read . If you do not have a CompactPCI model CP1400 or CP1500, or another UltraSPARC-IIi-cEngine boardset with hardware watchdog, you should say N to this option. # Choice: ia64type Itanium CONFIG_ITANIUM Select your IA64 processor type. The default is Intel Itanium. McKinley CONFIG_MCKINLEY Select this to configure for a McKinley processor. # Choice: ia64system IA-64 system type CONFIG_IA64_GENERIC This selects the system type of your hardware. A "generic" kernel will run on any supported IA-64 system. However, if you configure a kernel for your specific system, it will be faster and smaller. To find out what type of IA-64 system you have, you may want to check the IA-64 Linux web site at . As of the time of this writing, most hardware is DIG compliant, so the "DIG-compliant" option is usually the right choice. HP-simulator For the HP simulator (). HP-zx1 For HP zx1 Platforms. SN1 For SGI SN1 Platforms. SN2 For SGI SN2 Platforms. DIG-compliant For DIG ("Developer's Interface Guide") compliant systems. If you don't know what to do, choose "generic". CONFIG_IA64_HP_ZX1 Build a kernel that runs on HP zx1-based systems. This adds support for the zx1 IOMMU and makes root bus bridges appear in PCI config space (required for zx1 agpgart support). CONFIG_IA64_SGI_SN_SIM Build a kernel that runs on both the SGI simulator AND on hardware. There is a very slight performance penalty on hardware for including this option. CONFIG_IA64_SGI_SN_DEBUG This enables addition debug code that helps isolate platform/kernel bugs. There is a small but measurable performance degradation when this option is enabled. # Choice: pagesize Kernel page size CONFIG_IA64_PAGE_SIZE_4KB This lets you select the page size of the kernel. For best IA-64 performance, a page size of 8KB or 16KB is recommended. For best IA-32 compatibility, a page size of 4KB should be selected (the vast majority of IA-32 binaries work perfectly fine with a larger page size). For Itanium systems, do NOT chose a page size larger than 16KB. 4KB For best IA-32 compatibility 8KB For best IA-64 performance 16KB For best IA-64 performance 64KB Not for Itanium. If you don't know what to do, choose 8KB. Enable Itanium B-step specific code CONFIG_ITANIUM_BSTEP_SPECIFIC Select this option to build a kernel for an Itanium prototype system with a B-step CPU. Only B3 step CPUs are supported. You have a B3-step CPU if the "revision" field in /proc/cpuinfo is equal to 4. If the "revision" field shows a number bigger than 4, you do not have to turn on this option. Enable IA-64 Machine Check Abort CONFIG_IA64_MCA Say Y here to enable machine check support for IA-64. If you're unsure, answer Y. Disable IA-64 Virtual Hash Page Table CONFIG_DISABLE_VHPT The Virtual Hash Page Table (VHPT) enhances virtual address translation performance. Normally you want the VHPT active but you can select this option to disable the VHPT for debugging. If you're unsure, answer N. Turn on compare-and-exchange bug checking (slow!) CONFIG_IA64_DEBUG_CMPXCHG Selecting this option turns on bug checking for the IA64 compare-and-exchange instructions. This is slow! Itaniums from step B3 or later don't have this problem. If you're unsure, select N. IA64 IRQ bug checking CONFIG_IA64_DEBUG_IRQ Selecting this option turns on bug checking for the IA64 irq_save and restore instructions. It's useful for tracking down spinlock problems, but slow! If you're unsure, select N. Early printk support (requires VGA!) CONFIG_IA64_EARLY_PRINTK Selecting this option uses the VGA screen for printk() output before the consoles are initialised. It is useful for debugging problems early in the boot process, but only if you have a VGA screen attached. If you're unsure, select N. Print possible IA64 hazards to console CONFIG_IA64_PRINT_HAZARDS Selecting this option prints more information for Illegal Dependency Faults, that is, for Read after Write, Write after Write or Write after Read violations. If you're unsure, select Y. Performance monitor support CONFIG_PERFMON Selects whether support for the IA-64 performance monitor hardware is included in the kernel. This makes some kernel data-structures a little bigger and slows down execution a bit, but it is still usually a good idea to turn this on. If you're unsure, say N. /proc/pal support CONFIG_IA64_PALINFO If you say Y here, you are able to get PAL (Processor Abstraction Layer) information in /proc/pal. This contains useful information about the processors in your systems, such as cache and TLB sizes and the PAL firmware version in use. To use this option, you have to check that the "/proc file system support" (CONFIG_PROC_FS) is enabled, too. /proc/efi/vars support CONFIG_EFI_VARS If you say Y here, you are able to get EFI (Extensible Firmware Interface) variable information in /proc/efi/vars. You may read, write, create, and destroy EFI variables through this interface. To use this option, you have to check that the "/proc file system support" (CONFIG_PROC_FS) is enabled, too. Kernel support for IA-32 emulation CONFIG_IA32_SUPPORT IA64 processors can run IA32 (that is, x86) binaries by emulating the IA32 instruction set. Say Y here to build in kernel support for this. If in doubt, say Y. Physical memory granularity (16 MB) CONFIG_IA64_GRANULE_16MB IA64 identity-mapped regions use a large page size. We'll call such large pages "granules". If you can think of a better name that's unambiguous, let us know... Unless your identity-mapped regions are very large, select a granule size of 16MB. Physical memory granularity (64 MB) CONFIG_IA64_GRANULE_64MB IA64 identity-mapped regions use a large page size. We'll call such large pages "granules". If you can think of a better name that's unambiguous, let us know... Unless your identity-mapped regions are very large, select a granule size of 16MB. (This is the "large" choice.) Enable SGI SN extra debugging code CONFIG_IA64_SGI_SN_DEBUG Turns on extra debugging code in the SGI SN (Scalable NUMA) platform for IA64. Unless you are debugging problems on an SGI SN IA64 box, say N. Enable SGI Medusa Simulator Support CONFIG_IA64_SGI_SN_SIM If you are compiling a kernel that will run under SGI's IA64 simulator (Medusa) then say Y, otherwise say N. PCIBA Support CONFIG_PCIBA IRIX PCIBA-inspired user mode PCI interface for the SGI SN (Scalable NUMA) platform for IA64. Unless you are compiling a kernel for an SGI SN IA64 box, say N. Enable protocol mode for the L1 console SERIAL_SGI_L1_PROTOCOL Uses protocol mode instead of raw mode for the level 1 console on the SGI SN (Scalable NUMA) platform for IA64. If you are compiling for an SGI SN box then Y is the recommended value, otherwise say N. Directly Connected Compact Flash support CONFIG_CF_ENABLER Compact Flash is a small, removable mass storage device introduced in 1994 originally as a PCMCIA device. If you say `Y' here, you compile in support for Compact Flash devices directly connected to a SuperH processor. A Compact Flash FAQ is available at . If your board has "Directly Connected" CompactFlash at area 5 or 6, you may want to enable this option. Then, you can use CF as primary IDE drive (only tested for SanDisk). If in doubt, select 'N'. Kernel debugging CONFIG_DEBUG_KERNEL Say Y here if you are developing drivers or trying to debug and identify kernel problems. Debug memory allocations CONFIG_DEBUG_SLAB Say Y here to have the kernel do limited verification on memory allocation as well as poisoning memory on free to catch use of freed memory. Memory mapped I/O debugging CONFIG_DEBUG_IOVIRT Say Y here to get warned whenever an attempt is made to do I/O on obviously invalid addresses such as those generated when ioremap() calls are forgotten. Memory mapped I/O will go through an extra check to catch access to unmapped ISA addresses, an access method that can still be used by old drivers that are being ported from 2.0/2.2. Spinlock debugging CONFIG_DEBUG_SPINLOCK Say Y here and build SMP to catch missing spinlock initialization and certain other kinds of spinlock errors commonly made. This is best used in conjunction with the NMI watchdog so that spinlock deadlocks are also debuggable. Read-write spinlock debugging CONFIG_DEBUG_RWLOCK If you say Y here then read-write lock processing will count how many times it has tried to get the lock and issue an error message after too many attempts. If you suspect a rwlock problem or a kernel hacker asks for this option then say Y. Otherwise say N. Semaphore debugging CONFIG_DEBUG_SEMAPHORE If you say Y here then semaphore processing will issue lots of verbose debugging messages. If you suspect a semaphore problem or a kernel hacker asks for this option then say Y. Otherwise say N. Verbose BUG() reporting (adds 70K) CONFIG_DEBUG_BUGVERBOSE Say Y here to make BUG() panics output the file name and line number of the BUG call as well as the EIP and oops trace. This aids debugging but costs about 70-100K of memory. Include kgdb kernel debugger CONFIG_KGDB Include in-kernel hooks for kgdb, the Linux kernel source level debugger. This project has a web page at . Include xmon kernel debugger CONFIG_XMON 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. To learn more about the Abatron BDI2000, visit the web page at . 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. Include kgdb kernel debugger CONFIG_KWDB Include in-kernel hooks for kdb, the source level debugger for the PA-RISC port. IODC console CONFIG_IODC_CONSOLE IODC is HP's pre-PCI standard for device identification (a la PCI vendor, device IDs), detection, configuration, initialization and so on. It also can provide firmware function to do the actual IO, which are slow, not really defined for runtime usage and generally not desirable. See for the gory details. Say Y here to enable use of the IODC firmware functions for console I/O. This is only useful on older PA-RISC workstations. If in doubt, say Y. U2/Uturn I/O MMU CONFIG_IOMMU_CCIO Say Y here to enable DMA management routines for the first generation of PA-RISC cache-coherent machines. Programs the U2/Uturn chip in "Virtual Mode" and use the I/O MMU. LBA/Elroy PCI support CONFIG_PCI_LBA Say Y here to give the PA-RISC kernel access to PCI configuration and IO-port space on PA-RISC workstations equipped with a Lower Bus Adapter (LBA). This includes A, B, C, J, L, and N-class machines with 4-digit model numbers, also the A300. LASI I/O support CONFIG_GSC_LASI Say Y here to directly support the LASI controller chip found on PA-RISC workstations. Linux-oriented documentation for this chip can be found at . LASI/ASP builtin parallel-port CONFIG_PARPORT_GSC Say Y here to build in low-level parallel-support for PC-style hardware integrated in the LASI-Controller (on the GSC Bus) for HP-PARISC workstations. Fujitsu Vendor Specific CONFIG_BLK_DEV_IDEDISK_FUJITSU Enable vendor-specific code for Fujitsu IDE disks. Unless you are the IDE maintainer, you probably do not want to mess with this. IBM Vendor Specific CONFIG_BLK_DEV_IDEDISK_IBM Enable vendor-specific code for IBM IDE disks. Unless you are the IDE maintainer, you probably do not want to mess with this. Maxtor Vendor Specific CONFIG_BLK_DEV_IDEDISK_MAXTOR Enable vendor-specific code for Maxtor IDE disks. Unless you are the IDE maintainer, you probably do not want to mess with this. Quantum Vendor Specific CONFIG_BLK_DEV_IDEDISK_QUANTUM Enable vendor-specific code for Quantum IDE disks. Unless you are the IDE maintainer, you probably do not want to mess with this. Seagate Vendor Specific CONFIG_BLK_DEV_IDEDISK_SEAGATE Enable vendor-specific code for Seagate IDE disks. Unless you are the IDE maintainer, you probably do not want to mess with this. Western Digital Vendor Specific CONFIG_BLK_DEV_IDEDISK_WD Enable vendor-specific code for Western Digital IDE disks. Unless you are the IDE maintainer, you probably do not want to mess with this. TiVo Commerial Application Specific CONFIG_BLK_DEV_TIVO Enable vendor-specific code for TiVo IDE disks. Unless you are the IDE maintainer, you probably do not want to mess with this. # Choice: superhsys Generic CONFIG_SH_GENERIC Select Generic if configuring for a generic SuperH system. The "generic" option compiles in *all* the possible hardware support and relies on the sh_mv= kernel command option to choose at runtime which routines to use. "MV" stands for "machine vector"; each of the machines below is described by a machine vector. Select SolutionEngine if configuring for a Hitachi SH7709 or SH7750/7750S evaluation board. Select Overdrive if configuring for a ST407750 Overdrive board. More information at . Select HP620 if configuring for a HP Jornada HP620. More information (hardware only) at . Select HP680 if configuring for a HP Jornada HP680. More information (hardware only) at . Select HP690 if configuring for a HP Jornada HP690. More information (hardware only) at . Select CqREEK if configuring for a CqREEK SH7708 or SH7750. More information at . Select DMIDA if configuring for a DataMyte 4000 Industrial Digital Assistant. More information at . Select EC3104 if configuring for a system with an Eclipse International EC3104 chip, e.g. the Harris AD2000 or Compaq Aero 8000. Select Dreamcast if configuring for a SEGA Dreamcast. More information at . There is a Dreamcast project is at . Select BareCPU if you know what this means, and it applies to your system. # These may have to be merged in when we go to CML2: # - "SolutionEngine7751" for Hitachi SolutionEngine (7751) # - "STB1_Harp" for STMicroelectronics HARP # - "CqREEK" for CQ Publishing CqREEK SH-4 # - "CAT68701" for CAT 68701 Evaluation Board (SH7708) # - "BigSur" for Big Sur Evaluation Board # - "SH2000" for SH2000 Evaluation Board (SH7709A) # - "ADX" for A&D ADX SolutionEngine CONFIG_SH_SOLUTION_ENGINE Select SolutionEngine if configuring for a Hitachi SH7709 or SH7750 evaluation board. 7751 SolutionEngine CONFIG_SH_7751_SOLUTION_ENGINE Select 7751 SolutionEngine if configuring for a Hitachi SH7751 evaluation board. Overdrive CONFIG_SH_OVERDRIVE Select Overdrive if configuring for a ST407750 Overdrive board. More information at . HP620 CONFIG_SH_HP620 Select HP620 if configuring for a HP jornada HP620. More information (hardware only) at . HP680 CONFIG_SH_HP680 Select HP680 if configuring for a HP Jornada HP680. More information (hardware only) at . HP690 CONFIG_SH_HP690 Select HP690 if configuring for a HP Jornada HP690. More information (hardware only) at . CqREEK CONFIG_SH_CQREEK Select CqREEK if configuring for a CqREEK SH7708 or SH7750. More information at . DMIDA CONFIG_SH_DMIDA Select DMIDA if configuring for a DataMyte 4000 Industrial Digital Assistant. More information at . EC3104 CONFIG_SH_EC3104 Select EC3104 if configuring for a system with an Eclipse International EC3104 chip, e.g. the Harris AD2000. Dreamcast CONFIG_SH_DREAMCAST Select Dreamcast if configuring for a SEGA Dreamcast. More information at . There is a Dreamcast project is at . BareCPU CONFIG_SH_UNKNOWN "Bare CPU" aka "unknown" means an SH-based system which is not one of the specific ones mentioned above, which means you need to enter all sorts of stuff like CONFIG_MEMORY_START because the config system doesn't already know what it is. You get a machine vector without any platform-specific code in it, so things like the RTC may not work. This option is for the early stages of porting to a new machine. # Choice: superhtype SH7707 CONFIG_CPU_SUBTYPE_SH7707 Select the type of SuperH processor you have. This information is used for optimizing and configuration purposes. Select SH7707 if you have a 60 Mhz SH-3 HD6417707 CPU. Select SH7708 if you have a 60 Mhz SH-3 HD6417708S or if you have a 100 Mhz SH-3 HD6417708R CPU. Select SH7709 if you have a 80 Mhz SH-3 HD6417709 CPU. Select SH7750 if you have a 200 Mhz SH-4 HD6417750 CPU. Select SH7751 if you have a SH7751 Select ST40STB1 if you have a ST40STB1 SH7708 CONFIG_CPU_SUBTYPE_SH7708 Select SH7708 if you have a 60 Mhz SH-3 HD6417708S or if you have a 100 Mhz SH-3 HD6417708R CPU. SH7709 CONFIG_CPU_SUBTYPE_SH7709 Select SH7709 if you have a 80 Mhz SH-3 HD6417709 CPU. SH7750 CONFIG_CPU_SUBTYPE_SH7750 Select SH7750 if you have a 200 Mhz SH-4 HD6417750 CPU. Physical memory start address CONFIG_MEMORY_START Computers built with Hitachi SuperH processors always map the ROM starting at address zero. But the processor does not specify the range that RAM takes. The physical memory (RAM) start address will be automatically set to 08000000, unless you selected one of the following processor types: SolutionEngine, Overdrive, HP620, HP680, HP690, in which case the start address will be set to 0c000000. Tweak this only when porting to a new machine which is not already known by the config system. Changing it from the known correct value on any of the known systems will only lead to disaster. Hitachi HD64461 companion chip support CONFIG_HD64461 The Hitachi HD64461 provides an interface for the SH7709 CPU, supporting a LCD controller, CRT color controller, IrDA up to 4 Mbps, and a PCMCIA controller supporting 2 slots. More information is available at . Say Y if you want support for the HD64461. Otherwise, say N. HD64461 PCMCIA enabler CONFIG_HD64461_ENABLER Say Y here if you want to enable PCMCIA support via the HD64461 companion chip. Otherwise, say N. HD64461 virtualized IRQ number CONFIG_HD64461_IRQ The default setting of the HD64461 IRQ is 36. Do not change this unless you know what you are doing. Hitachi HD64465 companion chip support CONFIG_HD64465 The Hitachi HD64465 provides an interface for the SH7750 CPU, supporting a LCD controller, CRT color controller, IrDA, USB, PCMCIA, keyboard controller, and a printer interface. More information is available at . Say Y if you want support for the HD64465. Otherwise, say N. HD64465 virtualized IRQ number CONFIG_HD64465_IRQ The default setting of the HD64465 IRQ is 5. Do not change this unless you know what you are doing. HD64465 start address CONFIG_HD64465_IOBASE The default setting of the HD64465 IO base address is 0xb0000000. Do not change this unless you know what you are doing. Early printk support CONFIG_SH_EARLY_PRINTK Say Y here to redirect kernel printk messages to the serial port used by the SH-IPL bootloader, starting very early in the boot process and ending when the kernel's serial console is initialised. This option is only useful porting the kernel to a new machine, when the kernel may crash or hang before the serial console is initialised. If unsure, say N. SuperH SCI (serial) support CONFIG_SH_SCI Selecting this option will allow the Linux kernel to transfer data over SCI (Serial Communication Interface) and/or SCIF (Serial Communication Interface with FIFO) which are built into the Hitachi SuperH processor. The option provides 1 to 3 (depending on the CPU model) standard Linux tty devices, /dev/ttySC[012]; one of these is normally used as the system console. If in doubt, press "y". Use LinuxSH standard BIOS CONFIG_SH_STANDARD_BIOS Say Y here if your target has the gdb-sh-stub package from www.m17n.org (or any conforming standard LinuxSH BIOS) in FLASH or EPROM. The kernel will use standard BIOS calls during boot for various housekeeping tasks (including calls to read and write characters to a system console, get a MAC address from an on-board Ethernet interface, and shut down the hardware). Note this does not work with machines with an existing operating system in mask ROM and no flash (WindowsCE machines fall in this category). If unsure, say N. GDB Stub kernel debug CONFIG_DEBUG_KERNEL_WITH_GDB_STUB If you say Y here, it will be possible to remotely debug the SuperH kernel using gdb, if you have the gdb-sh-stub package from www.m17n.org (or any conforming standard LinuxSH BIOS) in FLASH or EPROM. This enlarges your kernel image disk size by several megabytes but allows you to load, run and debug the kernel image remotely using gdb. This is only useful for kernel hackers. If unsure, say N. 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'. 802.1Q VLAN Support CONFIG_VLAN_8021Q Select this and you will be able to create 802.1Q VLAN interfaces on your ethernet interfaces. 802.1Q VLAN supports almost everything a regular ethernet interface does, including firewalling, bridging, and of course IP traffic. You will need the 'vconfig' tool from the VLAN project in order to effectively use VLANs. See the VLAN web page for more information: If unsure, you can safely say 'N'. ARC console support CONFIG_ARC_CONSOLE Support for the PROM-based console on MIPS machines built according to the Advanced Risc Computing specification, which is now (2001) dead. These included boxes from Deskstation, Acer, Olivetti and NEC. There is a history at . AUTCPU12 CONFIG_ARCH_AUTCPU12 Say Y if you intend to run the kernel on the autronix autcpu12 board. This board is based on a Cirrus Logic CS89712. IT8172 IDE support CONFIG_BLK_DEV_IT8172 Say Y here to support the on-board IDE controller on the Integrated Technology Express, Inc. ITE8172 SBC. Vendor page at ; picture of the board at . Support ARM926T processor CONFIG_CPU_ARM926T This is a variant of the ARM920. It has slightly different instruction sequences for cache and TLB operations. Curiously, there is no documentation on it at the ARM corporate website. Say Y if you want support for the ARM926T processor. Otherwise, say N. Support CPU clock change (EXPERIMENTAL) CONFIG_CPU_FREQ CPU clock scaling allows you to change the clock speed of the running CPU on the fly. This is a nice method to save battery power, because the lower the clock speed, the less power the CPU consumes. Note that this driver doesn't automatically change the CPU clock speed, you need some userland tools (which still have to be written) to implement the policy. If you don't understand what this is all about, it's safe to say 'N'. SiS CONFIG_DRM_SIS Choose this option if you have a SIS graphics card. AGP support is required for this driver to work. Etrax Ethernet slave support (over lp0/1) CONFIG_ETRAX_ETHERNET_LPSLAVE This option enables a slave ETRAX 100 or ETRAX 100LX, connected to a master ETRAX 100 or ETRAX 100LX through par0 and par1, to act as an Ethernet controller. Slave has its own LEDs CONFIG_ETRAX_ETHERNET_LPSLAVE_HAS_LEDS Enable if the slave has it's own LEDs. ATA/IDE support CONFIG_ETRAX_IDE Enable this to get support for ATA/IDE. You can't use parallel ports or SCSI ports at the same time. LED on when link CONFIG_ETRAX_NETWORK_LED_ON_WHEN_LINK Selecting LED_on_when_link will light the LED when there is a connection and will flash off when there is activity. Selecting LED_on_when_activity will light the LED only when there is activity. This setting will also affect the behaviour of other activity LEDs e.g. Bluetooth. Power button bit on port G CONFIG_ETRAX_POWERBUTTON_BIT Configure where power button is connected. Root device name CONFIG_ETRAX_ROOT_DEVICE Specifies the device that should be mounted as root file system when booting from flash. The axisflashmap driver adds an additional mtd partition for the appended root file system image, so this option should normally be the mtdblock device for the partition after the last partition in the partition table. Serial port 0 enabled CONFIG_ETRAX_SERIAL_PORT0 Enables the ETRAX 100 serial driver for ser0 (ttyS0) Normally you want this on, unless you use external DMA 1 that uses the same DMA channels. Shutdown bit on port CSP0 CONFIG_ETRAX_SHUTDOWN_BIT Configure what pin on CSPO-port that is used for controlling power supply. Software Shutdown Support CONFIG_ETRAX_SOFT_SHUTDOWN Enable this if Etrax is used with a power-supply that can be turned off and on with PS_ON signal. Gives the possibility to detect powerbutton and then do a power off after unmounting disks. Disable watchdog during Oops printouts CONFIG_ETRAX_WATCHDOG_NICE_DOGGY By enabling this you make sure that the watchdog does not bite while printing oopses. Recommended for development systems but not for production releases. Compaq iPAQ Handheld sleeve support CONFIG_H3600_SLEEVE Choose this option to enable support for extension packs (sleeves) for the Compaq iPAQ H3XXX series of handheld computers. This option is required for the CF, PCMCIA, Bluetooth and GSM/GPRS extension packs. AVM Fritz!Card PCI/PCIv2/PnP support (EXPERIMENTAL) CONFIG_HISAX_FRITZ_PCIPNP This enables the driver for the AVM Fritz!Card PCI, Fritz!Card PCI v2 and Fritz!Card PnP. (the latter also needs you to select "ISA Plug and Play support" from the menu "Plug and Play configuration") IBM PCI Hotplug driver CONFIG_HOTPLUG_PCI_IBM Say Y here if you have a motherboard with a IBM PCI Hotplug controller. This code 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 cpqphp.o. If you want to compile it as a module, say M here and read Documentation/modules.txt. When in doubt, say N. Enable autotest (llsc). Option to run cache test instead of booting CONFIG_IA64_SGI_AUTOTEST Build a kernel used for hardware validation. If you include the keyword "autotest" on the boot command line, the kernel does NOT boot. Instead, it starts all cpus and runs cache coherency tests instead. If unsure, say N. IEC61883-6 (Audio transmission) support CONFIG_IEEE1394_AMDTP This option enables the Audio & Music Data Transmission Protocol (IEC61883-6) driver, which implements audio transmission over IEEE1394. The userspace interface is documented in amdtp.h. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called amdtp.o. IEC61883-1 Plug support CONFIG_IEEE1394_CMP This option enables the Connection Management Procedures (IEC61883-1) driver, which implements input and output plugs. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called amdtp.o. OHCI-DV I/O support CONFIG_IEEE1394_DV1394 This driver allows you to transmit and receive DV (digital video) streams on an OHCI-1394 card using a simple frame-oriented interface. The user-space API for dv1394 is documented in dv1394.h. If you want to compile this as a module ( = code which can be inserted in and removed from the running kernel whenever you want), say M here and read Documentation/modules.txt. The module will be called dv1394.o. Ethernet over 1394 CONFIG_IEEE1394_ETH1394 Extremely Experimental! This driver is a Linux specific way to use your IEEE1394 Host as an Ethernet type device. This is _NOT_ IP1394. Support for older IT8172 (Rev C) CONFIG_IT8172_REVC Say Y here to support the older, Revision C version of the Integrated Technology Express, Inc. ITE8172 SBC. Vendor page at ; picture of the board at . Enable Smart Card Reader 0 Support CONFIG_IT8172_SCR0 Say Y here to support smart-card reader 0 (SCR0) on the Integrated Technology Express, Inc. ITE8172 SBC. Vendor page at ; picture of the board at . Enable Smart Card Reader 1 Support CONFIG_IT8172_SCR1 Say Y here to support smart-card reader 1 (SCR1) on the Integrated Technology Express, Inc. ITE8172 SBC. Vendor page at ; picture of the board at . IT8172 IDE Tuning support CONFIG_IT8172_TUNING Say Y here to support tuning the ITE8172's IDE interface. This makes it possible to set DMA channel or PIO opration and the transfer rate. Enable protocol mode for the L1 console CONFIG_SERIAL_SGI_L1_PROTOCOL Uses protocol mode instead of raw mode for the level 1 console on the SGI SN (Scalable NUMA) platform for IA64. If you are compiling for an SGI SN box then Y is the recommended value, otherwise say N. New bus configuration (EXPERIMENTAL) CONFIG_TULIP_MWI This configures your Tulip card specifically for the card and system cache line size type you are using. This is experimental code, not yet tested on many boards. If unsure, say N. # # A couple of things I keep forgetting: # capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet, # Intel, IRQ, ISDN, Linux, MSDOS, NetWare, NetWinder, # NFS, PCI, SCSI, SPARC # two words: file system, hard drive, hard disk, home page, # user space, web site # other: it's safe to save; daemon; use --, not - or ---; # use KB for 1024 bytes, not kB or K. # # # This is used by Emacs' spell checker ispell.el: # # LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp ibiblio # LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz # LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd # LocalWords: HD CD-ROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN # LocalWords: ISA EISA Microchannel VESA BIOSes IPC SYSVIPC ipc Ctrl dmesg hlt # LocalWords: BINFMT Linkable http ac uk jo html GCC SPARC AVANTI CABRIOLET EB # LocalWords: netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP # LocalWords: genksyms INET loopback gatewaying Ethernet PPP ARP Arp MEMSIZE # LocalWords: howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip # LocalWords: proc acct IPIP encapsulator decapsulator klogd RARP EXT PS # LocalWords: telnetting subnetted NAGLE rlogin NOSR ttyS TGA techinfo mbone nl # LocalWords: Mb SKB IPX Novell dosemu DDP ATALK vmalloc visar ehome # LocalWords: SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA # LocalWords: buslogic DMA DPT ATT eata dma PIO UltraStor fdomain umsdos ext # LocalWords: QLOGIC qlogic TMC seagate Trantor ultrastor FASST wd NETDEVICES # LocalWords: unix BBS linux CSLIP PLIP Kirch's LDP CSlip SL SCC IRQ csustan # LocalWords: Turbo Laplink plip NCSA port's ReQuest IRQs EQL SMC AMD PCnet NE # LocalWords: COM ELPLUS Com EtherLinkIII VLB Arcnet Cabletron DEPCA DE carlos # LocalWords: depca EtherWorks EWRK ewrk SEEQ EtherExpress EEXPRESS NI xxx dia # LocalWords: EtherExpress WaveLAN wavelan PCLAN HPLAN VG SK Ansel Xen de ZNET # LocalWords: PCMCIA cb stanford LAN TEC RealTek ATP atp DLINK NetTools VISWS # LocalWords: TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA # LocalWords: Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech # LocalWords: Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs # LocalWords: LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos mtools Cichocki # LocalWords: std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI # LocalWords: hpfs SYSV SCO iBCS Wyse WordPerfect tsx mit unixes sysv NR irisa # LocalWords: SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST # LocalWords: PSMOUSE Compaq trackballs Travelmate Inport ATIXL ATI busmice ld # LocalWords: gpm config QIC DYNCONF FTAPE Stor Ftape ftape pcsndrv manpage NT # LocalWords: readprofile diskdrives org com masq EtherTalk tcp netrom sunacm # LocalWords: misc AIC aic pio scc Portmaster eql GIS PhotoCDs MCDX Perell PG # LocalWords: mcdx gscd optcd sjcd ISP hdparm Workgroups Lan samba PARIDE PCD # LocalWords: filesystems smbfs ATA ppp PCTech RZ www powerquest txt CMD ESDI # LocalWords: chipset FB multicast MROUTE appletalk ifconfig IBMTR multiport # LocalWords: Multisession STALDRV EasyIO EC EasyConnection ISTALLION ONboard # LocalWords: Brumby pci TNC cis ohio faq usenet NETLINK dev hydra ca Tyne mem # LocalWords: carleton DECstation SUNFD JENSEN Noname XXXM SLiRP LILO's amifb # LocalWords: pppd Zilog ZS SRM bootloader ez mainmenu rarp ipfwadm paride pcd # LocalWords: RTNETLINK mknod xos MTU lwared Macs netatalk macs cs Wolff # LocalWords: dartmouth flowerpt MultiMaster FlashPoint tudelft etherexpress # LocalWords: ICL EtherTeam ETH IDESCSI TXC SmartRAID SmartCache httpd sjc dlp # LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ MG HIPPI cern # LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX # LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa # LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite # LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrtools pg # LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT # LocalWords: kerneld callouts AdvanSys advansys Admin WDT DataStor EP verden # LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI # LocalWords: QD qd UMC umc ALI ali lena fnet fr azstarnet cdr fb MDA ps esdi # LocalWords: Avanti XL AlphaStations Jensen DECpc AXPpci UDB Cabriolet MCA RC # LocalWords: AlphaPC mca AOUT OUTput PPro sipx gwdg lo nwe FourPort Boca unm # LocalWords: Keepalive linefill RELCOM keepalive analogue CDR conf CDI INIT # LocalWords: OPTi isp irq noisp VFAT vfat NTFS losetup dmsdosfs dosfs ISDN MP # LocalWords: NOWAYOUT behaviour dialin isdn callback BTX Teles XXXX LVM lvm # LocalWords: ICN EDSS Cisco # LocalWords: ipppd syncppp RFC MPP VJ downloaded icn NICCY Creatix shmem ufr # LocalWords: ibp md ARCnet ether encap NDIS arcether ODI Amigas AmiTCP NetBSD # LocalWords: initrd tue util DES funet des OnNet BIOSP smc Travan Iomega CMS # LocalWords: FC DC dc PPA IOMEGA's ppa RNFS FMV Fujitsu ARPD arpd loran layes # LocalWords: FRAD indiana framerelay DLCI DCLIs Sangoma SDLA mrouted sync sec # LocalWords: Starmode Metricom MosquitoNet mosquitonet kbit nfsroot Digiboard # LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu Ethernets HBAs MEX # LocalWords: Shifflett netcom js jshiffle WIC DECchip ELCP EtherPower dst RTC # LocalWords: rtc SMP lp Digi Intl RightSwitch DGRS dgrs AFFS Amiga UFS SDL AP # LocalWords: Solaris RISCom riscom syncPPP PCBIT pcbit sparc anu au artoo MFB # LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCD-ROM FreeBSD NeXT # LocalWords: NeXTstep disklabel disklabels SMD FFS tm AmigaOS diskfiles Un IQ # LocalWords: Bernd informatik rwth aachen uae affs multihosting bytecode java # LocalWords: applets applet JDK ncsa cabi SNI Alphatronix readme LANs scarab # LocalWords: winsock RNIS caltech OSPF honour Honouring Mbit LocalTalk DEFRAG # LocalWords: localtalk download Packetwin Baycom baycom interwork ASCII JNT # LocalWords: Camtec proxying indyramp defragment defragmented UDP FAS FASXX # LocalWords: FastSCSI SIO FDC qlogicfas QLogic qlogicisp setbaycom ife ee LJ # LocalWords: ethz ch Travelmates ProAudioSpectrum ProAudio SoundMan SB SBPro # LocalWords: Thunderboard SM OPL FM ADLIB TSR Gravis MPU PSS ADI SW DSP codec # LocalWords: ADSP ESC ASIC daughtercard GUSMAX MSS NX AdLib Excell Ensoniq YM # LocalWords: SoundScape Spea MediaTriX AudioTriX WSS OTI ThunderBoard VoxWare # LocalWords: Soundscape SSCAPE TRIX MediaTrix PnP Maui dsp midixx EIA getty # LocalWords: mgetty sendfax gert greenie muc lowlevel Lasermate LanManager io # LocalWords: OOPSes trackball binghamton mobileip ncr IOMAPPED settags ns ser # LocalWords: setsync NEGO MPARITY autotuning prefetch PIIX cdwrite utils rc # LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu # LocalWords: YAMADA tetsu cauchy nslab ntt nevod perm su doc kaf kheops wsc # LocalWords: traduc Bourgin dbourgin menuconfig kfill READMEs HOWTOs Virge WA # LocalWords: IDEDISK IDEFLOPPY EIDE firewalls QMAGIC ZMAGIC LocalWords opti # LocalWords: SVGATextMode vga svga Xkernel syr jmwobus comfaqs dhcp flakey GD # LocalWords: IPv IPng interoperability ipng ipv radio's tapr pkthome PLP nano # LocalWords: Ses Mhz sethdlc SOUNDMODEM WindowsSoundSystem smdiag pcf inka ES # LocalWords: smmixer ptt circ soundmodem MKISS FDDI DEFEA DEFPA DEFXX redhat # LocalWords: HyperNews khg mconv sed lina wuftpd MicroChannel netlink irc cum # LocalWords: raudio RealAudio PPROP NETBIOS GUI IBMMCA ELMC Racal Interlan fi # LocalWords: eth shapecfg src esp PCWD PREVSTAT bootparam sig bitwizard SBC # LocalWords: downloads AFSK TCM FP Karn KA FSK RUH LinkSys cron mouseman LLC # LocalWords: SyQuest SyQuest's CCITT MicroSolutions BPCD bpcd ESPSERIAL PROM # LocalWords: SUNESP openprom OPENPROMIO quango themall al TT MC MMU LC RMW AA # LocalWords: INSNS Ataris AutoConfig ZORRO OCS AMIFB Agnus Denise ECS CDTV GB # LocalWords: AGA Cybervision CYBER GSP TMS DMI Zorro ACSI ROMs SLM BioNet GVP # LocalWords: PAMsNet TekMagic Cyberstorm MkI CYBERSTORMII MkII BLZ onboard cx # LocalWords: Village Tronic ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB # LocalWords: Rhotron BioData's Multiface AMIGAMOUSE COPCON Amiga's bitplanes # LocalWords: ATARIMOUSE MFPSER SCC's MegaSTE ESCC Atari's GVPIOEXT DMASOUND # LocalWords: fdutils cisco univercd rpcg htm iface lapb LAPBETHER tpqic qic # LocalWords: SYNTH xd en binfmt aout ipip terra ipx sd sr sg wic framebuffer # LocalWords: ibmmca lapbether mkiss dlci sdla fmv eepro eexpress ni hp ne es # LocalWords: ibmtr isofs ROMFS romfs pcxx cyclades istallion psaux msbusmouse # LocalWords: atixlmouse sbin softdog pcwd USS Lite ACI miroSOUND PCM miroPCM # LocalWords: microcontroller miro Voxware downloading teles acsi slm gvp ltpc # LocalWords: atari ariadne amigamouse atarimouse builtin IPDDP maths bradford # LocalWords: AppleTalk Farallon PhoneNet Zubkoff lnz SCCB HAPN WANs vesafb nt # LocalWords: wanrouter WANPIPE multiprotocol Mbps wanpipe EtherWORKS nodma SC # LocalWords: smp HiSax SiemensChipSet Siemens AVM Elsa ITK hisax PCC MICROR # LocalWords: Mircolink EURO DSS Spellcaster BRI sc spellcast Digiboards GPIO # LocalWords: SYMBIOS COMPAT SDMS rev ASUS Tekram HX VX API ibmmcascsi ASY asy # LocalWords: loader's PCnetPCI automounter AUTOFS amd autofs VT Gallant's Pnp # LocalWords: AEDSP aedsp enskip tik Sysctl sysctl PARPORT parport pnp IDs EPP # LocalWords: Autoprobe bart patrickr HDLS READBACK AB usr DAMA DS SparQ aten # LocalWords: Symbios PCscsi tmscsim RoamAbout GHz Hinds contrib mathematik ok # LocalWords: darmstadt okir DIGIEPCA International's Xem digiepca epca bootup # LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk # LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls # LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james # LocalWords: caldera Preload Preloading slowdowns schoebel uni NBD nbd prog # LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD # LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid # LocalWords: adm Nodename hostname uname Kernelname bootp nmi DI OV StegFS # LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt RX mdafb # LocalWords: dataless kerneltype SYSNAME Comtrol Rocketport palmtop fbset EGS # LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY # LocalWords: Sitor Amtor Pactor GTOR hayes TX TMOUT JFdocs BIGMEM DAC IRQ's # LocalWords: IDEPCI IDEDMA PDC pdc TRM trm raidtools luthien nuclecu BAGET VR # LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS # LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE # LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM # LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd # LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate # LocalWords: ipddp Decapsulation DECAP bool HAMRADIO tcpdump af CDs tx FBCON # LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio bpp # LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO # LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate # LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched # LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW # LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC # LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian # LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ # LocalWords: Valencian Slovene Esperanto Estonian Latvian Belarusian KOI mt # LocalWords: charset Inuit Greenlandic Sami Lappish koi Alexey Kuznetsov's sa # LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr # LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb # LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer # LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB # LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax # LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev # LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS # LocalWords: pms Avatar Freecom Imation Superdisk BPCK bpck COMM comm DSTR ru # LocalWords: dstr EPAT EPEZ epat EPIA epia FreeCom FRPW frpw KingByte KBIC HW # LocalWords: KingByte's kbic OnSpec ValuStore FASTROUTE fastroute FLOWCONTROL # LocalWords: struct APIC realtime OSs LynxOS CNC tmp cvf HFS hfs ADFS Risc os # LocalWords: adfs ncpmount namespace SUBDIR reexport NDS kcore FT SPX spx DAT # LocalWords: interserver BLKSZ NUMBUFFERS apmd Tadpole ANA roestock QuickCam # LocalWords: isapnptools Colour CQCAM colour Connectix QuickClip prive mentre # LocalWords: KMOD kmod conformant utexas kharker UnixWare Mwave cgi cl ts ibm # LocalWords: eXchange threepio oakland simtel pre ULTRAMCA EtherLink isa luik # LocalWords: EtherLink OpenBSD pts DEVPTS devpts ptmx ttyp glibc readback SA # LocalWords: mwave OLDCARD isdnloop linklevel loopctrl Eicon Diehl DIEHLDIVA # LocalWords: ASUSCOM AsusCom TELEINT semiactiv Sedlbauer Sportster TA MIC ITH # LocalWords: NETjet NetJet Niccy Neuhaus sparcs AOC AOCD AOCE Microlink SAA # LocalWords: teletext WinTV saa iproute tc Quadra Performa PowerBook tor AUN # LocalWords: setserial compsoc steve Econet econet AUNUDP psched TEQL TLE CLS # LocalWords: teql FW Ingres TwistedPair MTRR MTRRs mtrr cfs crypto TD ktti KT # LocalWords: PHd ICS ipchains adelaide rustcorp syslog Cumana steganography # LocalWords: AcornSCSI EcoSCSI EESOX EESOXSCSI Powertec POWERTECSCSI dec SF # LocalWords: RadioReveal gatekeeper aimslab aztech FMI sf fmi RTL rtl cesdis # LocalWords: Yellowfin gsfc nasa gov yellowfin pcnet Mylex LNE lne EtherH hs # LocalWords: EBSA chattr RiscOS Winmodem AGP Atomwide DUALSP pcsp robinson CT # LocalWords: SGALAXY Waverider DSPxxx TRXPRO AudioTrix OSWF MOT CFB DSY kbps # LocalWords: tuwien kkudielk LVD mega lun MAXTAGS Gbps arcnet Olicom SNA PAE # LocalWords: SysKonnect tms sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX # LocalWords: MSNDINIT MSNDPERM MSNDPIN PNDSPINI PNDSPERM Ensoniq's RetinaZ SS # LocalWords: AudioPCI lspci SonicVibes sonicvibes SPARCs roadrunner CLgen UPA # LocalWords: swansea shtml Zoltrix zoltrix BINUTILS EGCS binutils VIDC DACs # LocalWords: CyberVision Cirrus PowerBooks Topcat SBUS CGsix TurboGX BWtwo SS # LocalWords: CGthree TCX unswappable vfb fbcon hicolor truecolor AFB ILBM SOC # LocalWords: IPLAN gracilis Fibre SBus SparcSTORAGE SV jnewbigin swin QNX qnx # LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss pvv kerneli hd # LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX Nx # LocalWords: PowerMac's BMAC radiotrack rtrack miropcm OFFBOARD HPT UDMA DVD # LocalWords: hpt fokus gmd Cyrix DXL SLC DLC NexGen MediaGX GXm IDT WinChip # LocalWords: MMX MII valkyrie mdacon vdolive VDOLive cuseeme CU hippi rrunner # LocalWords: SeeMe ipmasqadm juanjox ipmarkfw markfw TNCs Microdyne rhine lib # LocalWords: libc jsX gamepad gameport CHF FCS FPGaming MadCatz ASSASIN GrIP # LocalWords: Assasin gamepads GamePad PDPI gamecards gamecard WingMan BSP WCS # LocalWords: ThunderPad CyberMan SideWinder ThrustMaster DirectConnect NES XF # LocalWords: Millenium SNES PSX Multisystem Nintendo PlayStation Amstrad CPC # LocalWords: Sega TurboGraFX Steffen Schwenke Multiststem PDIF FIFOSIZE EPLUS # LocalWords: PowerUP RoadRunner tahallah dos functionkey setterm imladris Woz # LocalWords: PowerMacs Winbond Algorithmics ALGOR algor ECOFF IRIX SGI SGI's # LocalWords: gfx virtualized Xpmac mklinux XFree FBDev Woodhouse mvhi Seeq fp # LocalWords: SGISEEQ HIgh ADB ADBMOUSE crosscompiler CROSSCOMPILE FPE GDB gdb # LocalWords: JOYPORT rp spoofing DawiControl NOGENSUPP EEPROM HSSI Alessandro # LocalWords: singleprocessor tex MATHEMU FRIQ Maxell friq Alcor XLT AlphaBook # LocalWords: AlphaPCI DP LX Miata Mikasa Noritake RPX UX BX Takara EV PRIMO # LocalWords: TSC Matrox Productiva matroxfb matrox multihead ia linuxhq MFW # LocalWords: mfw AAA MCS Initio XXU initio imm AutoDetect IZIP CTR usec HDLC # LocalWords: COSA SRP muni cz kas cosa Alteon AceNIC acenic VTOC OSes GMT SAx # LocalWords: Inspiron localtime INTS Thinkpads Ralf Brown's Flightstick NNN # LocalWords: Xterminator Blackhawk NN mpu ioports DCA HPDCA HPLANCE DIO Corel # LocalWords: GemTek gemtek CMDLINE IrDA PDA's irmanager irattach RR AVA DN rg # LocalWords: uit dagb irda LSAP IrLMP RR's IrLAP IR alloc skb's kfree skb's # LocalWords: GZIP IrLAN NetbeamIR ESI JetEye IrOBEX IrCOMM TTY's minicom dti # LocalWords: ircomm ircomm pluto thiguchi IrTTY Linux's bps NetWinder MIR NSC # LocalWords: ACTiSYS dongle dongles esi actisys IrMate tekram BVM MVME # LocalWords: BVME BVME WRITETHROUGH copyback writethrough fwmark syncookie tu # LocalWords: alphalinux GOBIOS csn chemnitz nat ACARD AMI MegaRAID megaraid # LocalWords: QNXFS ISI isicom xterms Apollos VPN RCPCI rcpci sgi visws pcmcia # LocalWords: IrLPT UIRCC Tecra Strebel jstrebel suse Eichwalder ke INI INIA # LocalWords: FCP qlogicfc sym isapnp DTLK DoubleTalk rcsys dtlk DMAP SGIVW ar # LocalWords: dmabuf EcoRadio MUTEFREQ GIrBIL girbil tepkom vol mha diplom PQS # LocalWords: bmac Microgate SyncLink synclink hdlc excl ioaddr Tane tanep TCQ # LocalWords: PDS SMALLDOS charsets bigfoot kernelfr mcs cls fw rsvp SKnet sk # LocalWords: SKMC USB UHCI OHCI intel compaq usb ohci HCD Virt Compaq's hcd # LocalWords: VROOTHUB KBD ARRs MCRs NWBUTTON nwbutton NUM WaveArtist APNE cpu # LocalWords: apne blackhawke PlanB lu mlan planb NWFPE FPA nwfpe unbootable # LocalWords: FPEmulator ds vmlinux initialization discardable pgtable PGT mdw # LocalWords: quicklist pagetable arthur StrongARM podule podules Autodetect # LocalWords: dodgy IrPORT irport Litelink litelink SuSE rtfm internet hda CY # LocalWords: multmode DriveReady SeekComplete DriveStatusError miscompile AEC # LocalWords: mainboard's Digital's alim FastTrak aec PIIXn piix Gayle Eyetech # LocalWords: Catweasel IDEDOUBLER Powerbook Centris ICSIDE RapIDE OSM HDM IOP # LocalWords: HDM's OSM's lan FibreChannel ECP autoprobe itg lbl ipmasq cjb IC # LocalWords: bieringer Caulfield's dreamtime decnet SIOCFIGCONF SIOCGIFCONF # LocalWords: rtnetlink Endnode Aironet Arlan Telxon ylenurme arlan ACB aeschi # LocalWords: Sealevel sealevel Cyclom br wanconfig tarball conectiva cycsyn # LocalWords: devel bazar cyclomx NetGear GA IBMOL Lanstreamer uhci eu efs CYZ # LocalWords: olympic linuxtr usbcore acm EZUSB downloader EFS XFS INTR op IIC # LocalWords: heine soundcore JavaStations JavaStation GemTeks TerraTec TODO # LocalWords: ActiveRadio Standalone terratec Rolf Offermanns rolf offermanns # LocalWords: Zoran ZR Buz LML CPQ DA cpqarray PPDEV deviceid vlp ppdev atyfb # LocalWords: AcceleRAID eXtremeRAID NETFILTER Netfilter masqueraded netfilter # LocalWords: kernelnotes Cardbus PCMCIA's CardBus clgenfb Permedia YAM MMAP # LocalWords: mmapped ATM atm PVCs SVCs InARP ATMARP neighbour neighbours MPOA # LocalWords: VCs ENI FPGA Tonga MMF MF UTP printks ZeitNet ZN ZATM uPD SAR PN # LocalWords: approx NICStAR NICs ForeRunnerLE Madge Collage ATMizer Dxxxx VCI # LocalWords: ServeRAID IPS ips ipslinux gzip BSDCOMP LZW RAYCS Interphase app # LocalWords: Tachyon IPHASE Surfboard NextLevel SURFboard jacksonville Tigon # LocalWords: fventuri adelphia siglercm linuxpower AceNICs Starfire starfire # LocalWords: ISOC CPiA cpia uss ACPI UDF DirectCD udf CDRW's OSF Manx acpi DM # LocalWords: Unixware cymru Computone IntelliPort Intelliport computone SI sx # LocalWords: adbmouse DRI DRM dlabs GMX PLCs Applicom fieldbus applicom int # LocalWords: VWSND eg ESSSOLO CFU CFNR scribed eiconctrl eicon hylafax KFPU # LocalWords: EXTRAPREC fpu mainboards KHTTPD kHTTPd khttpd Xcelerator SBNI tw # LocalWords: LOGIBUSMOUSE Granch granch sbni Raylink NOHIGHMEM Athlon SIM sim # LocalWords: hpl Tourrilhes DuraLAN starfire Davicom davicom dmfe auk tms tr # LocalWords: TokenExpress Belkin Peracom eTek DVDs infradead Cxxx Adlib AV ZX # LocalWords: NeoMagic CPi CPt Celeron decapsulation Undeletion BFS bfs nVidia # LocalWords: OnStream Irongate Riva phonedev QuickNet LineJack PhoneJack IXJ # LocalWords: Quicknet PhoneJACK LineJACK ixj pnpdump Quicknet's Joandi SSID # LocalWords: aironet quickconfig adhoc btw bap NONCS cardservices Xircom lin # LocalWords: Netwave AirSurfer netwave HomePNA failover MVP iMacs ALi aktual # LocalWords: Aladin HIDBP usbkbd KEYBDEV MOUSEDEV JOYDEV EVDEV UAB WhiteHEAT # LocalWords: Handspring ov DABUSB URB URB's dabusb CRAMFS NFSv ELV IOAPIC WIP # LocalWords: NLMv SMBus ALGOBIT algo PHILIPSPAR philips elv Velleman velleman # LocalWords: ALGOPCF Elektor elektor CHARDEV dfx TDFX tdfx Extensa dof gravis # LocalWords: assasin logitech Overdrive thrustmaster DWave Aureal magellan db # LocalWords: SpaceTec SpaceOrb SpaceBall spaceorb FLX spaceball turbografx zr # LocalWords: amiga ESS's WaveWatcher Maxi belkin RW's ata glx GART MPV Baget # LocalWords: OpenGL Xserver agpgart HOTPLUG CyberPro Integraphics Netwinder # LocalWords: aty FONTWIDTH eni zatm nicstar ForeRunner OC DECstations DEC's # LocalWords: PHYsical SUNI reinsertion ChipSAR KVC PHY ClassID iphase iadbg # LocalWords: DEVS FireWire PCILynx pcilynx LOCALRAM miro's DV RAWIO GRED Mk # LocalWords: Diffserv DSMARK Ingress Qdisc TCINDEX TMSPCI tmspci Ringode JE # LocalWords: MADGEMC madgemc TokenRing SMCTR TokenCard smctr Wacom Graphire # LocalWords: mousedev ConnectTech HandSpring Xirlink IBMCAM ibmcam SN # LocalWords: DEVICEFS yyy Cymraeg Dwave SIMM JSFLASH JavaStation's multilink # LocalWords: nsc ircc DDB Vrc CMN TB PROMs Vino rivafb DDC Matroxes MGA TVO # LocalWords: MAVEN fbdev crtc maven matroxset NTSC PCA SBA AAL SKFP DAS SAS # LocalWords: skfp Intuos ADMtek's pegasus PLUSB plusb pointopoint mp rio Xeon # LocalWords: DEVFS devfs dd bs EDSS german TELESPCI FRITZPCI HFC HFCS BDS HST # LocalWords: ISURF ISAR Saphir HSTSAPHIR Telekom BKM Scitel Quadro SCT Gazel # LocalWords: SP PRI Hypercope HYSDN Hypercope's hysdn IbssJoinNetTimeout FTDI # LocalWords: ARCNet Keyspan PDA ADMtek sgalaxy sgbase opl mpuio mpuirq sbio # LocalWords: sbirq sbdma gus uart mssio mssirq mssdma sscape maui mouirq iph # LocalWords: CHDLC UPS's usbmouse wacom wmforce keybdev joydev fibre Trunking # LocalWords: Etherchannel IOC Moxa Intellio moxa SmartIO mxser Mixcom EFI ir # LocalWords: MIXCOMWD mixcomwd SENDCOMPLETE GMAC iBook gmac OAKNET oaknet PCG # LocalWords: diffserv irlan irtty toshoboe IrCC Lifebook idex AUTODMA FIP Cxx # LocalWords: Yenta Databook TCIC FMVJ fmvj NMCLAN LiveWire nmclan XIRC xirc # LocalWords: loadkeys setfont shm SuperIO soc SOCAL socal FCAL fc fcal COMX # LocalWords: MultiGate ITConsult comx CMX HiCOMX downloadable hw LoCOMX PROTO # LocalWords: locomx MixCOM mixcom proto MyriCOM MYRI Sbus myri sbus IBMLS hme # LocalWords: lanstreamer baseT HAPPYMEAL qfe sunhme SUNLANCE sunlance BigMAC # LocalWords: SUNBMAC sunbmac QuadEthernet SUNQE qe FastEthernet sunqe DSB PTI # LocalWords: DSBR dsbr procinfo QLOGICPTI qpti ptisp QLGC qlogicpti se LBA NF # LocalWords: OPENPROMFS OpenPROM openpromfs OBP OpenBoot flashable Multiboard # LocalWords: SPARCAUDIO SparcClassic Ultras DBRI Sparcbook sparcaudio SUNBPP # LocalWords: UltraDMA WDC CRC CONNTRACK IPTABLES iptables nfmark interface's # LocalWords: tdfxfb TNTx HGA hgafb VERBOSEDEBUG SunTrunking SunSoft XIRTULIP # LocalWords: ethercards PNIC Macronix MXIC ASIX xircom Mustek MDC gphoto mdc # 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 # # The following sets edit modes for GNU EMACS # Local Variables: # case-fold-search:nil # fill-prefix:" " # adaptive-fill:nil # fill-column:70 # End: