1 mainmenu "Linux/MIPS Kernel Configuration"
5 menu "Machine selection"
8 bool "Support for Acer PICA 1 chipset (EXPERIMENTAL)"
9 depends on EXPERIMENTAL
11 This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
12 kernel that runs on these, say Y here. For details about Linux on
13 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
14 <http://oss.sgi.com/mips/>.
17 bool "Support for BAGET MIPS series (EXPERIMENTAL)"
18 depends on MIPS32 && EXPERIMENTAL
20 This enables support for the Baget, a Russian embedded system. For
21 more details about the Baget see the Linux/MIPS FAQ on
22 <http://oss.sgi.com/mips/>.
25 bool "Support for CASIO CASSIOPEIA E-10/15/55/65"
28 bool "Support for Cobalt Server (EXPERIMENTAL)"
29 depends on EXPERIMENTAL
32 bool "Support for DECstations"
33 depends on MIPS32 || EXPERIMENTAL
35 This enables support for DEC's MIPS based workstations. For details
36 see the Linux/MIPS FAQ on <http://oss.sgi.com/mips/> and the
37 DECstation porting pages on <http://decstation.unix-ag.org/>.
39 If you have one of the following DECstation Models you definitely
40 want to choose R4xx0 for the CPU Type:
47 otherwise choose R3000.
50 bool "Support for Galileo EV64120 Evaluation board (EXPERIMENTAL)"
51 depends on EXPERIMENTAL
53 This is an evaluation board based on the Galileo GT-64120
54 single-chip system controller that contains a MIPS R5000 compatible
55 core running at 75/100MHz. Their website is located at
56 <http://www.galileot.com/>. Say Y here if you wish to build a
57 kernel for this platform.
60 bool "Enable Second PCI (PCI1)"
61 depends on MIPS_EV64120
63 if MOMENCO_OCELOT_G || MOMENCO_OCELOT
73 prompt "Galileo Chip Clock"
83 bool "100" if MIPS_EV64120
90 bool "Support for Galileo EV96100 Evaluation board (EXPERIMENTAL)"
91 depends on EXPERIMENTAL
93 This is an evaluation board based on the Galielo GT-96100 LAN/WAN
94 communications controllers containing a MIPS R5000 compatible core
95 running at 83MHz. Their website is <http://www.galileot.com/>. Say Y
96 here if you wish to build a kernel for this platform.
99 bool "Support for Globespan IVR board"
101 This is an evaluation board built by Globespan to showcase thir
102 iVR (Internet Video Recorder) design. It utilizes a QED RM5231
103 R5000 MIPS core. More information can be found out their website
104 located at <http://www.globespan.net/products/product4.html>P. Say Y
105 here if you wish to build a kernel for this platform.
108 bool "Support for LASAT Networks platforms"
111 bool "Support for LASAT Networks 100 series"
115 bool "Support for LASAT Networks 200 series"
119 tristate "PICVUE LCD display driver"
123 tristate "PICVUE LCD display driver /proc interface"
127 bool "DS1603 RTC driver"
131 bool "LASAT sysctl interface"
135 bool "Support for Hewlett Packard LaserJet board"
138 bool "Support for IBM WorkPad z50"
141 bool "Support for ITE 8172G board"
143 Ths is an evaluation board made by ITE <http://www.ite.com.tw/>
144 with ATX form factor that utilizes a MIPS R5000 to work with its
145 ITE8172G companion internet appliance chip. The MIPS core can be
146 either a NEC Vr5432 or QED RM5231. Say Y here if you wish to build
147 a kernel for this platform.
150 bool "Support for older IT8172 (Rev C)"
151 depends on MIPS_ITE8172
153 Say Y here to support the older, Revision C version of the Integrated
154 Technology Express, Inc. ITE8172 SBC. Vendor page at
155 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
156 board at <http://www.mvista.com/allies/semiconductor/ite.html>.
159 bool "Support for MIPS Atlas board"
161 This enables support for the QED R5231-based MIPS Atlas evaluation
164 config MIPS_MAGNUM_4000
165 bool "Support for MIPS Magnum 4000"
167 This is a machine with a R4000 100 MHz CPU. To compile a Linux
168 kernel that runs on these, say Y here. For details about Linux on
169 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
170 <http://oss.sgi.com/mips/>.
173 bool "Support for MIPS Malta board"
175 This enables support for the VR5000-based MIPS Malta evaluation
179 bool "Support for MIPS SEAD board (EXPERIMENTAL)"
180 depends on EXPERIMENTAL
182 config MOMENCO_OCELOT
183 bool "Support for Momentum Ocelot board"
185 The Ocelot is a MIPS-based Single Board Computer (SBC) made by
186 Momentum Computer <http://www.momenco.com/>.
188 config MOMENCO_OCELOT_G
189 bool "Support for Momentum Ocelot-G board"
191 The Ocelot is a MIPS-based Single Board Computer (SBC) made by
192 Momentum Computer <http://www.momenco.com/>.
194 config MOMENCO_OCELOT_C
195 bool "Support for Momentum Ocelot-C board"
197 The Ocelot is a MIPS-based Single Board Computer (SBC) made by
198 Momentum Computer <http://www.momenco.com/>.
201 bool "Support for NEC DDB Vrc-5074 (EXPERIMENTAL)"
202 depends on EXPERIMENTAL
204 This enables support for the VR5000-based NEC DDB Vrc-5074
208 bool "Support for NEC DDB Vrc-5476"
210 This enables support for the R5432-based NEC DDB Vrc-5476
213 Features : kernel debugging, serial terminal, NFS root fs, on-board
214 ether port USB, AC97, PCI, PCI VGA card & framebuffer console,
215 IDE controller, PS2 keyboard, PS2 mouse, etc.
218 bool "Support for NEC DDB Vrc-5477"
220 This enables support for the R5432-based NEC DDB Vrc-5477,
221 or Rockhopper/SolutionGear boards with R5432/R5500 CPUs.
223 Features : kernel debugging, serial terminal, NFS root fs, on-board
224 ether port USB, AC97, PCI, etc.
226 config DDB5477_BUS_FREQUENCY
227 int "bus frequency (in kHZ, 0 for auto-detect)"
232 bool "Support for NEC Osprey board"
235 bool "Support for NEC Eagle/Hawk board"
238 bool "Support for Olivetti M700-10"
240 This is a machine with a R4000 100 MHz CPU. To compile a Linux
241 kernel that runs on these, say Y here. For details about Linux on
242 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
243 <http://oss.sgi.com/mips/>.
246 bool "Support for SGI IP22 (Indy/Indigo2)"
248 This are the SGI Indy, Challenge S and Indigo2, as well as certain
249 OEM variants like the Tandem CMN B006S. To compile a Linux kernel
250 that runs on these, say Y here.
253 bool "Support for SGI IP27 (Origin200/2000)"
256 This are the SGI Origin 200, Origin 2000 and Onyx 2 Graphics
257 workstations. To compile a Linux kernel that runs on these, say Y
262 # depends on SGI_IP27
263 # This options adds support for userspace processes upto 16TB size.
264 # Normally the limit is just .5TB.
266 config SGI_SN0_N_MODE
270 The nodes of Origin 200, Origin 2000 and Onyx 2 systems can be
271 configured in either N-Modes which allows for more nodes or M-Mode
272 which allows for more memory. Your system is most probably
273 running in M-Mode, so you should say N here.
276 bool "Discontiguous Memory Support"
279 Say Y to upport efficient handling of discontiguous physical memory,
280 for architectures which are either NUMA (Non-Uniform Memory Access)
281 or have huge holes in the physical address space for other reasons.
282 See <file:Documentation/vm/numa> for more.
288 Say Y to compile the kernel to support NUMA (Non-Uniform Memory
289 Access). This option is for configuring high-end multiprocessor
290 server machines. If in doubt, say N.
293 bool "Mapped kernel support"
296 Change the way a Linux kernel is loaded unto memory on a MIPS64
297 machine. This is required in order to support text replication and
298 NUMA. If you need to undersatand it, read the source code.
300 config REPLICATE_KTEXT
301 bool "Kernel text replication support"
304 Say Y here to enable replicating the kernel text across multiple
305 nodes in a NUMA cluster. This trades memory for speed.
307 config REPLICATE_EXHANDLERS
308 bool "Exception handler replication support"
311 Say Y here to enable replicating the kernel exception handlers
312 across multiple nodes in a NUMA cluster. This trades memory for
316 bool "Support for SGI IP32 (O2) (EXPERIMENTAL)"
317 depends on EXPERIMENTAL
319 If you want this kernel to run on SGI O2 workstation, say Y here.
323 bool "Support for AMD/Alchemy Au1X00 SOCs"
326 prompt "Au1X00 SOC Type"
327 depends on SOC_AU1X00
329 Say Y here to enable support for one of three AMD/Alchemy
330 SOCs. For additional documentation see www.amd.com.
342 prompt "AMD/Alchemy Pb1x and Db1x board support"
343 depends on SOC_AU1X00
345 These are evaluation boards built by AMD/Alchemy to
346 showcase their Au1X00 Internet Edge Processors. The SOC design
347 is based on the MIPS32 architecture running at 266/400/500MHz
348 with many integrated peripherals. Further information can be
349 found at their website, <http://www.amd.com/>. Say Y here if you
350 wish to build a kernel for this platform.
354 depends on SOC_AU1000
358 depends on SOC_AU1100
362 depends on SOC_AU1500
366 depends on SOC_AU1000
370 depends on SOC_AU1100
374 depends on SOC_AU1500
378 config SIBYTE_SB1xxx_SOC
379 bool "Support for Broadcom BCM1xxx SOCs (EXPERIMENTAL)"
380 depends on EXPERIMENTAL
383 prompt "BCM1xxx SOC Type"
384 depends on SIBYTE_SB1xxx_SOC
385 default SIBYTE_SB1250
393 bool "Running under simulation"
394 depends on SIBYTE_SB1xxx_SOC
397 bool "Booting from CFE"
398 depends on SIBYTE_SB1xxx_SOC
400 config SIBYTE_CFE_CONSOLE
401 bool "Use firmware console"
402 depends on SIBYTE_CFE
404 config SIBYTE_STANDALONE
406 depends on SIBYTE_SB1xxx_SOC && !SIBYTE_CFE
409 config SIBYTE_STANDALONE_RAM_SIZE
410 int "Memory size (in megabytes)"
411 depends on SIBYTE_SB1xxx_SOC && !SIBYTE_CFE
414 config SIBYTE_BUS_WATCHER
415 bool "Support for Bus Watcher statistics"
416 depends on SIBYTE_SB1xxx_SOC
418 config SIBYTE_SB1250_PROF
419 bool "Support for SB1/SOC profiling - SB1/SCD perf counters"
420 depends on SIBYTE_SB1xxx_SOC
423 bool "Support for ZBbus profiling"
424 depends on SIBYTE_SB1xxx_SOC
427 bool "Support for SWARM board"
428 depends on SIBYTE_SB1250
432 depends on SIBYTE_SWARM
436 bool "Support for SNI RM200 PCI"
438 The SNI RM200 PCI was a MIPS-based platform manufactured by Siemens
439 Nixdorf Informationssysteme (SNI), parent company of Pyramid
440 Technology and now in turn merged with Fujitsu. Say Y here to
441 support this machine type.
444 bool "Support for TANBAC TB0226 (Mbase)"
446 The TANBAC TB0226 (Mbase) is a MIPS-based platform manufactured by TANBAC.
447 Please refer to <http://www.tanbac.co.jp/> about Mbase.
450 bool "Support for TANBAC TB0229 (VR4131DIMM)"
452 The TANBAC TB0229 (VR4131DIMM) is a MIPS-based platform manufactured by TANBAC.
453 Please refer to <http://www.tanbac.co.jp/> about VR4131DIMM.
455 config TOSHIBA_JMR3927
456 bool "Support for Toshiba JMR-TX3927 board"
459 config TOSHIBA_RBTX4927
460 bool "Support for Toshiba TBTX49[23]7 board"
464 bool "Support for Victor MP-C303/304"
467 bool "Support for ZAO Networks Capcella"
469 config RWSEM_GENERIC_SPINLOCK
473 config RWSEM_XCHGADD_ALGORITHM
477 # Select some configuration options automatically based on user selections.
481 depends on SNI_RM200_PCI || SGI_IP32 || SGI_IP27 || SGI_IP22 || MIPS_MAGNUM_4000 || OLIVETTI_M700 || ACER_PICA_61
484 config GENERIC_ISA_DMA
486 depends on SNI_RM200_PCI || MIPS_MAGNUM_4000 || OLIVETTI_M700 || ACER_PICA_61
489 config CONFIG_GT64120
491 depends on MIPS_EV64120 || MOMENCO_OCELOT
496 depends on SNI_RM200_PCI || DDB5477 || DDB5476 || DDB5074 || MIPS_MALTA || MIPS_MAGNUM_4000 || OLIVETTI_M700 || MIPS_COBALT || ACER_PICA_61
501 depends on MIPS_MAGNUM_4000 || OLIVETTI_M700 || ACER_PICA_61
504 config NONCOHERENT_IO
506 depends on ZAO_CAPCELLA || VICTOR_MPC30X || TOSHIBA_JMR3927 || TOSHIBA_RBTX4927 || SNI_RM200_PCI || SGI_IP32 || SGI_IP22 || NEC_EAGLE || NEC_OSPREY || DDB5477 || DDB5476 || DDB5074 || MOMENCO_OCELOT || MOMENCO_OCELOT_C || MOMENCO_OCELOT_G || MIPS_SEAD || MIPS_MALTA || MIPS_MAGNUM_4000 || OLIVETTI_M700 || MIPS_ATLAS || LASAT || MIPS_ITE8172 || IBM_WORKPAD || HP_LASERJET || MIPS_IVR || MIPS_EV96100 || MIPS_EV64120 || DECSTATION || MIPS_COBALT || MIPS_PB1500 || MIPS_PB1100 || MIPS_PB1000 || CASIO_E55 || ACER_PICA_61 || TANBAC_TB0226 || TANBAC_TB0229
507 default y if ZAO_CAPCELLA || VICTOR_MPC30X || TOSHIBA_JMR3927 || TOSHIBA_RBTX4927 || SNI_RM200_PCI || SGI_IP32 || SGI_IP22 || NEC_EAGLE || NEC_OSPREY || DDB5477 || DDB5476 || DDB5074 || MOMENCO_OCELOT_G || MOMENCO_OCELOT || MIPS_SEAD || MIPS_MALTA || MIPS_MAGNUM_4000 || OLIVETTI_M700 || MIPS_ATLAS || LASAT || MIPS_ITE8172 || IBM_WORKPAD || HP_LASERJET || MIPS_IVR || MIPS_EV96100 || MIPS_EV64120 || DECSTATION || MIPS_COBALT || MIPS_PB1500 || MIPS_PB1100 || MIPS_PB1000 || CASIO_E55 || ACER_PICA_61 || TANBAC_TB0226 || TANBAC_TB0229
508 default n if (SIBYTE_SB1250 || SGI_IP27)
510 config CPU_LITTLE_ENDIAN
511 bool "Generate little endian code"
512 default y if ACER_PICA_61 || CASIO_E55 || DDB5074 || DDB5476 || DDB5477 || DECSTATION || HP_LASERJET || IBM_WORKPAD || LASAT || MIPS_COBALT || MIPS_ITE8172 || MIPS_IVR || MIPS_PB1000 || MIPS_PB1100 || MIPS_PB1500 || NEC_OSPREY || NEC_EAGLE || OLIVETTI_M700 || SNI_RM200_PCI || VICTOR_MPC30X || ZAO_CAPCELLA
513 default n if BAGET_MIPS || MIPS_EV64120 || MIPS_EV96100 || MOMENCO_OCELOT || MOMENCO_OCELOT_G || SGI_IP22 || SGI_IP27 || SGI_IP32 || TOSHIBA_JMR3927
515 Some MIPS machines can be configured for either little or big endian
516 byte order. These modes require different kernels. Say Y if your
517 machine is little endian, N if it's a big endian machine.
521 depends on ZAO_CAPCELLA || VICTOR_MPC30X || SGI_IP22 || NEC_EAGLE || NEC_OSPREY || DDB5477 || DDB5476 || DDB5074 || IBM_WORKPAD || HP_LASERJET || DECSTATION || CASIO_E55 || TANBAC_TB0226 || TANBAC_TB0229
526 depends on ZAO_CAPCELLA || VICTOR_MPC30X || NEC_EAGLE || IBM_WORKPAD || CASIO_E55 || TANBAC_TB0226 || TANBAC_TB0229
531 depends on ZAO_CAPCELLA || VICTOR_MPC30X || SIBYTE_SB1250 || NEC_EAGLE || NEC_OSPREY || DDB5477 || IBM_WORKPAD || CASIO_E55 || TANBAC_TB0226 || TANBAC_TB0229
536 depends on NEC_EAGLE || ZAO_CAPCELLA || VICTOR_MPC30X || IBM_WORKPAD || CASIO_E55 || TANBAC_TB0226 || TANBAC_TB0229
540 tristate "NEC VRC4173 Support"
541 depends on NEC_EAGLE || VICTOR_MPC30X
543 config DDB5XXX_COMMON
545 depends on DDB5074 || DDB5476 || DDB5477
548 config MIPS_BOARDS_GEN
550 depends on MIPS_ATLAS || MIPS_MALTA || MIPS_SEAD
555 depends on MIPS_IVR || MIPS_ITE8172
560 depends on ZAO_CAPCELLA || VICTOR_MPC30X || TOSHIBA_JMR3927 || TOSHIBA_RBTX4927 || NEC_EAGLE || DDB5477 || DDB5476 || DDB5074 || MIPS_ITE8172 || HP_LASERJET || MIPS_IVR || MIPS_EV96100 || MIPS_PB1500 || MIPS_PB1100 || MIPS_PB1000 || TANBAC_TB0226 || TANBAC_TB0229
564 bool "Support for paging of anonymous memory"
565 depends on TOSHIBA_JMR3927 || TOSHIBA_RBTX4927 || SIBYTE_SB1250 || SGI_IP22 || MOMENCO_OCELOT_C || MOMENCO_OCELOT_G || MOMENCO_OCELOT || MIPS_MALTA || MIPS_ATLAS || MIPS_EV96100 || MIPS_PB1100 || MIPS_PB1000
568 This option allows you to choose whether you want to have support
569 for socalled swap devices or swap files in your kernel that are
570 used to provide more virtual memory than the actual RAM present
571 in your computer. If unusre say Y.
573 config AU1000_USB_DEVICE
575 depends on MIPS_PB1500 || MIPS_PB1100 || MIPS_PB1000
580 depends on MIPS_COBALT
585 depends on MIPS_EV64120
590 depends on MIPS_EV96100
593 Say Y here to support the Galileo Technology GT96100 communications
594 controller card. There is a web page at <http://www.galileot.com/>.
598 depends on MIPS_ITE8172 || MIPS_IVR
603 depends on MIPS_ITE8172
608 depends on DECSTATION || MIPS_ATLAS || MIPS_MALTA || SIBYTE_SB1250 || SGI_IP32 || SGI_IP22 || SNI_RM200_PCI
611 config L1_CACHE_SHIFT
613 default "4" if DECSTATION
614 default "5" if SGI_IP32 || SGI_IP22 || MIPS_SEAD || MIPS_MALTA || MIPS_ATLAS
615 default "7" if SGI_IP27
619 depends on SNI_RM200_PCI || SGI_IP32 || SGI_IP22 || MIPS_MAGNUM_4000 || OLIVETTI_M700
624 depends on MIPS_MAGNUM_4000 || OLIVETTI_M700
627 The frame buffer device provides an abstraction for the graphics
628 hardware. It represents the frame buffer of some video hardware and
629 allows application software to access the graphics hardware through
630 a well-defined interface, so the software doesn't need to know
631 anything about the low-level (hardware register) stuff.
633 Frame buffer devices work identically across the different
634 architectures supported by Linux and make the implementation of
635 application programs easier and more portable; at this point, an X
636 server exists which uses the frame buffer device exclusively.
637 On several non-X86 architectures, the frame buffer device is the
638 only way to use the graphics hardware.
640 The device is accessed through special device nodes, usually located
641 in the /dev directory, i.e. /dev/fb*.
643 You need an utility program called fbset to make full use of frame
644 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
645 and the Framebuffer-HOWTO at
646 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
649 Say Y here and to the driver for your graphics board below if you
650 are compiling a kernel for a non-x86 architecture.
652 If you are compiling for the x86 architecture, you can say Y if you
653 want to play with it, but it is not essential. Please note that
654 running graphical applications that directly touch the hardware
655 (e.g. an accelerated X server) and that are not frame buffer
656 device-aware may cause unexpected results. If unsure, say N.
660 depends on MIPS_MAGNUM_4000 || OLIVETTI_M700
663 config HAVE_STD_PC_SERIAL_PORT
665 depends on DDB5476 || DDB5074 || MIPS_MALTA
670 depends on NEC_OSPREY
674 bool "ARC console support"
675 depends on SGI_IP22 || SNI_RM200_PCI
679 depends on SNI_RM200_PCI || SGI_IP32 || SGI_IP22
684 depends on SNI_RM200_PCI || SGI_IP32 || SGI_IP22
689 depends on MIPS_EV96100 || MOMENCO_OCELOT || SGI_IP22
702 #config MAPPED_PCI_IO y
704 # depends on SGI_IP27
712 config TOSHIBA_BOARDS
714 depends on TOSHIBA_JMR3927 || TOSHIBA_RBTX4927
718 bool "Added TANBAC TB0219 Base board support"
719 depends on TANBAC_TB0229
740 Please make sure to pick the right CPU type. Linux/MIPS is not
741 designed to be generic, i.e. Kernels compiled for R3000 CPUs will
742 *not* work on R4000 machines and vice versa. However, since most
743 of the supported machines have an R4000 (or similar) CPU, R4x00
744 might be a safe bet. If the resulting kernel does not work,
745 try to recompile with R3000.
754 The options selects support for the NEC VR41xx series of processors.
755 Only choose this option if you have one of these processors as a
756 kernel built with this option will not run on any other type of
757 processor or vice versa.
762 MIPS Technologies R4300-series processors.
767 MIPS Technologies R4000-series processors other than 4300, including
768 the R4000, R4400, R4600, and 4700.
776 MIPS Technologies R5000-series processors other than the Nevada.
783 depends on MIPS32 && EXPERIMENTAL
785 MIPS Technologies R6000 and R6000A series processors. Note these
786 processors are extremly rare and the support for them is incomplete.
791 MIPS Technologies R52x0-series ("Nevada") processors.
795 depends on MIPS64 && EXPERIMENTAL
797 MIPS Technologies R8000 processors. Note these processors are
798 uncommon and the support for them is incomplete.
803 MIPS Technologies R10000-series processors.
813 config R5000_CPU_SCACHE
815 depends on CPU_NEVADA || CPU_R5000
816 default y if SGI_IP32 || LASAT
820 depends on CPU_NEVADA || CPU_R4X00 || CPU_R5000
821 default y if SGI_IP22 || (SGI_IP32 && CPU_R5000) || R5000_CPU_SCACHE
823 config CPU_HAS_PREFETCH
824 bool "Enable prefetches" if CPU_SB1 && !CPU_SB1_PASS_2
825 default y if CPU_RM7000 || CPU_MIPS64 || CPU_MIPS32
828 bool "Support for Virtual Tagged I-cache" if CPU_MIPS64 || CPU_MIPS32
834 default CPU_SB1_PASS_1
836 config CPU_SB1_PASS_1
839 config CPU_SB1_PASS_2
842 config CPU_SB1_PASS_2_2
847 config SB1_PASS_1_WORKAROUNDS
849 depends on CPU_SB1_PASS_1
852 config SB1_PASS_2_WORKAROUNDS
854 depends on CPU_SB1 && (CPU_SB1_PASS_2_2 || CPU_SB1_PASS_2)
857 # Avoid prefetches on Pass 2 (before 2.2)
858 # XXXKW for now, let 2.2 use same WORKAROUNDS flag as pre-2.2
859 config SB1_CACHE_ERROR
860 bool "Support for SB1 Cache Error handler"
863 config SB1_CERR_IGNORE_RECOVERABLE
864 bool "Ignore recoverable cache errors"
865 depends on SB1_CACHE_ERROR
868 bool "Spin instead of running handler"
869 depends on SB1_CACHE_ERROR
871 config 64BIT_PHYS_ADDR
872 bool "Support for 64-bit physical address space"
873 depends on (CPU_R4X00 || CPU_R5000 || CPU_RM7000 || CPU_R10000 || CPU_SB1 || CPU_MIPS32 || CPU_MIPS64) && MIPS32
876 bool "Override CPU Options"
879 Saying yes here allows you to select support for various features
880 your CPU may or may not have. Most people should say N here.
883 bool "ll/sc Instructions available" if CPU_ADVANCED
884 default y if !CPU_ADVANCED && !CPU_R3000 && !CPU_VR41XX && !CPU_TX39XX
886 MIPS R4000 series and later provide the Load Linked (ll)
887 and Store Conditional (sc) instructions. More information is
888 available at <http://www.go-ecs.com/mips/miptek1.htm>.
890 Say Y here if your CPU has the ll and sc instructions. Say Y here
891 for better performance, N if you don't know. You must say Y here
892 for multiprocessor machines.
894 config CPU_HAS_LLDSCD
895 bool "lld/scd Instructions available" if CPU_ADVANCED
896 default y if !CPU_ADVANCED && !CPU_R3000 && !CPU_VR41XX && !CPU_TX39XX && !CPU_MIPS32
898 Say Y here if your CPU has the lld and scd instructions, the 64-bit
899 equivalents of ll and sc. Say Y here for better performance, N if
900 you don't know. You must say Y here for multiprocessor machines.
903 bool "Writeback Buffer available" if CPU_ADVANCED
904 default y if !CPU_ADVANCED && (CPU_R3000 || CPU_VR41XX || CPU_TX39XX) && DECSTATION
906 Say N here for slightly better performance. You must say Y here for
907 machines which require flushing of write buffers in software. Saying
908 Y is the safe option; N may result in kernel malfunction and crashes.
912 depends on !CPU_R3000
916 # - Highmem only makes sense for the 32-bit kernel.
917 # - The current highmem code will only work properly on physically indexed
918 # caches such as R3000, SB1, R7000 or those that look like they're virtually
919 # indexed such as R4000/R4400 SC and MC versions or R10000. So for the
920 # moment we protect the user and offer the highmem option only on machines
921 # where it's known to be safe. This will not offer highmem on a few systems
922 # such as MIPS32 and MIPS64 CPUs which may have virtual and physically
923 # indexed CPUs but we're playing safe.
924 # - We should not offer highmem for system of which we already know that they
925 # don't have memory configurations that could gain from highmem support in
926 # the kernel because they don't support configurations with RAM at physical
927 # addresses > 0x20000000.
930 bool "High Memory Support"
931 depends on MIPS32 && (CPU_R3000 || CPU_SB1 || CPU_R7000 || CPU_R10000) && !(BAGET_MIPS || DECSTATION)
934 bool "Multi-Processing support"
935 depends on SIBYTE_SB1xxx_SOC && SIBYTE_SB1250 && !SIBYTE_STANDALONE || SGI_IP27
937 This enables support for systems with more than one CPU. If you have
938 a system with only one CPU, like most personal computers, say N. If
939 you have a system with more than one CPU, say Y.
941 If you say N here, the kernel will run on single and multiprocessor
942 machines, but will use only one CPU of a multiprocessor machine. If
943 you say Y here, the kernel will run on many, but not all,
944 singleprocessor machines. On a singleprocessor machine, the kernel
945 will run faster if you say N here.
947 People using multiprocessor machines who say Y here should also say
948 Y to "Enhanced Real Time Clock Support", below.
950 See also the <file:Documentation/smp.tex>,
951 <file:Documentation/smp.txt> and the SMP-HOWTO available at
952 <http://www.tldp.org/docs.html#howto>.
954 If you don't know what to do here, say N.
957 int "Maximum number of CPUs (2-32)"
961 This allows you to specify the maximum number of CPUs which this
962 kernel will support. The maximum supported value is 32 and the
963 minimum value which makes sense is 2.
965 This is purely to save memory - each supported CPU adds
966 approximately eight kilobytes to the kernel image.
969 bool "Preemptible Kernel"
971 This option reduces the latency of the kernel when reacting to
972 real-time or interactive events by allowing a low priority process to
973 be preempted even if it is in kernel mode executing a system call.
974 This allows applications to run more reliably even when the system is
978 bool "Load all symbols for debugging/kksymoops"
980 Say Y here to let the kernel print out symbolic crash information and
981 symbolic stack backtraces. This increases the size of the kernel
982 somewhat, as all symbols have to be loaded into the kernel image.
984 config DEBUG_SPINLOCK_SLEEP
985 bool "Sleep-inside-spinlock checking"
987 If you say Y here, various routines which may sleep will become very
988 noisy if they are called with a spinlock held.
991 bool "DS1742 BRAM/RTC support"
992 depends on TOSHIBA_JMR3927 || TOSHIBA_RBTX4927
994 config MIPS_INSANE_LARGE
995 bool "Support for large 64-bit configurations"
996 depends on CPU_R10000 && MIPS64
998 MIPS R10000 does support a 44 bit / 16TB address space as opposed to
999 previous 64-bit processors which only supported 40 bit / 1TB. If you
1000 need processes of more than 1TB virtual address space, say Y here.
1001 This will result in additional memory usage, so it is not
1002 recommended for normal users.
1004 config RWSEM_GENERIC_SPINLOCK
1010 menu "Bus options (PCI, PCMCIA, EISA, ISA, TC)"
1013 bool "Support for PCI controller"
1014 depends on MIPS_DB1000 || DDB5074 || DDB5476 || DDB5477 || HP_LASERJET || LASAT || MIPS_IVR || MIPS_ATLAS || MIPS_COBALT || MIPS_EV64120 || MIPS_EV96100 || MIPS_ITE8172 || MIPS_MALTA || MOMENCO_OCELOT || MOMENCO_OCELOT_C || MOMENCO_OCELOT_G || MIPS_PB1000 || MIPS_PB1100 || MIPS_PB1500 || NEC_EAGLE || SGI_IP27 || SGI_IP32 || SIBYTE_SB1250 || SNI_RM200_PCI || TANBAC_TB0226 || TANBAC_TB0229 || TOSHIBA_JMR3927 || TOSHIBA_RBTX4927 || VICTOR_MPC30X || ZAO_CAPCELLA
1016 Find out whether you have a PCI motherboard. PCI is the name of a
1017 bus system, i.e. the way the CPU talks to the other stuff inside
1018 your box. Other bus systems are ISA, EISA, or VESA. If you have PCI,
1021 The PCI-HOWTO, available from
1022 <http://www.tldp.org/docs.html#howto>, contains valuable
1023 information about which PCI hardware does work under Linux and which
1026 source "drivers/pci/Kconfig"
1029 bool "ISA bus support"
1030 depends on ACER_PICA_61 || SGI_IP22 || MIPS_MAGNUM_4000 || OLIVETTI_M700 || SNI_RM200_PCI
1031 default y if TOSHIBA_RBTX4927 || DDB5476 || DDB5074 || IBM_WORKPAD || CASIO_E55
1033 Find out whether you have ISA slots on your motherboard. ISA is the
1034 name of a bus system, i.e. the way the CPU talks to the other stuff
1035 inside your box. Other bus systems are PCI, EISA, or VESA. ISA is
1036 an older system, now being displaced by PCI; newer boards don't
1037 support it. If you have ISA, say Y, otherwise N.
1040 # The SCSI bits are needed to get the SCSI code to link ...
1042 config GENERIC_ISA_DMA
1044 default y if ACER_PICA_61 || MIPS_MAGNUM_4000 || OLIVETTI_M700 || SNI_RM200_PCI || SCSI
1048 depends on ISA && (SGI_IP22 || SNI_RM200_PCI)
1050 The Extended Industry Standard Architecture (EISA) bus was
1051 developed as an open alternative to the IBM MicroChannel bus.
1053 The EISA bus provided some of the features of the IBM MicroChannel
1054 bus while maintaining backward compatibility with cards made for
1055 the older ISA bus. The EISA bus saw limited use between 1988 and
1056 1995 when it was made obsolete by the PCI bus.
1058 Say Y here if you are building a kernel for an EISA-based machine.
1062 source "drivers/eisa/Kconfig"
1065 bool "TURBOchannel support"
1066 depends on DECSTATION
1068 TurboChannel is a DEC (now Compaq (now HP)) bus for Alpha and MIPS
1069 processors. Documentation on writing device drivers for TurboChannel
1071 <http://www.cs.arizona.edu/computer.help/policy/DIGITAL_unix/AA-PS3HD-TET1_html/TITLE.html>.
1074 # bool "Access.Bus support"
1088 bool "Support for hot-pluggable devices"
1090 Say Y here if you want to plug devices into your computer while
1091 the system is running, and be able to use them quickly. In many
1092 cases, the devices can likewise be unplugged at any time too.
1094 One well known example of this is PCMCIA- or PC-cards, credit-card
1095 size devices such as network cards, modems or hard drives which are
1096 plugged into slots found on all modern laptop computers. Another
1097 example, used on modern desktops as well as laptops, is USB.
1099 Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
1100 software (at <http://linux-hotplug.sourceforge.net/>) and install it.
1101 Then your kernel will automatically call out to a user mode "policy
1102 agent" (/sbin/hotplug) to load modules and set up software needed
1103 to use devices as you hotplug them.
1105 source "drivers/pcmcia/Kconfig"
1107 source "drivers/hotplug/Kconfig"
1111 menu "Executable file formats"
1117 If you enabled support for /proc file system then the file
1118 /proc/kcore will contain the kernel core image. This can be used
1121 $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
1123 You have two choices here: ELF and A.OUT. Selecting ELF will make
1124 /proc/kcore appear in ELF core format as defined by the Executable
1125 and Linking Format specification. Selecting A.OUT will choose the
1126 old "a.out" format which may be necessary for some old versions
1127 of binutils or on some architectures.
1129 This is especially useful if you have compiled the kernel with the
1130 "-g" option to preserve debugging information. It is mainly used
1131 for examining kernel data structures on the live kernel so if you
1132 don't understand what this means or are not a kernel hacker, just
1133 leave it at its default value ELF.
1142 tristate "Kernel support for ELF binaries"
1144 ELF (Executable and Linkable Format) is a format for libraries and
1145 executables used across different architectures and operating
1146 systems. Saying Y here will enable your kernel to run ELF binaries
1147 and enlarge it by about 13 KB. ELF support under Linux has now all
1148 but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
1149 because it is portable (this does *not* mean that you will be able
1150 to run executables from different architectures or operating systems
1151 however) and makes building run-time libraries very easy. Many new
1152 executables are distributed solely in ELF format. You definitely
1155 Information about ELF is contained in the ELF HOWTO available from
1156 <http://www.tldp.org/docs.html#howto>.
1158 If you find that after upgrading from Linux kernel 1.2 and saying Y
1159 here, you still can't run any ELF binaries (they just crash), then
1160 you'll have to install the newest ELF runtime libraries, including
1161 ld.so (check the file <file:Documentation/Changes> for location and
1164 If you want to compile this as a module ( = code which can be
1165 inserted in and removed from the running kernel whenever you want),
1166 say M here and read <file:Documentation/modules.txt>. The module
1167 will be called binfmt_elf. Saying M or N here is dangerous because
1168 some crucial programs on your system might be in ELF format.
1171 bool "Include IRIX binary compatibility"
1172 depends on !CPU_LITTLE_ENDIAN && MIPS32
1174 config MIPS32_COMPAT
1175 bool "Kernel support for Linux/MIPS 32-bit binary compatibility"
1178 Select this option if you want Linux/MIPS 32-bit binary
1179 compatibility. Since all software available for Linux/MIPS is
1180 currently 32-bit you should say Y here.
1184 depends on MIPS32_COMPAT
1188 bool "Kernel support for o32 binaries"
1189 depends on MIPS32_COMPAT
1191 Select this option if you want to run o32 binaries. These are pure
1192 32-bit binaries as used by the 32-bit Linux/MIPS port. Most of
1193 existing binaries are in this format.
1198 bool "Kernel support for n32 binaries"
1199 depends on MIPS32_COMPAT
1201 Select this option if you want to run n32 binaries. These are
1202 64-bit binaries using 32-bit quantities for addressing and certain
1203 data that would normally be 64-bit. They are used in special
1210 default y if MIPS32_O32 || MIPS32_N32
1213 tristate "Kernel support for MISC binaries"
1215 If you say Y here, it will be possible to plug wrapper-driven binary
1216 formats into the kernel. You will like this especially when you use
1217 programs that need an interpreter to run like Java, Python or
1218 Emacs-Lisp. It's also useful if you often run DOS executables under
1219 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
1220 <http://www.tldp.org/docs.html#howto>). Once you have
1221 registered such a binary class with the kernel, you can start one of
1222 those programs simply by typing in its name at a shell prompt; Linux
1223 will automatically feed it to the correct interpreter.
1225 You can do other nice things, too. Read the file
1226 <file:Documentation/binfmt_misc.txt> to learn how to use this
1227 feature, and <file:Documentation/java.txt> for information about how
1228 to include Java support.
1230 You must say Y to "/proc file system support" (PROC_FS) to
1231 use this part of the kernel.
1233 You may say M here for module support and later load the module when
1234 you have use for it; the module is called binfmt_misc. If you
1235 don't know what to answer at this point, say Y.
1238 bool "Power Management support (EXPERIMENTAL)"
1239 depends on EXPERIMENTAL && SOC_AU1X00
1243 source "drivers/mtd/Kconfig"
1245 source "drivers/parport/Kconfig"
1247 source "drivers/pnp/Kconfig"
1249 source "drivers/block/Kconfig"
1252 menu "MIPS initrd options"
1253 depends on BLK_DEV_INITRD
1255 config EMBEDDED_RAMDISK
1256 bool "Embed root filesystem ramdisk into the kernel"
1258 config EMBEDDED_RAMDISK_IMAGE
1259 string "Filename of gziped ramdisk image"
1260 depends on EMBEDDED_RAMDISK
1261 default "ramdisk.gz"
1263 This is the filename of the ramdisk image to be built into the
1264 kernel. Relative pathnames are relative to arch/mips/ramdisk/.
1265 The ramdisk image is not part of the kernel distribution; you must
1266 provide one yourself.
1271 menu "ATA/ATAPI/MFM/RLL support"
1274 tristate "ATA/ATAPI/MFM/RLL support"
1276 If you say Y here, your kernel will be able to manage low cost mass
1277 storage units such as ATA/(E)IDE and ATAPI units. The most common
1278 cases are IDE hard drives and ATAPI CD-ROM drives.
1280 If your system is pure SCSI and doesn't use these interfaces, you
1283 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
1284 for mass storage units such as hard disks. It was designed by
1285 Western Digital and Compaq Computer in 1984. It was then named
1286 ST506. Quite a number of disks use the IDE interface.
1288 AT Attachment (ATA) is the superset of the IDE specifications.
1289 ST506 was also called ATA-1.
1291 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
1292 ATA-3. It provides support for larger disks (up to 8.4GB by means of
1293 the LBA standard), more disks (4 instead of 2) and for other mass
1294 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
1295 ATA-4 and provides faster (and more CPU friendly) transfer modes
1296 than previous PIO (Programmed processor Input/Output) from previous
1297 ATA/IDE standards by means of fast DMA controllers.
1299 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
1300 CD-ROM drives, similar in many respects to the SCSI protocol.
1302 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
1303 designed in order to prevent data corruption and disk crash by
1304 detecting pre hardware failure conditions (heat, access time, and
1305 the like...). Disks built since June 1995 may follow this standard.
1306 The kernel itself don't manage this; however there are quite a
1307 number of user programs such as smart that can query the status of
1308 SMART parameters disk.
1310 If you want to compile this driver as a module ( = code which can be
1311 inserted in and removed from the running kernel whenever you want),
1312 say M here and read <file:Documentation/modules.txt>. The module
1315 For further information, please read <file:Documentation/ide.txt>.
1319 source "drivers/ide/Kconfig"
1324 menu "SCSI device support"
1327 tristate "SCSI device support"
1329 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
1330 any other SCSI device under Linux, say Y and make sure that you know
1331 the name of your SCSI host adapter (the card inside your computer
1332 that "speaks" the SCSI protocol, also called SCSI controller),
1333 because you will be asked for it.
1335 You also need to say Y here if you want support for the parallel
1336 port version of the 100 MB IOMEGA ZIP drive.
1338 This driver is also available as a module ( = code which can be
1339 inserted in and removed from the running kernel whenever you want).
1340 The module will be called scsi_mod. If you want to compile it as
1341 a module, say M here and read <file:Documentation/modules.txt> and
1342 <file:Documentation/scsi/scsi.txt>. However, do not compile this as a
1343 module if your root file system (the one containing the directory /)
1344 is located on a SCSI device.
1346 source "drivers/scsi/Kconfig"
1351 menu "Old CD-ROM drivers (not SCSI, not IDE)"
1354 config CD_NO_IDESCSI
1355 bool "Support non-SCSI/IDE/ATAPI CDROM drives"
1357 If you have a CD-ROM drive that is neither SCSI nor IDE/ATAPI, say Y
1358 here, otherwise N. Read the CD-ROM-HOWTO, available from
1359 <http://www.tldp.org/docs.html#howto>.
1361 Note that the answer to this question doesn't directly affect the
1362 kernel: saying N will just cause the configurator to skip all
1363 the questions about these CD-ROM drives. If you are unsure what you
1364 have, say Y and find out whether you have one of the following
1367 For each of these drivers, a file Documentation/cdrom/{driver_name}
1368 exists. Especially in cases where you do not know exactly which kind
1369 of drive you have you should read there. Most of these drivers use a
1370 file drivers/cdrom/{driver_name}.h where you can define your
1371 interface parameters and switch some internal goodies.
1373 All these CD-ROM drivers are also usable as a module ( = code which
1374 can be inserted in and removed from the running kernel whenever you
1375 want). If you want to compile them as module, say M instead of Y and
1376 read <file:Documentation/modules.txt>.
1378 If you want to use any of these CD-ROM drivers, you also have to
1379 answer Y or M to "ISO 9660 CD-ROM file system support" below (this
1380 answer will get "defaulted" for you if you enable any of the Linux
1383 source "drivers/cdrom/Kconfig"
1387 source "drivers/md/Kconfig"
1389 source "drivers/message/fusion/Kconfig"
1391 source "drivers/ieee1394/Kconfig"
1393 source "drivers/message/i2o/Kconfig"
1395 source "net/Kconfig"
1397 source "net/ax25/Kconfig"
1399 source "net/irda/Kconfig"
1401 source "drivers/isdn/Kconfig"
1403 source "drivers/telephony/Kconfig"
1406 # input before char - char/joystick depends on it. As does USB.
1408 source "drivers/input/Kconfig"
1410 source "drivers/char/Kconfig"
1412 #source drivers/misc/Config.in
1414 source "drivers/media/Kconfig"
1418 source "drivers/video/Kconfig"
1424 tristate "Sound card support"
1426 If you have a sound card in your computer, i.e. if it can say more
1427 than an occasional beep, say Y. Be sure to have all the information
1428 about your sound card and its configuration down (I/O port,
1429 interrupt and DMA channel), because you will be asked for it.
1431 You want to read the Sound-HOWTO, available from
1432 <http://www.tldp.org/docs.html#howto>. General information about
1433 the modular sound system is contained in the files
1434 <file:Documentation/sound/Introduction>. The file
1435 <file:Documentation/sound/README.OSS> contains some slightly
1436 outdated but still useful information as well.
1438 If you have a PnP sound card and you want to configure it at boot
1439 time using the ISA PnP tools (read
1440 <http://www.roestock.demon.co.uk/isapnptools/>), then you need to
1441 compile the sound card support as a module ( = code which can be
1442 inserted in and removed from the running kernel whenever you want)
1443 and load that module after the PnP configuration is finished. To do
1444 this, say M here and read <file:Documentation/modules.txt> as well
1445 as <file:Documentation/sound/README.modules>; the module will be
1448 I'm told that even without a sound card, you can make your computer
1449 say more than an occasional beep, by programming the PC speaker.
1450 Kernel patches and supporting utilities to do that are in the pcsp
1451 package, available at <ftp://ftp.infradead.org/pub/pcsp/>.
1453 source "sound/Kconfig"
1457 source "drivers/usb/Kconfig"
1459 source "net/bluetooth/Kconfig"
1462 menu "Kernel hacking"
1465 bool "Are you using a crosscompiler"
1467 Say Y here if you are compiling the kernel on a different
1468 architecture than the one it is intended to run on.
1471 bool "Kernel debugging"
1474 bool "Remote GDB kernel debugging"
1475 depends on DEBUG_KERNEL
1477 If you say Y here, it will be possible to remotely debug the MIPS
1478 kernel using gdb. This enlarges your kernel image disk size by
1479 several megabytes and requires a machine with more than 16 MB,
1480 better 32 MB RAM to avoid excessive linking time. This is only
1481 useful for kernel hackers. If unsure, say N.
1484 bool "Console output to GDB"
1487 If you are using GDB for remote debugging over a serial port and
1488 would like kernel messages to be formatted into GDB $O packets so
1489 that GDB prints them as program output, say 'Y'.
1491 config RUNTIME_DEBUG
1492 bool "Enable run-time debugging"
1493 depends on DEBUG_KERNEL
1495 If you say Y here, some debugging macros will do run-time checking.
1496 If you say N here, those macros will mostly turn to no-ops. See
1497 include/asm-mips/debug.h for debuging macros.
1502 bool "Magic SysRq key"
1503 depends on DEBUG_KERNEL
1505 If you say Y here, you will have some control over the system even
1506 if the system crashes for example during kernel debugging (e.g., you
1507 will be able to flush the buffer cache to disk, reboot the system
1508 immediately or dump some status information). This is accomplished
1509 by pressing various keys while holding SysRq (Alt+PrintScreen). It
1510 also works on a serial console (on PC hardware at least), if you
1511 send a BREAK and then within 5 seconds a command keypress. The
1512 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
1513 unless you really know what this hack does.
1515 config MIPS_UNCACHED
1517 depends on DEBUG_KERNEL && !SMP && !SGI_IP27
1519 If you say Y here there kernel will disable all CPU caches. This will
1520 reduce the system's performance dramatically but can help finding
1521 otherwise hard to track bugs. It can also useful if you're doing
1522 hardware debugging with a logic analyzer and need to see all traffic
1525 config DEBUG_HIGHMEM
1526 bool "Highmem debugging"
1527 depends on DEBUG_KERNEL && HIGHMEM
1531 source "security/Kconfig"
1533 source "crypto/Kconfig"
1535 source "lib/Kconfig"