5 select HAVE_GENERIC_HARDIRQS
6 select GENERIC_HARDIRQS_NO_DEPRECATED
28 config RWSEM_GENERIC_SPINLOCK
32 config RWSEM_XCHGADD_ALGORITHM
36 config ARCH_HAS_ILOG2_U32
40 config ARCH_HAS_ILOG2_U64
44 config GENERIC_FIND_NEXT_BIT
48 config GENERIC_HWEIGHT
52 config GENERIC_CALIBRATE_DELAY
84 source "kernel/Kconfig.freezer"
86 source "arch/h8300/Kconfig.cpu"
88 menu "Executable file formats"
90 source "fs/Kconfig.binfmt"
96 source "drivers/base/Kconfig"
98 source "drivers/mtd/Kconfig"
100 source "drivers/block/Kconfig"
102 source "drivers/ide/Kconfig"
104 source "arch/h8300/Kconfig.ide"
106 source "drivers/net/Kconfig"
109 # input - input/joystick depends on it. As does USB.
111 source "drivers/input/Kconfig"
113 menu "Character devices"
116 bool "Virtual terminal"
118 If you say Y here, you will get support for terminal devices with
119 display and keyboard devices. These are called "virtual" because you
120 can run several virtual terminals (also called virtual consoles) on
121 one physical terminal. This is rather useful, for example one
122 virtual terminal can collect system messages and warnings, another
123 one can be used for a text-mode user session, and a third could run
124 an X session, all in parallel. Switching between virtual terminals
125 is done with certain key combinations, usually Alt-<function key>.
127 The setterm command ("man setterm") can be used to change the
128 properties (such as colors or beeping) of a virtual terminal. The
129 man page console_codes(4) ("man console_codes") contains the special
130 character sequences that can be used to change those properties
131 directly. The fonts used on virtual terminals can be changed with
132 the setfont ("man setfont") command and the key bindings are defined
133 with the loadkeys ("man loadkeys") command.
135 You need at least one virtual terminal device in order to make use
136 of your keyboard and monitor. Therefore, only people configuring an
137 embedded system would want to say N here in order to save some
138 memory; the only way to log into such a system is then via a serial
139 or network connection.
141 If unsure, say Y, or else you won't be able to do much with your new
142 shiny Linux system :-)
145 bool "Support for console on virtual terminal"
148 The system console is the device which receives all kernel messages
149 and warnings and which allows logins in single user mode. If you
150 answer Y here, a virtual terminal (the device used to interact with
151 a physical terminal) can be used as system console. This is the most
152 common mode of operations, so you should say Y here unless you want
153 the kernel messages be output only to a serial port (in which case
154 you should say Y to "Console on serial port", below).
156 If you do say Y here, by default the currently visible virtual
157 terminal (/dev/tty0) will be used as system console. You can change
158 that with a kernel command line option such as "console=tty3" which
159 would use the third virtual terminal as system console. (Try "man
160 bootparam" or see the documentation of your boot loader (lilo or
161 loadlin) about how to pass options to the kernel at boot time.)
167 depends on VT && !S390 && !UM
170 comment "Unix98 PTY support"
173 bool "Unix98 PTY support"
175 A pseudo terminal (PTY) is a software device consisting of two
176 halves: a master and a slave. The slave device behaves identical to
177 a physical terminal; the master device is used by a process to
178 read data from and write data to the slave, thereby emulating a
179 terminal. Typical programs for the master side are telnet servers
182 Linux has traditionally used the BSD-like names /dev/ptyxx for
183 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
184 has a number of problems. The GNU C library glibc 2.1 and later,
185 however, supports the Unix98 naming standard: in order to acquire a
186 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
187 terminal is then made available to the process and the pseudo
188 terminal slave can be accessed as /dev/pts/<number>. What was
189 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
191 The entries in /dev/pts/ are created on the fly by a virtual
192 file system; therefore, if you say Y here you should say Y to
193 "/dev/pts file system for Unix98 PTYs" as well.
195 If you want to say Y here, you need to have the C library glibc 2.1
196 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
197 Read the instructions in <file:Documentation/Changes> pertaining to
198 pseudo terminals. It's safe to say N.
200 source "drivers/char/pcmcia/Kconfig"
202 source "drivers/serial/Kconfig"
204 source "drivers/i2c/Kconfig"
206 source "drivers/hwmon/Kconfig"
208 source "drivers/usb/Kconfig"
210 source "drivers/uwb/Kconfig"
214 source "drivers/staging/Kconfig"
218 source "arch/h8300/Kconfig.debug"
220 source "security/Kconfig"
222 source "crypto/Kconfig"