arch/h8300/Kconfig

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