arch/h8300/Kconfig

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