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