Linux/Unix编程

开发平台：

Unix_Linux

Configure.help：源码内容

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
<file:Documentation/isdn/README.eicon> 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 <file:Documentation/modules.txt>. 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 <file:Documentation/isdn/README.fax> 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 <http://www.capi.org/>. 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
<file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>. 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 <file:Documentation/modules.txt>. 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 <file:Documentation/modules.txt>. 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 <file:Documentation/modules.txt>. 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 <file:Documentation/modules.txt>. 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 <file:Documentation/modules.txt>. 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 <file:Documentation/modules.txt>. 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 <file:Documentation/modules.txt>. 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
<file:Documentation/isdn/README.act2000> 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 <file:Documentation/modules.txt>. 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: <http://www.auvertech.fr/>.
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 <file:Documentation/modules.txt>. 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 <file:Documentation/isdn/README.hysdn> 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 <file:Documentation/modules.txt>. 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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>. 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
<file:Documentation/modules.txt>.
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
<http://www.ultralinux.org/faq.html> 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
<http://www.dementia.org/~shadow/sparcaudio.html> 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 <http://www.bluetooth.com/>.
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 <http://bluez.sourceforge.net/>.
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 <http://bluez.sourceforge.net>.
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 <http://bluez.sf.net>.
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 <mailto:quango@themall.net> 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 <file:Documentation/m68k>; 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
"<file:Documentation/modules.txt>".
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 <file:Documentation/m68k>; 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
<http://www.q40.de/>. 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
<http://www.angelfire.com/ca2/tech68k/sun3.html>.
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 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
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
<http://www.suse.cz/development/input/adapters.html> and
<http://sourceforge.net/projects/linuxconsole/> 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 <http://www.hisoft.co.uk/>, 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
<file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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
<http://amiga.multigraph.com/photos/oktagon.html>.
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 <file:Documentation/modules.txt>. 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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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
<file:Documentation/modules.txt>.
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
<file:Documentation/modules.txt>.
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
<file:Documentation/modules.txt>.
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
<file:Documentation/modules.txt>.
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
<file:Documentation/modules.txt>.
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
<file:Documentation/modules.txt>.
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
<file:Documentation/modules.txt>.
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
<file:Documentation/modules.txt>.
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
<file:Documentation/modules.txt>.
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
<file:Documentation/modules.txt>.
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:
<http://www.chips.ibm.com/products/powerpc/tools/evk_pn.html#GCX>.
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:
<http://www.synergymicro.com/PressRel/97_10_15.html>.
Select APUS if configuring for a PowerUP Amiga. More information is
available at: <http://linux-apus.sourceforge.net/>.
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:
<http://www.synergymicro.com/PressRel/97_10_15.html>.
Amiga-Apus
CONFIG_APUS
Select APUS if configuring for a PowerUP Amiga.
More information is available at:
<http://linux-apus.sourceforge.net/>.
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 <ftp://ftp.samba.org/pub/ppclinux/pmud/>.
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: <http://www.denx.de/PDF/TQM8xxLHWM201.pdf>
- starter kit: <http://www.denx.de/PDF/STK8xxLHWM201.pdf>
- images: <http://www.denx.de/embedded-ppc-en.html>
FPS850L:
FingerPrint Sensor System (based on TQM850L)
Manufacturer: IKENDI AG, <http://www.ikendi.com/>
Date of Release: November 1999
End of life: end 2000 ?
URL: see TQM850L
SPD823TS:
MPC823 based board used in the "Tele Server" product
Manufacturer: Speech Design, <http://www.speech-design.de/>
Date of Release: Mid 2000 (?)
End of life: -
URL: <http://www.speech-design.de/>
select "English", then "Teleteam Solutions", then "TeleServer"
IVMS8:
MPC860 based board used in the "Integrated Voice Mail System",
Small Version (8 voice channels)
Manufacturer: Speech Design, <http://www.speech-design.de/>
Date of Release: December 2000 (?)
End of life: -
URL: <http://www.speech-design.de/>
IVML24:
MPC860 based board used in the "Integrated Voice Mail System",
Large Version (24 voice channels)
Manufacturer: Speech Design, <http://www.speech-design.de/>
Date of Release: March 2001 (?)
End of life: -
URL: <http://www.speech-design.de/>
SM850:
Service Module (based on TQM850L)
Manufacturer: Dependable Computer Systems, <http://www.decomsys.com/>
Date of Release: end 2000 (?)
End of life: mid 2001 (?)
URL: <http://www.tz-mikroelektronik.de/ServiceModule/index.html>
HERMES_PRO:
Hermes-Pro ISDN/LAN router with integrated 8 x hub
Manufacturer: Multidata Gesellschaft f黵 Datentechnik und Informatik
<http://www.multidata.de/>
Date of Release: 2000 (?)
End of life: -
URL: <http://www.multidata.de/english/products/hpro.htm>
IP860:
VMEBus IP (Industry Pack) carrier board with MPC860
Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
Date of Release: ?
End of life: -
URL: <http://www.microsys.de/html/ip860.html>
PCU_E:
PCU = Peripheral Controller Unit, Extended
Manufacturer: Siemens AG, ICN (Information and Communication Networks)
<http://www.siemens.de/page/1,3771,224315-1-999_2_226207-0,00.html>
Date of Release: April 2001
End of life: August 2001
URL: n. a.
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
<http://www.denx.de/PDF/TQM8xxLHWM201.pdf>, and
<http://www.denx.de/PDF/STK8xxLHWM201.pdf>, and an image at
<http://www.denx.de/embedded-ppc-en.html>.
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
<http://www.denx.de/PDF/TQM8xxLHWM201.pdf>, and
<http://www.denx.de/PDF/STK8xxLHWM201.pdf>, and an image at
<http://www.denx.de/embedded-ppc-en.html>.
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
<http://www.denx.de/PDF/TQM8xxLHWM201.pdf>, and
<http://www.denx.de/PDF/STK8xxLHWM201.pdf>, and an image at
<http://www.denx.de/embedded-ppc-en.html>.
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
<http://www.denx.de/PDF/TQM8xxLHWM201.pdf>, and
<http://www.denx.de/PDF/STK8xxLHWM201.pdf>, and an image at
<http://www.denx.de/embedded-ppc-en.html>.
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 <http://www.decomsys.com/>.
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
<http://www.speech-design.de/>.
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 <http://www.speech-design.de/>.
# 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 <http://www.speech-design.de/>.
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 <wd@denx.de>:
#
# TQM8260:
# MPC8260 based module
#
# Manufacturer: TQ Components, www.tq-group.de
# Date of Release: June 2001
# End of Life: not yet :-)
# URL: <http://www.denx.de/PDF/TQM82xx_SPEC_Rev003.pdf>
#
# IP860:
# VMEBus IP (Industry Pack) carrier board with MPC860
#
# Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
# Date of Release: ?
# End of life: -
# URL: <http://www.microsys.de/html/ip860.html>
#
# CU824:
# VMEBus Board with PCI extension with MPC8240 CPU
#
# Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
# Date of Release: early 2001 (?)
# End of life: -
# URL: <http://www.microsys.de/html/cu824.html>
#
# PM826:
# Modular system with MPC8260 CPU
#
# Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
# Date of Release: mid 2001
# End of life: -
# URL: <http://www.microsys.de/html/pm826.html>
#
# PCU_E:
# PCU = Peripheral Controller Unit; E = extended (?)
#
# Mfr: Siemens AG, ICN (Information and Communication Networks)
# <http://www.siemens.de/page/1,3771,224315-1-999_2_226207-0,00.html>
# Date of Release: April 2001
# End of life: -
# 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
<http://www.windriver.com/>, 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: <http://www.denx.de/PDF/TQM82xx_SPEC_Rev005.pdf>
PM826:
Modular system with MPC8260 CPU
Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
Date of Release: mid 2001
End of life: -
URL: <http://www.microsys.de/html/pm826.html>
CU824:
VMEBus Board with PCI extension with MPC8240 CPU
Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
Date of Release: early 2001 (?)
End of life: -
URL: <http://www.microsys.de/html/cu824.html>
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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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
<ftp://ftp.uk.linux.org/pub/linux/video4linux/>.
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 <file:Documentation/video4linux/API.html>.
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 <file:Documentation/modules.txt>.
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
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>. More
information is contained in the file
<file:Documentation/video4linux/radiotrack.txt>.
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 <file:Documentation/modules.txt>. 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
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
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 <file:Documentation/modules.txt>. 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
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
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 <file:Documentation/modules.txt>. 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
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
Further documentation on this driver can be found on the WWW at
<http://linux.blackhawke.net/cadet.html>.
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 <file:Documentation/modules.txt>. 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=<io>" 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
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
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 <file:Documentation/modules.txt>. 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
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
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 <file:Documentation/modules.txt>. 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
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
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 <file:Documentation/modules.txt>. 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 <file:Documentation/modules.txt>. 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
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
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 <file:Documentation/modules.txt>. 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
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
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 <file:Documentation/modules.txt>. 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
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
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 <file:Documentation/modules.txt>. 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
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
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 <file:Documentation/modules.txt>. 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
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
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 <file:Documentation/modules.txt>. 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 <http://www.cpu.lu/~mlan/planb.html> 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
<http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
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 <file:Documentation/modules.txt>. 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 <file:Documentation/modules.txt>.
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
<file:Documentation/video4linux/bttv> 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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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
<http://www.stradis.com/decoder.html>.
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 <http://www.lysator.liu.se/~gz/buz/>.
Miro DC10(+) support
CONFIG_VIDEO_ZORAN_DC10
Say Y to support the Pinnacle Systems Studio DC10 plus TV/Video
card. Linux page at
<http://lhd.datapower.com/db/dispproduct.php3?DISP?1511>. Vendor
page at <http://www.pinnaclesys.com/>.
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 <http://www.linuxmedialabs.com/lml33doc.html>.
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
<file:Documentation/video4linux/zr36120.txt> 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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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 <file:Documentation/modules.txt>.
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 <file:Documentation/video4linux/CQcam.txt> 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 <file:drivers/media/video4linux/w9966.txt> and
<file:drivers/media/video/w9966.c> 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 <file:Documentation/video4linux/README.cpia> 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
<file:Documentation/modules.txt>.
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
<file:Documentation/video4linux/meye.txt> 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 <file:Documentation/modules.txt>.
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
<file:Documentation/s390/chandev.8> 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
<file:Documentation/cpqarray.txt> 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
<file:Documentation/modules.txt>. 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
<http://www.computingmuseum.com/museum/archi.htm>.
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:
<http://www.linkupsys.com/>
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:
<http://www.netwinder.org/>
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:
<http://crl.research.compaq.com/projects/personalserver/>
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
<http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2001-June/003510.html>.
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:
<http://www.handhelds.org/Compaq/index.html#iPAQ_H3600>
<http://www.compaq.com/products/handhelds/pocketpc/>
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 <http://www.lart.tudelft.nl/> 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
<http://www.applieddata.net/> 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
<http://www.applieddata.net/products_masterSpec.asp> 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
<http://www.applieddata.net/products_bitsySpec.asp> for more
information.
ITSY
CONFIG_SA1100_ITSY
Say Y here if you are using the Compaq Itsy experimental pocket
computer. See <http://research.compaq.com/wrl/projects/itsy/> for
more information.
PLEB
CONFIG_SA1100_PLEB
Say Y here if you are using a Portable Linux Embedded Board
(also known as PLEB). See <http://www.cse.unsw.edu.au/~pleb/>
for more information.
CerfBoard
CONFIG_SA1100_CERF
The Intrinsyc CerfBoard is based on the StrongARM 1110.
More information is available at:
<http://www.intrinsyc.com/products/referenceplatforms/cerfboard.html>.
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: <http://www.flexanet.com/>.
nanoEngine
CONFIG_SA1100_NANOENGINE
The nanoEngine is a StrongARM 1110-based single board computer
from Bright Star Engineering. More information is available at:
<http://www.brightstareng.com/arm/nanoeng.htm>.
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
<http://www.visuaide.com/pagevictor.en.html> 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
<http://linuxdevices.com/products/PD2382866068.html>.
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
<http://developer.intel.com/design/strong/sa110.htm>.
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