arch/h8300/Kconfig

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