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