arch/h8300/Kconfig

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