1config H8300 2 bool 3 default y 4 select HAVE_IDE 5 select HAVE_GENERIC_HARDIRQS 6 select HAVE_UID16 7 select ARCH_WANT_IPC_PARSE_VERSION 8 select GENERIC_IRQ_SHOW 9 select GENERIC_CPU_DEVICES 10 select MODULES_USE_ELF_RELA 11 12config SYMBOL_PREFIX 13 string 14 default "_" 15 16config MMU 17 bool 18 default n 19 20config SWAP 21 bool 22 default n 23 24config ZONE_DMA 25 bool 26 default y 27 28config FPU 29 bool 30 default n 31 32config RWSEM_GENERIC_SPINLOCK 33 bool 34 default y 35 36config RWSEM_XCHGADD_ALGORITHM 37 bool 38 default n 39 40config ARCH_HAS_ILOG2_U32 41 bool 42 default n 43 44config ARCH_HAS_ILOG2_U64 45 bool 46 default n 47 48config GENERIC_HWEIGHT 49 bool 50 default y 51 52config GENERIC_CALIBRATE_DELAY 53 bool 54 default y 55 56config GENERIC_BUG 57 bool 58 depends on BUG 59 60config TIME_LOW_RES 61 bool 62 default y 63 64config NO_IOPORT 65 def_bool y 66 67config NO_DMA 68 def_bool y 69 70config ISA 71 bool 72 default y 73 74config PCI 75 bool 76 default n 77 78config HZ 79 int 80 default 100 81 82source "init/Kconfig" 83 84source "kernel/Kconfig.freezer" 85 86source "arch/h8300/Kconfig.cpu" 87 88menu "Executable file formats" 89 90source "fs/Kconfig.binfmt" 91 92endmenu 93 94source "net/Kconfig" 95 96source "drivers/base/Kconfig" 97 98source "drivers/mtd/Kconfig" 99 100source "drivers/block/Kconfig" 101 102source "drivers/ide/Kconfig" 103 104source "arch/h8300/Kconfig.ide" 105 106source "drivers/net/Kconfig" 107 108# 109# input - input/joystick depends on it. As does USB. 110# 111source "drivers/input/Kconfig" 112 113menu "Character devices" 114 115config VT 116 bool "Virtual terminal" 117 ---help--- 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>. 126 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. 134 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. 140 141 If unsure, say Y, or else you won't be able to do much with your new 142 shiny Linux system :-) 143 144config VT_CONSOLE 145 bool "Support for console on virtual terminal" 146 depends on VT 147 ---help--- 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). 155 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.) 162 163 If unsure, say Y. 164 165config HW_CONSOLE 166 bool 167 depends on VT 168 default y 169 170comment "Unix98 PTY support" 171 172config UNIX98_PTYS 173 bool "Unix98 PTY support" 174 ---help--- 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 180 and xterms. 181 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. 190 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. 194 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. 199 200source "drivers/char/pcmcia/Kconfig" 201 202source "drivers/tty/serial/Kconfig" 203 204source "drivers/i2c/Kconfig" 205 206source "drivers/hwmon/Kconfig" 207 208source "drivers/usb/Kconfig" 209 210source "drivers/uwb/Kconfig" 211 212endmenu 213 214source "drivers/staging/Kconfig" 215 216source "fs/Kconfig" 217 218source "arch/h8300/Kconfig.debug" 219 220source "security/Kconfig" 221 222source "crypto/Kconfig" 223 224source "lib/Kconfig" 225