arch/h8300/Kconfig

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