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