arch/h8300/Kconfig

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