blob: 085dc6ec152b057b6da23c2742a39d0a0012c327 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# For a description of the syntax of this configuration file,
Dirk Hohndele4031492007-10-30 13:37:19 -07003# see Documentation/kbuild/kconfig-language.txt.
Linus Torvalds1da177e2005-04-16 15:20:36 -07004#
5
6mainmenu "uClinux/h8300 (w/o MMU) Kernel Configuration"
7
8config H8300
9 bool
10 default y
Sam Ravnborgec7748b2008-02-09 10:46:40 +010011 select HAVE_IDE
Linus Torvalds1da177e2005-04-16 15:20:36 -070012
13config MMU
14 bool
15 default n
16
17config SWAP
18 bool
19 default n
20
Christoph Lameter66701b12007-02-10 01:43:09 -080021config ZONE_DMA
22 bool
23 default y
24
Linus Torvalds1da177e2005-04-16 15:20:36 -070025config FPU
26 bool
27 default n
28
Linus Torvalds1da177e2005-04-16 15:20:36 -070029config RWSEM_GENERIC_SPINLOCK
30 bool
31 default y
32
33config RWSEM_XCHGADD_ALGORITHM
34 bool
35 default n
36
David Howellsf0d1b0b2006-12-08 02:37:49 -080037config ARCH_HAS_ILOG2_U32
38 bool
39 default n
40
41config ARCH_HAS_ILOG2_U64
42 bool
43 default n
44
Akinobu Mitaf6e02132006-03-26 01:39:23 -080045config GENERIC_FIND_NEXT_BIT
46 bool
47 default y
48
49config GENERIC_HWEIGHT
50 bool
51 default y
52
Yoshinori Satoc728d6042007-05-06 14:50:35 -070053config GENERIC_HARDIRQS
54 bool
55 default y
56
Linus Torvalds1da177e2005-04-16 15:20:36 -070057config GENERIC_CALIBRATE_DELAY
58 bool
59 default y
60
john stultzaeecf3142007-05-06 14:50:34 -070061config GENERIC_TIME
62 bool
63 default y
64
Ingo Molnar06027bd2006-02-14 13:53:15 -080065config TIME_LOW_RES
66 bool
67 default y
68
David Howellsb0b933c2008-02-08 04:19:27 -080069config ARCH_SUPPORTS_AOUT
70 def_bool y
71
Al Viro5ea81762007-02-11 15:41:31 +000072config NO_IOPORT
73 def_bool y
74
Dan Williams1b0fac42007-07-15 23:40:26 -070075config NO_DMA
76 def_bool y
77
Linus Torvalds1da177e2005-04-16 15:20:36 -070078config ISA
79 bool
80 default y
81
82config PCI
83 bool
84 default n
85
H. Peter Anvinbdc80782008-02-08 04:21:26 -080086config HZ
87 int
88 default 100
89
Linus Torvalds1da177e2005-04-16 15:20:36 -070090source "init/Kconfig"
91
92source "arch/h8300/Kconfig.cpu"
93
94menu "Executable file formats"
95
96source "fs/Kconfig.binfmt"
97
98endmenu
99
Sam Ravnborgd5950b42005-07-11 21:03:49 -0700100source "net/Kconfig"
101
Linus Torvalds1da177e2005-04-16 15:20:36 -0700102source "drivers/base/Kconfig"
103
104source "drivers/mtd/Kconfig"
105
106source "drivers/block/Kconfig"
107
108source "drivers/ide/Kconfig"
109
110source "arch/h8300/Kconfig.ide"
111
Sam Ravnborgd5950b42005-07-11 21:03:49 -0700112source "drivers/net/Kconfig"
Linus Torvalds1da177e2005-04-16 15:20:36 -0700113
114#
115# input - input/joystick depends on it. As does USB.
116#
117source "drivers/input/Kconfig"
118
119menu "Character devices"
120
121config VT
122 bool "Virtual terminal"
123 ---help---
124 If you say Y here, you will get support for terminal devices with
125 display and keyboard devices. These are called "virtual" because you
126 can run several virtual terminals (also called virtual consoles) on
127 one physical terminal. This is rather useful, for example one
128 virtual terminal can collect system messages and warnings, another
129 one can be used for a text-mode user session, and a third could run
130 an X session, all in parallel. Switching between virtual terminals
131 is done with certain key combinations, usually Alt-<function key>.
132
133 The setterm command ("man setterm") can be used to change the
134 properties (such as colors or beeping) of a virtual terminal. The
135 man page console_codes(4) ("man console_codes") contains the special
136 character sequences that can be used to change those properties
137 directly. The fonts used on virtual terminals can be changed with
138 the setfont ("man setfont") command and the key bindings are defined
139 with the loadkeys ("man loadkeys") command.
140
141 You need at least one virtual terminal device in order to make use
142 of your keyboard and monitor. Therefore, only people configuring an
143 embedded system would want to say N here in order to save some
144 memory; the only way to log into such a system is then via a serial
145 or network connection.
146
147 If unsure, say Y, or else you won't be able to do much with your new
148 shiny Linux system :-)
149
150config VT_CONSOLE
151 bool "Support for console on virtual terminal"
152 depends on VT
153 ---help---
154 The system console is the device which receives all kernel messages
155 and warnings and which allows logins in single user mode. If you
156 answer Y here, a virtual terminal (the device used to interact with
157 a physical terminal) can be used as system console. This is the most
158 common mode of operations, so you should say Y here unless you want
159 the kernel messages be output only to a serial port (in which case
160 you should say Y to "Console on serial port", below).
161
162 If you do say Y here, by default the currently visible virtual
163 terminal (/dev/tty0) will be used as system console. You can change
164 that with a kernel command line option such as "console=tty3" which
165 would use the third virtual terminal as system console. (Try "man
166 bootparam" or see the documentation of your boot loader (lilo or
167 loadlin) about how to pass options to the kernel at boot time.)
168
169 If unsure, say Y.
170
171config HW_CONSOLE
172 bool
173 depends on VT && !S390 && !UM
174 default y
175
176comment "Unix98 PTY support"
177
178config UNIX98_PTYS
179 bool "Unix98 PTY support"
180 ---help---
181 A pseudo terminal (PTY) is a software device consisting of two
182 halves: a master and a slave. The slave device behaves identical to
183 a physical terminal; the master device is used by a process to
184 read data from and write data to the slave, thereby emulating a
185 terminal. Typical programs for the master side are telnet servers
186 and xterms.
187
188 Linux has traditionally used the BSD-like names /dev/ptyxx for
189 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
190 has a number of problems. The GNU C library glibc 2.1 and later,
191 however, supports the Unix98 naming standard: in order to acquire a
192 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
193 terminal is then made available to the process and the pseudo
194 terminal slave can be accessed as /dev/pts/<number>. What was
195 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
196
197 The entries in /dev/pts/ are created on the fly by a virtual
198 file system; therefore, if you say Y here you should say Y to
199 "/dev/pts file system for Unix98 PTYs" as well.
200
201 If you want to say Y here, you need to have the C library glibc 2.1
202 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
203 Read the instructions in <file:Documentation/Changes> pertaining to
204 pseudo terminals. It's safe to say N.
205
206config UNIX98_PTY_COUNT
207 int "Maximum number of Unix98 PTYs in use (0-2048)"
208 depends on UNIX98_PTYS
209 default "256"
210 help
211 The maximum number of Unix98 PTYs that can be used at any one time.
212 The default is 256, and should be enough for desktop systems. Server
213 machines which support incoming telnet/rlogin/ssh connections and/or
214 serve several X terminals may want to increase this: every incoming
215 connection and every xterm uses up one PTY.
216
217 When not in use, each additional set of 256 PTYs occupy
218 approximately 8 KB of kernel memory on 32-bit architectures.
219
220source "drivers/char/pcmcia/Kconfig"
221
222source "drivers/serial/Kconfig"
223
224source "drivers/i2c/Kconfig"
225
Jean Delvaread2f9312005-07-02 18:15:49 +0200226source "drivers/hwmon/Kconfig"
227
Linus Torvalds1da177e2005-04-16 15:20:36 -0700228source "drivers/usb/Kconfig"
229
230endmenu
231
232source "fs/Kconfig"
233
Linus Torvalds1da177e2005-04-16 15:20:36 -0700234source "arch/h8300/Kconfig.debug"
235
236source "security/Kconfig"
237
238source "crypto/Kconfig"
239
240source "lib/Kconfig"