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