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