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