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