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