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