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