drivers/char/Kconfig

   1 #
   2 # Character device configuration
   3 #
   4
   5 menu "Character devices"
   6
   7 source "drivers/tty/Kconfig"
   8
   9 config DEVKMEM
  10         bool "/dev/kmem virtual device support"
  11         default y
  12         help
  13           Say Y here if you want to support the /dev/kmem device. The
  14           /dev/kmem device is rarely used, but can be used for certain
  15           kind of kernel debugging operations.
  16           When in doubt, say "N".
  17
  18 config COMPUTONE
  19         tristate "Computone IntelliPort Plus serial support"
  20         depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
  21         ---help---
  22           This driver supports the entire family of Intelliport II/Plus
  23           controllers with the exception of the MicroChannel controllers and
  24           products previous to the Intelliport II. These are multiport cards,
  25           which give you many serial ports. You would need something like this
  26           to connect more than two modems to your Linux box, for instance in
  27           order to become a dial-in server. If you have a card like that, say
  28           Y here and read <file:Documentation/serial/computone.txt>.
  29
  30           To compile this driver as module, choose M here: the
  31           module will be called ip2.
  32
  33 config DIGIEPCA
  34         tristate "Digiboard Intelligent Async Support"
  35         depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
  36         ---help---
  37           This is a driver for Digi International's Xx, Xeve, and Xem series
  38           of cards which provide multiple serial ports. You would need
  39           something like this to connect more than two modems to your Linux
  40           box, for instance in order to become a dial-in server. This driver
  41           supports the original PC (ISA) boards as well as PCI, and EISA. If
  42           you have a card like this, say Y here and read the file
  43           <file:Documentation/serial/digiepca.txt>.
  44
  45           To compile this driver as a module, choose M here: the
  46           module will be called epca.
  47
  48 config RISCOM8
  49         tristate "SDL RISCom/8 card support"
  50         depends on SERIAL_NONSTANDARD
  51         help
  52           This is a driver for the SDL Communications RISCom/8 multiport card,
  53           which gives you many serial ports. You would need something like
  54           this to connect more than two modems to your Linux box, for instance
  55           in order to become a dial-in server. If you have a card like that,
  56           say Y here and read the file <file:Documentation/serial/riscom8.txt>.
  57
  58           Also it's possible to say M here and compile this driver as kernel
  59           loadable module; the module will be called riscom8.
  60
  61 config SPECIALIX
  62         tristate "Specialix IO8+ card support"
  63         depends on SERIAL_NONSTANDARD
  64         help
  65           This is a driver for the Specialix IO8+ multiport card (both the
  66           ISA and the PCI version) which gives you many serial ports. You
  67           would need something like this to connect more than two modems to
  68           your Linux box, for instance in order to become a dial-in server.
  69
  70           If you have a card like that, say Y here and read the file
  71           <file:Documentation/serial/specialix.txt>. Also it's possible to say
  72           M here and compile this driver as kernel loadable module which will be
  73           called specialix.
  74
  75 config SX
  76         tristate "Specialix SX (and SI) card support"
  77         depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA) && BROKEN
  78         help
  79           This is a driver for the SX and SI multiport serial cards.
  80           Please read the file <file:Documentation/serial/sx.txt> for details.
  81
  82           This driver can only be built as a module ( = code which can be
  83           inserted in and removed from the running kernel whenever you want).
  84           The module will be called sx. If you want to do that, say M here.
  85
  86 config RIO
  87         tristate "Specialix RIO system support"
  88         depends on SERIAL_NONSTANDARD && BROKEN
  89         help
  90           This is a driver for the Specialix RIO, a smart serial card which
  91           drives an outboard box that can support up to 128 ports.  Product
  92           information is at <http://www.perle.com/support/documentation.html#multiport>.
  93           There are both ISA and PCI versions.
  94
  95 config RIO_OLDPCI
  96         bool "Support really old RIO/PCI cards"
  97         depends on RIO
  98         help
  99           Older RIO PCI cards need some initialization-time configuration to
 100           determine the IRQ and some control addresses.  If you have a RIO and
 101           this doesn't seem to work, try setting this to Y.
 102
 103 config STALDRV
 104         bool "Stallion multiport serial support"
 105         depends on SERIAL_NONSTANDARD
 106         help
 107           Stallion cards give you many serial ports.  You would need something
 108           like this to connect more than two modems to your Linux box, for
 109           instance in order to become a dial-in server.  If you say Y here,
 110           you will be asked for your specific card model in the next
 111           questions.  Make sure to read <file:Documentation/serial/stallion.txt>
 112           in this case.  If you have never heard about all this, it's safe to
 113           say N.
 114
 115 config STALLION
 116         tristate "Stallion EasyIO or EC8/32 support"
 117         depends on STALDRV && (ISA || EISA || PCI)
 118         help
 119           If you have an EasyIO or EasyConnection 8/32 multiport Stallion
 120           card, then this is for you; say Y.  Make sure to read
 121           <file:Documentation/serial/stallion.txt>.
 122
 123           To compile this driver as a module, choose M here: the
 124           module will be called stallion.
 125
 126 config ISTALLION
 127         tristate "Stallion EC8/64, ONboard, Brumby support"
 128         depends on STALDRV && (ISA || EISA || PCI)
 129         help
 130           If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
 131           serial multiport card, say Y here. Make sure to read
 132           <file:Documentation/serial/stallion.txt>.
 133
 134           To compile this driver as a module, choose M here: the
 135           module will be called istallion.
 136
 137 config A2232
 138         tristate "Commodore A2232 serial support (EXPERIMENTAL)"
 139         depends on EXPERIMENTAL && ZORRO && BROKEN
 140         ---help---
 141           This option supports the 2232 7-port serial card shipped with the
 142           Amiga 2000 and other Zorro-bus machines, dating from 1989.  At
 143           a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
 144           each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
 145           ports were connected with 8 pin DIN connectors on the card bracket,
 146           for which 8 pin to DB25 adapters were supplied. The card also had
 147           jumpers internally to toggle various pinning configurations.
 148
 149           This driver can be built as a module; but then "generic_serial"
 150           will also be built as a module. This has to be loaded before
 151           "ser_a2232". If you want to do this, answer M here.
 152
 153 config SGI_SNSC
 154         bool "SGI Altix system controller communication support"
 155         depends on (IA64_SGI_SN2 || IA64_GENERIC)
 156         help
 157           If you have an SGI Altix and you want to enable system
 158           controller communication from user space (you want this!),
 159           say Y.  Otherwise, say N.
 160
 161 config SGI_TIOCX
 162        bool "SGI TIO CX driver support"
 163        depends on (IA64_SGI_SN2 || IA64_GENERIC)
 164        help
 165          If you have an SGI Altix and you have fpga devices attached
 166          to your TIO, say Y here, otherwise say N.
 167
 168 config SGI_MBCS
 169        tristate "SGI FPGA Core Services driver support"
 170        depends on SGI_TIOCX
 171        help
 172          If you have an SGI Altix with an attached SABrick
 173          say Y or M here, otherwise say N.
 174
 175 source "drivers/tty/serial/Kconfig"
 176
 177 config TTY_PRINTK
 178         bool "TTY driver to output user messages via printk"
 179         depends on EXPERT
 180         default n
 181         ---help---
 182           If you say Y here, the support for writing user messages (i.e.
 183           console messages) via printk is available.
 184
 185           The feature is useful to inline user messages with kernel
 186           messages.
 187           In order to use this feature, you should output user messages
 188           to /dev/ttyprintk or redirect console to this TTY.
 189
 190           If unsure, say N.
 191
 192 config BRIQ_PANEL
 193         tristate 'Total Impact briQ front panel driver'
 194         depends on PPC_CHRP
 195         ---help---
 196           The briQ is a small footprint CHRP computer with a frontpanel VFD, a
 197           tristate led and two switches. It is the size of a CDROM drive.
 198
 199           If you have such one and want anything showing on the VFD then you
 200           must answer Y here.
 201
 202           To compile this driver as a module, choose M here: the
 203           module will be called briq_panel.
 204
 205           It's safe to say N here.
 206
 207 config BFIN_OTP
 208         tristate "Blackfin On-Chip OTP Memory Support"
 209         depends on BLACKFIN && (BF51x || BF52x || BF54x)
 210         default y
 211         help
 212           If you say Y here, you will get support for a character device
 213           interface into the One Time Programmable memory pages that are
 214           stored on the Blackfin processor.  This will not get you access
 215           to the secure memory pages however.  You will need to write your
 216           own secure code and reader for that.
 217
 218           To compile this driver as a module, choose M here: the module
 219           will be called bfin-otp.
 220
 221           If unsure, it is safe to say Y.
 222
 223 config BFIN_OTP_WRITE_ENABLE
 224         bool "Enable writing support of OTP pages"
 225         depends on BFIN_OTP
 226         default n
 227         help
 228           If you say Y here, you will enable support for writing of the
 229           OTP pages.  This is dangerous by nature as you can only program
 230           the pages once, so only enable this option when you actually
 231           need it so as to not inadvertently clobber data.
 232
 233           If unsure, say N.
 234
 235 config PRINTER
 236         tristate "Parallel printer support"
 237         depends on PARPORT
 238         ---help---
 239           If you intend to attach a printer to the parallel port of your Linux
 240           box (as opposed to using a serial printer; if the connector at the
 241           printer has 9 or 25 holes ["female"], then it's serial), say Y.
 242           Also read the Printing-HOWTO, available from
 243           <http://www.tldp.org/docs.html#howto>.
 244
 245           It is possible to share one parallel port among several devices
 246           (e.g. printer and ZIP drive) and it is safe to compile the
 247           corresponding drivers into the kernel.
 248
 249           To compile this driver as a module, choose M here and read
 250           <file:Documentation/parport.txt>.  The module will be called lp.
 251
 252           If you have several parallel ports, you can specify which ports to
 253           use with the "lp" kernel command line option.  (Try "man bootparam"
 254           or see the documentation of your boot loader (lilo or loadlin) about
 255           how to pass options to the kernel at boot time.)  The syntax of the
 256           "lp" command line option can be found in <file:drivers/char/lp.c>.
 257
 258           If you have more than 8 printers, you need to increase the LP_NO
 259           macro in lp.c and the PARPORT_MAX macro in parport.h.
 260
 261 config LP_CONSOLE
 262         bool "Support for console on line printer"
 263         depends on PRINTER
 264         ---help---
 265           If you want kernel messages to be printed out as they occur, you
 266           can have a console on the printer. This option adds support for
 267           doing that; to actually get it to happen you need to pass the
 268           option "console=lp0" to the kernel at boot time.
 269
 270           If the printer is out of paper (or off, or unplugged, or too
 271           busy..) the kernel will stall until the printer is ready again.
 272           By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
 273           can make the kernel continue when this happens,
 274           but it'll lose the kernel messages.
 275
 276           If unsure, say N.
 277
 278 config PPDEV
 279         tristate "Support for user-space parallel port device drivers"
 280         depends on PARPORT
 281         ---help---
 282           Saying Y to this adds support for /dev/parport device nodes.  This
 283           is needed for programs that want portable access to the parallel
 284           port, for instance deviceid (which displays Plug-and-Play device
 285           IDs).
 286
 287           This is the parallel port equivalent of SCSI generic support (sg).
 288           It is safe to say N to this -- it is not needed for normal printing
 289           or parallel port CD-ROM/disk support.
 290
 291           To compile this driver as a module, choose M here: the
 292           module will be called ppdev.
 293
 294           If unsure, say N.
 295
 296 source "drivers/tty/hvc/Kconfig"
 297
 298 config VIRTIO_CONSOLE
 299         tristate "Virtio console"
 300         depends on VIRTIO
 301         select HVC_DRIVER
 302         help
 303           Virtio console for use with lguest and other hypervisors.
 304
 305           Also serves as a general-purpose serial device for data
 306           transfer between the guest and host.  Character devices at
 307           /dev/vportNpn will be created when corresponding ports are
 308           found, where N is the device number and n is the port number
 309           within that device.  If specified by the host, a sysfs
 310           attribute called 'name' will be populated with a name for
 311           the port which can be used by udev scripts to create a
 312           symlink to the device.
 313
 314 config IBM_BSR
 315         tristate "IBM POWER Barrier Synchronization Register support"
 316         depends on PPC_PSERIES
 317         help
 318           This devices exposes a hardware mechanism for fast synchronization
 319           of threads across a large system which avoids bouncing a cacheline
 320           between several cores on a system
 321
 322 source "drivers/char/ipmi/Kconfig"
 323
 324 config DS1620
 325         tristate "NetWinder thermometer support"
 326         depends on ARCH_NETWINDER
 327         help
 328           Say Y here to include support for the thermal management hardware
 329           found in the NetWinder. This driver allows the user to control the
 330           temperature set points and to read the current temperature.
 331
 332           It is also possible to say M here to build it as a module (ds1620)
 333           It is recommended to be used on a NetWinder, but it is not a
 334           necessity.
 335
 336 config NWBUTTON
 337         tristate "NetWinder Button"
 338         depends on ARCH_NETWINDER
 339         ---help---
 340           If you say Y here and create a character device node /dev/nwbutton
 341           with major and minor numbers 10 and 158 ("man mknod"), then every
 342           time the orange button is pressed a number of times, the number of
 343           times the button was pressed will be written to that device.
 344
 345           This is most useful for applications, as yet unwritten, which
 346           perform actions based on how many times the button is pressed in a
 347           row.
 348
 349           Do not hold the button down for too long, as the driver does not
 350           alter the behaviour of the hardware reset circuitry attached to the
 351           button; it will still execute a hard reset if the button is held
 352           down for longer than approximately five seconds.
 353
 354           To compile this driver as a module, choose M here: the
 355           module will be called nwbutton.
 356
 357           Most people will answer Y to this question and "Reboot Using Button"
 358           below to be able to initiate a system shutdown from the button.
 359
 360 config NWBUTTON_REBOOT
 361         bool "Reboot Using Button"
 362         depends on NWBUTTON
 363         help
 364           If you say Y here, then you will be able to initiate a system
 365           shutdown and reboot by pressing the orange button a number of times.
 366           The number of presses to initiate the shutdown is two by default,
 367           but this can be altered by modifying the value of NUM_PRESSES_REBOOT
 368           in nwbutton.h and recompiling the driver or, if you compile the
 369           driver as a module, you can specify the number of presses at load
 370           time with "insmod button reboot_count=<something>".
 371
 372 config NWFLASH
 373         tristate "NetWinder flash support"
 374         depends on ARCH_NETWINDER
 375         ---help---
 376           If you say Y here and create a character device /dev/flash with
 377           major 10 and minor 160 you can manipulate the flash ROM containing
 378           the NetWinder firmware. Be careful as accidentally overwriting the
 379           flash contents can render your computer unbootable. On no account
 380           allow random users access to this device. :-)
 381
 382           To compile this driver as a module, choose M here: the
 383           module will be called nwflash.
 384
 385           If you're not sure, say N.
 386
 387 source "drivers/char/hw_random/Kconfig"
 388
 389 config NVRAM
 390         tristate "/dev/nvram support"
 391         depends on ATARI || X86 || (ARM && RTC_DRV_CMOS) || GENERIC_NVRAM
 392         ---help---
 393           If you say Y here and create a character special file /dev/nvram
 394           with major number 10 and minor number 144 using mknod ("man mknod"),
 395           you get read and write access to the extra bytes of non-volatile
 396           memory in the real time clock (RTC), which is contained in every PC
 397           and most Ataris.  The actual number of bytes varies, depending on the
 398           nvram in the system, but is usually 114 (128-14 for the RTC).
 399
 400           This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
 401           on Ataris. /dev/nvram may be used to view settings there, or to
 402           change them (with some utility). It could also be used to frequently
 403           save a few bits of very important data that may not be lost over
 404           power-off and for which writing to disk is too insecure. Note
 405           however that most NVRAM space in a PC belongs to the BIOS and you
 406           should NEVER idly tamper with it. See Ralf Brown's interrupt list
 407           for a guide to the use of CMOS bytes by your BIOS.
 408
 409           On Atari machines, /dev/nvram is always configured and does not need
 410           to be selected.
 411
 412           To compile this driver as a module, choose M here: the
 413           module will be called nvram.
 414
 415 #
 416 # These legacy RTC drivers just cause too many conflicts with the generic
 417 # RTC framework ... let's not even try to coexist any more.
 418 #
 419 if RTC_LIB=n
 420
 421 config RTC
 422         tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)"
 423         depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \
 424                         && !ARM && !SUPERH && !S390 && !AVR32 && !BLACKFIN
 425         ---help---
 426           If you say Y here and create a character special file /dev/rtc with
 427           major number 10 and minor number 135 using mknod ("man mknod"), you
 428           will get access to the real time clock (or hardware clock) built
 429           into your computer.
 430
 431           Every PC has such a clock built in. It can be used to generate
 432           signals from as low as 1Hz up to 8192Hz, and can also be used
 433           as a 24 hour alarm. It reports status information via the file
 434           /proc/driver/rtc and its behaviour is set by various ioctls on
 435           /dev/rtc.
 436
 437           If you run Linux on a multiprocessor machine and said Y to
 438           "Symmetric Multi Processing" above, you should say Y here to read
 439           and set the RTC in an SMP compatible fashion.
 440
 441           If you think you have a use for such a device (such as periodic data
 442           sampling), then say Y here, and read <file:Documentation/rtc.txt>
 443           for details.
 444
 445           To compile this driver as a module, choose M here: the
 446           module will be called rtc.
 447
 448 config JS_RTC
 449         tristate "Enhanced Real Time Clock Support"
 450         depends on SPARC32 && PCI
 451         ---help---
 452           If you say Y here and create a character special file /dev/rtc with
 453           major number 10 and minor number 135 using mknod ("man mknod"), you
 454           will get access to the real time clock (or hardware clock) built
 455           into your computer.
 456
 457           Every PC has such a clock built in. It can be used to generate
 458           signals from as low as 1Hz up to 8192Hz, and can also be used
 459           as a 24 hour alarm. It reports status information via the file
 460           /proc/driver/rtc and its behaviour is set by various ioctls on
 461           /dev/rtc.
 462
 463           If you think you have a use for such a device (such as periodic data
 464           sampling), then say Y here, and read <file:Documentation/rtc.txt>
 465           for details.
 466
 467           To compile this driver as a module, choose M here: the
 468           module will be called js-rtc.
 469
 470 config GEN_RTC
 471         tristate "Generic /dev/rtc emulation"
 472         depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH && !AVR32 && !BLACKFIN
 473         ---help---
 474           If you say Y here and create a character special file /dev/rtc with
 475           major number 10 and minor number 135 using mknod ("man mknod"), you
 476           will get access to the real time clock (or hardware clock) built
 477           into your computer.
 478
 479           It reports status information via the file /proc/driver/rtc and its
 480           behaviour is set by various ioctls on /dev/rtc. If you enable the
 481           "extended RTC operation" below it will also provide an emulation
 482           for RTC_UIE which is required by some programs and may improve
 483           precision in some cases.
 484
 485           To compile this driver as a module, choose M here: the
 486           module will be called genrtc.
 487
 488 config GEN_RTC_X
 489         bool "Extended RTC operation"
 490         depends on GEN_RTC
 491         help
 492           Provides an emulation for RTC_UIE which is required by some programs
 493           and may improve precision of the generic RTC support in some cases.
 494
 495 config EFI_RTC
 496         bool "EFI Real Time Clock Services"
 497         depends on IA64
 498
 499 config DS1302
 500         tristate "DS1302 RTC support"
 501         depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
 502         help
 503           If you say Y here and create a character special file /dev/rtc with
 504           major number 121 and minor number 0 using mknod ("man mknod"), you
 505           will get access to the real time clock (or hardware clock) built
 506           into your computer.
 507
 508 endif # RTC_LIB
 509
 510 config DTLK
 511         tristate "Double Talk PC internal speech card support"
 512         depends on ISA
 513         help
 514           This driver is for the DoubleTalk PC, a speech synthesizer
 515           manufactured by RC Systems (<http://www.rcsys.com/>).  It is also
 516           called the `internal DoubleTalk'.
 517
 518           To compile this driver as a module, choose M here: the
 519           module will be called dtlk.
 520
 521 config XILINX_HWICAP
 522         tristate "Xilinx HWICAP Support"
 523         depends on XILINX_VIRTEX || MICROBLAZE
 524         help
 525           This option enables support for Xilinx Internal Configuration
 526           Access Port (ICAP) driver.  The ICAP is used on Xilinx Virtex
 527           FPGA platforms to partially reconfigure the FPGA at runtime.
 528
 529           If unsure, say N.
 530
 531 config R3964
 532         tristate "Siemens R3964 line discipline"
 533         ---help---
 534           This driver allows synchronous communication with devices using the
 535           Siemens R3964 packet protocol. Unless you are dealing with special
 536           hardware like PLCs, you are unlikely to need this.
 537
 538           To compile this driver as a module, choose M here: the
 539           module will be called n_r3964.
 540
 541           If unsure, say N.
 542
 543 config APPLICOM
 544         tristate "Applicom intelligent fieldbus card support"
 545         depends on PCI
 546         ---help---
 547           This driver provides the kernel-side support for the intelligent
 548           fieldbus cards made by Applicom International. More information
 549           about these cards can be found on the WWW at the address
 550           <http://www.applicom-int.com/>, or by email from David Woodhouse
 551           <dwmw2@infradead.org>.
 552
 553           To compile this driver as a module, choose M here: the
 554           module will be called applicom.
 555
 556           If unsure, say N.
 557
 558 config SONYPI
 559         tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
 560         depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
 561         ---help---
 562           This driver enables access to the Sony Programmable I/O Control
 563           Device which can be found in many (all ?) Sony Vaio laptops.
 564
 565           If you have one of those laptops, read
 566           <file:Documentation/laptops/sonypi.txt>, and say Y or M here.
 567
 568           To compile this driver as a module, choose M here: the
 569           module will be called sonypi.
 570
 571 config GPIO_TB0219
 572         tristate "TANBAC TB0219 GPIO support"
 573         depends on TANBAC_TB022X
 574         select GPIO_VR41XX
 575
 576 source "drivers/char/pcmcia/Kconfig"
 577
 578 config MWAVE
 579         tristate "ACP Modem (Mwave) support"
 580         depends on X86
 581         select SERIAL_8250
 582         ---help---
 583           The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
 584           kernel driver and a user level application. Together these components
 585           support direct attachment to public switched telephone networks (PSTNs)
 586           and support selected world wide countries.
 587
 588           This version of the ACP Modem driver supports the IBM Thinkpad 600E,
 589           600, and 770 that include on board ACP modem hardware.
 590
 591           The modem also supports the standard communications port interface
 592           (ttySx) and is compatible with the Hayes AT Command Set.
 593
 594           The user level application needed to use this driver can be found at
 595           the IBM Linux Technology Center (LTC) web site:
 596           <http://www.ibm.com/linux/ltc/>.
 597
 598           If you own one of the above IBM Thinkpads which has the Mwave chipset
 599           in it, say Y.
 600
 601           To compile this driver as a module, choose M here: the
 602           module will be called mwave.
 603
 604 config SCx200_GPIO
 605         tristate "NatSemi SCx200 GPIO Support"
 606         depends on SCx200
 607         select NSC_GPIO
 608         help
 609           Give userspace access to the GPIO pins on the National
 610           Semiconductor SCx200 processors.
 611
 612           If compiled as a module, it will be called scx200_gpio.
 613
 614 config PC8736x_GPIO
 615         tristate "NatSemi PC8736x GPIO Support"
 616         depends on X86_32
 617         default SCx200_GPIO     # mostly N
 618         select NSC_GPIO         # needed for support routines
 619         help
 620           Give userspace access to the GPIO pins on the National
 621           Semiconductor PC-8736x (x=[03456]) SuperIO chip.  The chip
 622           has multiple functional units, inc several managed by
 623           hwmon/pc87360 driver.  Tested with PC-87366
 624
 625           If compiled as a module, it will be called pc8736x_gpio.
 626
 627 config NSC_GPIO
 628         tristate "NatSemi Base GPIO Support"
 629         depends on X86_32
 630         # selected by SCx200_GPIO and PC8736x_GPIO
 631         # what about 2 selectors differing: m != y
 632         help
 633           Common support used (and needed) by scx200_gpio and
 634           pc8736x_gpio drivers.  If those drivers are built as
 635           modules, this one will be too, named nsc_gpio
 636
 637 config RAW_DRIVER
 638         tristate "RAW driver (/dev/raw/rawN)"
 639         depends on BLOCK
 640         help
 641           The raw driver permits block devices to be bound to /dev/raw/rawN.
 642           Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
 643           See the raw(8) manpage for more details.
 644
 645           Applications should preferably open the device (eg /dev/hda1)
 646           with the O_DIRECT flag.
 647
 648 config MAX_RAW_DEVS
 649         int "Maximum number of RAW devices to support (1-8192)"
 650         depends on RAW_DRIVER
 651         default "256"
 652         help
 653           The maximum number of RAW devices that are supported.
 654           Default is 256. Increase this number in case you need lots of
 655           raw devices.
 656
 657 config HPET
 658         bool "HPET - High Precision Event Timer" if (X86 || IA64)
 659         default n
 660         depends on ACPI
 661         help
 662           If you say Y here, you will have a miscdevice named "/dev/hpet/".  Each
 663           open selects one of the timers supported by the HPET.  The timers are
 664           non-periodic and/or periodic.
 665
 666 config HPET_MMAP
 667         bool "Allow mmap of HPET"
 668         default y
 669         depends on HPET
 670         help
 671           If you say Y here, user applications will be able to mmap
 672           the HPET registers.
 673
 674           In some hardware implementations, the page containing HPET
 675           registers may also contain other things that shouldn't be
 676           exposed to the user.  If this applies to your hardware,
 677           say N here.
 678
 679 config HANGCHECK_TIMER
 680         tristate "Hangcheck timer"
 681         depends on X86 || IA64 || PPC64 || S390
 682         help
 683           The hangcheck-timer module detects when the system has gone
 684           out to lunch past a certain margin.  It can reboot the system
 685           or merely print a warning.
 686
 687 config MMTIMER
 688         tristate "MMTIMER Memory mapped RTC for SGI Altix"
 689         depends on IA64_GENERIC || IA64_SGI_SN2
 690         default y
 691         help
 692           The mmtimer device allows direct userspace access to the
 693           Altix system timer.
 694
 695 config UV_MMTIMER
 696         tristate "UV_MMTIMER Memory mapped RTC for SGI UV"
 697         depends on X86_UV
 698         default m
 699         help
 700           The uv_mmtimer device allows direct userspace access to the
 701           UV system timer.
 702
 703 source "drivers/char/tpm/Kconfig"
 704
 705 config TELCLOCK
 706         tristate "Telecom clock driver for ATCA SBC"
 707         depends on EXPERIMENTAL && X86
 708         default n
 709         help
 710           The telecom clock device is specific to the MPCBL0010 and MPCBL0050
 711           ATCA computers and allows direct userspace access to the
 712           configuration of the telecom clock configuration settings.  This
 713           device is used for hardware synchronization across the ATCA backplane
 714           fabric.  Upon loading, the driver exports a sysfs directory,
 715           /sys/devices/platform/telco_clock, with a number of files for
 716           controlling the behavior of this hardware.
 717
 718 config DEVPORT
 719         bool
 720         depends on !M68K
 721         depends on ISA || PCI
 722         default y
 723
 724 source "drivers/s390/char/Kconfig"
 725
 726 config RAMOOPS
 727         tristate "Log panic/oops to a RAM buffer"
 728         depends on HAS_IOMEM
 729         default n
 730         help
 731           This enables panic and oops messages to be logged to a circular
 732           buffer in RAM where it can be read back at some later point.
 733
 734 endmenu
 735