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