Blame view
drivers/char/Kconfig
21.6 KB
1da177e4c Linux-2.6.12-rc2 |
1 2 3 4 5 |
# # Character device configuration # menu "Character devices" |
bdcffc5a1 tty: move Kconfig... |
6 |
source "drivers/tty/Kconfig" |
13ae66458 [PATCH] VT bindin... |
7 |
|
b781ecb6a make /dev/kmem a ... |
8 9 10 11 12 13 14 15 |
config DEVKMEM bool "/dev/kmem virtual device support" default y help Say Y here if you want to support the /dev/kmem device. The /dev/kmem device is rarely used, but can be used for certain kind of kernel debugging operations. When in doubt, say "N". |
1da177e4c Linux-2.6.12-rc2 |
16 17 18 19 20 21 22 23 |
config STALDRV bool "Stallion multiport serial support" depends on SERIAL_NONSTANDARD help Stallion cards give you many serial ports. You would need something like this to connect more than two modems to your Linux box, for instance in order to become a dial-in server. If you say Y here, you will be asked for your specific card model in the next |
31c00fc15 Create/use more d... |
24 25 |
questions. Make sure to read <file:Documentation/serial/stallion.txt> in this case. If you have never heard about all this, it's safe to |
1da177e4c Linux-2.6.12-rc2 |
26 |
say N. |
1da177e4c Linux-2.6.12-rc2 |
27 28 29 30 31 32 33 |
config SGI_SNSC bool "SGI Altix system controller communication support" depends on (IA64_SGI_SN2 || IA64_GENERIC) help If you have an SGI Altix and you want to enable system controller communication from user space (you want this!), say Y. Otherwise, say N. |
e1e19747e [IA64-SGI] Bus dr... |
34 35 36 37 38 39 40 41 42 |
config SGI_TIOCX bool "SGI TIO CX driver support" depends on (IA64_SGI_SN2 || IA64_GENERIC) help If you have an SGI Altix and you have fpga devices attached to your TIO, say Y here, otherwise say N. config SGI_MBCS tristate "SGI FPGA Core Services driver support" |
ae40aae9b [IA64-SGI] Altix ... |
43 |
depends on SGI_TIOCX |
e1e19747e [IA64-SGI] Bus dr... |
44 45 46 |
help If you have an SGI Altix with an attached SABrick say Y or M here, otherwise say N. |
ab4382d27 tty: move drivers... |
47 |
source "drivers/tty/serial/Kconfig" |
1da177e4c Linux-2.6.12-rc2 |
48 |
|
24b4b67d1 add ttyprintk driver |
49 50 |
config TTY_PRINTK bool "TTY driver to output user messages via printk" |
6a108a14f kconfig: rename C... |
51 |
depends on EXPERT |
24b4b67d1 add ttyprintk driver |
52 53 54 55 56 57 58 59 60 61 62 |
default n ---help--- If you say Y here, the support for writing user messages (i.e. console messages) via printk is available. The feature is useful to inline user messages with kernel messages. In order to use this feature, you should output user messages to /dev/ttyprintk or redirect console to this TTY. If unsure, say N. |
a45b83957 [POWERPC] Add sup... |
63 64 |
config BRIQ_PANEL tristate 'Total Impact briQ front panel driver' |
2818c5dec [POWERPC] Only of... |
65 |
depends on PPC_CHRP |
a45b83957 [POWERPC] Add sup... |
66 67 68 69 70 71 72 73 74 75 76 |
---help--- The briQ is a small footprint CHRP computer with a frontpanel VFD, a tristate led and two switches. It is the size of a CDROM drive. If you have such one and want anything showing on the VFD then you must answer Y here. To compile this driver as a module, choose M here: the module will be called briq_panel. It's safe to say N here. |
2dc63a84b Blackfin char dri... |
77 78 |
config BFIN_OTP tristate "Blackfin On-Chip OTP Memory Support" |
f69b2d7e9 bfin-otp: add BF5... |
79 |
depends on BLACKFIN && (BF51x || BF52x || BF54x) |
2dc63a84b Blackfin char dri... |
80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 |
default y help If you say Y here, you will get support for a character device interface into the One Time Programmable memory pages that are stored on the Blackfin processor. This will not get you access to the secure memory pages however. You will need to write your own secure code and reader for that. To compile this driver as a module, choose M here: the module will be called bfin-otp. If unsure, it is safe to say Y. config BFIN_OTP_WRITE_ENABLE bool "Enable writing support of OTP pages" depends on BFIN_OTP default n help If you say Y here, you will enable support for writing of the OTP pages. This is dangerous by nature as you can only program the pages once, so only enable this option when you actually need it so as to not inadvertently clobber data. If unsure, say N. |
1da177e4c Linux-2.6.12-rc2 |
104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 |
config PRINTER tristate "Parallel printer support" depends on PARPORT ---help--- If you intend to attach a printer to the parallel port of your Linux box (as opposed to using a serial printer; if the connector at the printer has 9 or 25 holes ["female"], then it's serial), say Y. Also read the Printing-HOWTO, available from <http://www.tldp.org/docs.html#howto>. It is possible to share one parallel port among several devices (e.g. printer and ZIP drive) and it is safe to compile the corresponding drivers into the kernel. To compile this driver as a module, choose M here and read <file:Documentation/parport.txt>. The module will be called lp. If you have several parallel ports, you can specify which ports to use with the "lp" kernel command line option. (Try "man bootparam" or see the documentation of your boot loader (lilo or loadlin) about how to pass options to the kernel at boot time.) The syntax of the "lp" command line option can be found in <file:drivers/char/lp.c>. If you have more than 8 printers, you need to increase the LP_NO macro in lp.c and the PARPORT_MAX macro in parport.h. config LP_CONSOLE bool "Support for console on line printer" depends on PRINTER ---help--- If you want kernel messages to be printed out as they occur, you can have a console on the printer. This option adds support for doing that; to actually get it to happen you need to pass the option "console=lp0" to the kernel at boot time. If the printer is out of paper (or off, or unplugged, or too busy..) the kernel will stall until the printer is ready again. By defining CONSOLE_LP_STRICT to 0 (at your own risk) you can make the kernel continue when this happens, but it'll lose the kernel messages. If unsure, say N. config PPDEV tristate "Support for user-space parallel port device drivers" depends on PARPORT ---help--- Saying Y to this adds support for /dev/parport device nodes. This is needed for programs that want portable access to the parallel port, for instance deviceid (which displays Plug-and-Play device IDs). This is the parallel port equivalent of SCSI generic support (sg). It is safe to say N to this -- it is not needed for normal printing or parallel port CD-ROM/disk support. To compile this driver as a module, choose M here: the module will be called ppdev. If unsure, say N. |
bdcffc5a1 tty: move Kconfig... |
164 |
source "drivers/tty/hvc/Kconfig" |
5427bcf5e hvc: add Blackfin... |
165 |
|
31610434b Virtio console dr... |
166 |
config VIRTIO_CONSOLE |
7721c494a virtio: console a... |
167 168 |
tristate "Virtio console" depends on VIRTIO |
31610434b Virtio console dr... |
169 |
select HVC_DRIVER |
7721c494a virtio: console a... |
170 171 |
help Virtio console for use with lguest and other hypervisors. |
fb08bd274 virtio: console: ... |
172 173 174 175 176 177 178 179 |
Also serves as a general-purpose serial device for data transfer between the guest and host. Character devices at /dev/vportNpn will be created when corresponding ports are found, where N is the device number and n is the port number within that device. If specified by the host, a sysfs attribute called 'name' will be populated with a name for the port which can be used by udev scripts to create a symlink to the device. |
31610434b Virtio console dr... |
180 |
|
fe9e8d537 powerpc: Add driv... |
181 182 183 184 185 186 187 |
config IBM_BSR tristate "IBM POWER Barrier Synchronization Register support" depends on PPC_PSERIES help This devices exposes a hardware mechanism for fast synchronization of threads across a large system which avoids bouncing a cacheline between several cores on a system |
1da177e4c Linux-2.6.12-rc2 |
188 |
source "drivers/char/ipmi/Kconfig" |
1da177e4c Linux-2.6.12-rc2 |
189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 |
config DS1620 tristate "NetWinder thermometer support" depends on ARCH_NETWINDER help Say Y here to include support for the thermal management hardware found in the NetWinder. This driver allows the user to control the temperature set points and to read the current temperature. It is also possible to say M here to build it as a module (ds1620) It is recommended to be used on a NetWinder, but it is not a necessity. config NWBUTTON tristate "NetWinder Button" depends on ARCH_NETWINDER ---help--- If you say Y here and create a character device node /dev/nwbutton with major and minor numbers 10 and 158 ("man mknod"), then every time the orange button is pressed a number of times, the number of times the button was pressed will be written to that device. This is most useful for applications, as yet unwritten, which perform actions based on how many times the button is pressed in a row. Do not hold the button down for too long, as the driver does not alter the behaviour of the hardware reset circuitry attached to the button; it will still execute a hard reset if the button is held down for longer than approximately five seconds. To compile this driver as a module, choose M here: the module will be called nwbutton. Most people will answer Y to this question and "Reboot Using Button" below to be able to initiate a system shutdown from the button. config NWBUTTON_REBOOT bool "Reboot Using Button" depends on NWBUTTON help If you say Y here, then you will be able to initiate a system shutdown and reboot by pressing the orange button a number of times. The number of presses to initiate the shutdown is two by default, but this can be altered by modifying the value of NUM_PRESSES_REBOOT in nwbutton.h and recompiling the driver or, if you compile the driver as a module, you can specify the number of presses at load time with "insmod button reboot_count=<something>". config NWFLASH tristate "NetWinder flash support" depends on ARCH_NETWINDER ---help--- If you say Y here and create a character device /dev/flash with major 10 and minor 160 you can manipulate the flash ROM containing the NetWinder firmware. Be careful as accidentally overwriting the flash contents can render your computer unbootable. On no account allow random users access to this device. :-) To compile this driver as a module, choose M here: the module will be called nwflash. If you're not sure, say N. |
844dd05fe [PATCH] Add new g... |
251 |
source "drivers/char/hw_random/Kconfig" |
1da177e4c Linux-2.6.12-rc2 |
252 253 |
config NVRAM tristate "/dev/nvram support" |
807a96cd0 NVRAM depends on ... |
254 |
depends on ATARI || X86 || (ARM && RTC_DRV_CMOS) || GENERIC_NVRAM |
1da177e4c Linux-2.6.12-rc2 |
255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 |
---help--- If you say Y here and create a character special file /dev/nvram with major number 10 and minor number 144 using mknod ("man mknod"), you get read and write access to the extra bytes of non-volatile memory in the real time clock (RTC), which is contained in every PC and most Ataris. The actual number of bytes varies, depending on the nvram in the system, but is usually 114 (128-14 for the RTC). This memory is conventionally called "CMOS RAM" on PCs and "NVRAM" on Ataris. /dev/nvram may be used to view settings there, or to change them (with some utility). It could also be used to frequently save a few bits of very important data that may not be lost over power-off and for which writing to disk is too insecure. Note however that most NVRAM space in a PC belongs to the BIOS and you should NEVER idly tamper with it. See Ralf Brown's interrupt list for a guide to the use of CMOS bytes by your BIOS. On Atari machines, /dev/nvram is always configured and does not need to be selected. To compile this driver as a module, choose M here: the module will be called nvram. |
c75009008 rtc: avoid legacy... |
277 278 279 280 281 |
# # These legacy RTC drivers just cause too many conflicts with the generic # RTC framework ... let's not even try to coexist any more. # if RTC_LIB=n |
1da177e4c Linux-2.6.12-rc2 |
282 |
config RTC |
e6d2bb2ba rtc: make HPET_RT... |
283 |
tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)" |
c75009008 rtc: avoid legacy... |
284 |
depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \ |
3369465ed um: switch to use... |
285 |
&& !ARM && !SUPERH && !S390 && !AVR32 && !BLACKFIN && !UML |
1da177e4c Linux-2.6.12-rc2 |
286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 |
---help--- If you say Y here and create a character special file /dev/rtc with major number 10 and minor number 135 using mknod ("man mknod"), you will get access to the real time clock (or hardware clock) built into your computer. Every PC has such a clock built in. It can be used to generate signals from as low as 1Hz up to 8192Hz, and can also be used as a 24 hour alarm. It reports status information via the file /proc/driver/rtc and its behaviour is set by various ioctls on /dev/rtc. If you run Linux on a multiprocessor machine and said Y to "Symmetric Multi Processing" above, you should say Y here to read and set the RTC in an SMP compatible fashion. If you think you have a use for such a device (such as periodic data sampling), then say Y here, and read <file:Documentation/rtc.txt> for details. To compile this driver as a module, choose M here: the module will be called rtc. |
2240598c2 [SPARC32]: Deal w... |
308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 |
config JS_RTC tristate "Enhanced Real Time Clock Support" depends on SPARC32 && PCI ---help--- If you say Y here and create a character special file /dev/rtc with major number 10 and minor number 135 using mknod ("man mknod"), you will get access to the real time clock (or hardware clock) built into your computer. Every PC has such a clock built in. It can be used to generate signals from as low as 1Hz up to 8192Hz, and can also be used as a 24 hour alarm. It reports status information via the file /proc/driver/rtc and its behaviour is set by various ioctls on /dev/rtc. If you think you have a use for such a device (such as periodic data sampling), then say Y here, and read <file:Documentation/rtc.txt> for details. To compile this driver as a module, choose M here: the module will be called js-rtc. |
1da177e4c Linux-2.6.12-rc2 |
329 330 |
config GEN_RTC tristate "Generic /dev/rtc emulation" |
3369465ed um: switch to use... |
331 |
depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH && !AVR32 && !BLACKFIN && !UML |
1da177e4c Linux-2.6.12-rc2 |
332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 |
---help--- If you say Y here and create a character special file /dev/rtc with major number 10 and minor number 135 using mknod ("man mknod"), you will get access to the real time clock (or hardware clock) built into your computer. It reports status information via the file /proc/driver/rtc and its behaviour is set by various ioctls on /dev/rtc. If you enable the "extended RTC operation" below it will also provide an emulation for RTC_UIE which is required by some programs and may improve precision in some cases. To compile this driver as a module, choose M here: the module will be called genrtc. config GEN_RTC_X bool "Extended RTC operation" depends on GEN_RTC help Provides an emulation for RTC_UIE which is required by some programs and may improve precision of the generic RTC support in some cases. config EFI_RTC bool "EFI Real Time Clock Services" depends on IA64 config DS1302 tristate "DS1302 RTC support" depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT) help If you say Y here and create a character special file /dev/rtc with major number 121 and minor number 0 using mknod ("man mknod"), you will get access to the real time clock (or hardware clock) built into your computer. |
c75009008 rtc: avoid legacy... |
366 |
endif # RTC_LIB |
1da177e4c Linux-2.6.12-rc2 |
367 368 |
config DTLK tristate "Double Talk PC internal speech card support" |
eeca7a36a [S390] Kconfig: r... |
369 |
depends on ISA |
1da177e4c Linux-2.6.12-rc2 |
370 371 372 373 374 375 376 |
help This driver is for the DoubleTalk PC, a speech synthesizer manufactured by RC Systems (<http://www.rcsys.com/>). It is also called the `internal DoubleTalk'. To compile this driver as a module, choose M here: the module will be called dtlk. |
ef141a0bb [POWERPC] Xilinx:... |
377 378 |
config XILINX_HWICAP tristate "Xilinx HWICAP Support" |
6fa612b56 microblaze: Kconf... |
379 |
depends on XILINX_VIRTEX || MICROBLAZE |
ef141a0bb [POWERPC] Xilinx:... |
380 381 382 383 384 385 |
help This option enables support for Xilinx Internal Configuration Access Port (ICAP) driver. The ICAP is used on Xilinx Virtex FPGA platforms to partially reconfigure the FPGA at runtime. If unsure, say N. |
1da177e4c Linux-2.6.12-rc2 |
386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 |
config R3964 tristate "Siemens R3964 line discipline" ---help--- This driver allows synchronous communication with devices using the Siemens R3964 packet protocol. Unless you are dealing with special hardware like PLCs, you are unlikely to need this. To compile this driver as a module, choose M here: the module will be called n_r3964. If unsure, say N. config APPLICOM tristate "Applicom intelligent fieldbus card support" depends on PCI ---help--- This driver provides the kernel-side support for the intelligent fieldbus cards made by Applicom International. More information about these cards can be found on the WWW at the address <http://www.applicom-int.com/>, or by email from David Woodhouse <dwmw2@infradead.org>. To compile this driver as a module, choose M here: the module will be called applicom. If unsure, say N. config SONYPI tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)" depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT ---help--- This driver enables access to the Sony Programmable I/O Control Device which can be found in many (all ?) Sony Vaio laptops. If you have one of those laptops, read |
018a651a9 sonypi - Move son... |
421 |
<file:Documentation/laptops/sonypi.txt>, and say Y or M here. |
1da177e4c Linux-2.6.12-rc2 |
422 423 424 |
To compile this driver as a module, choose M here: the module will be called sonypi. |
097625167 rename TANBAC TB0... |
425 426 |
config GPIO_TB0219 tristate "TANBAC TB0219 GPIO support" |
bef1f4026 kconfig: Standard... |
427 |
depends on TANBAC_TB022X |
584e1236b [PATCH] add "sele... |
428 |
select GPIO_VR41XX |
1da177e4c Linux-2.6.12-rc2 |
429 |
|
1da177e4c Linux-2.6.12-rc2 |
430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 |
source "drivers/char/pcmcia/Kconfig" config MWAVE tristate "ACP Modem (Mwave) support" depends on X86 select SERIAL_8250 ---help--- The ACP modem (Mwave) for Linux is a WinModem. It is composed of a kernel driver and a user level application. Together these components support direct attachment to public switched telephone networks (PSTNs) and support selected world wide countries. This version of the ACP Modem driver supports the IBM Thinkpad 600E, 600, and 770 that include on board ACP modem hardware. The modem also supports the standard communications port interface (ttySx) and is compatible with the Hayes AT Command Set. The user level application needed to use this driver can be found at the IBM Linux Technology Center (LTC) web site: <http://www.ibm.com/linux/ltc/>. If you own one of the above IBM Thinkpads which has the Mwave chipset in it, say Y. To compile this driver as a module, choose M here: the module will be called mwave. config SCx200_GPIO tristate "NatSemi SCx200 GPIO Support" depends on SCx200 |
7a8e2a5ea [PATCH] chardev: ... |
461 |
select NSC_GPIO |
1da177e4c Linux-2.6.12-rc2 |
462 463 464 465 466 |
help Give userspace access to the GPIO pins on the National Semiconductor SCx200 processors. If compiled as a module, it will be called scx200_gpio. |
7a8e2a5ea [PATCH] chardev: ... |
467 468 |
config PC8736x_GPIO tristate "NatSemi PC8736x GPIO Support" |
3369465ed um: switch to use... |
469 |
depends on X86_32 && !UML |
7a8e2a5ea [PATCH] chardev: ... |
470 471 472 473 474 475 476 477 478 479 480 481 |
default SCx200_GPIO # mostly N select NSC_GPIO # needed for support routines help Give userspace access to the GPIO pins on the National Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip has multiple functional units, inc several managed by hwmon/pc87360 driver. Tested with PC-87366 If compiled as a module, it will be called pc8736x_gpio. config NSC_GPIO tristate "NatSemi Base GPIO Support" |
699352c30 [PATCH] GPIO for ... |
482 |
depends on X86_32 |
7a8e2a5ea [PATCH] chardev: ... |
483 484 485 486 487 488 |
# selected by SCx200_GPIO and PC8736x_GPIO # what about 2 selectors differing: m != y help Common support used (and needed) by scx200_gpio and pc8736x_gpio drivers. If those drivers are built as modules, this one will be too, named nsc_gpio |
1da177e4c Linux-2.6.12-rc2 |
489 |
config RAW_DRIVER |
abd4aa5a9 undeprecate raw d... |
490 |
tristate "RAW driver (/dev/raw/rawN)" |
9361401eb [PATCH] BLOCK: Ma... |
491 |
depends on BLOCK |
1da177e4c Linux-2.6.12-rc2 |
492 |
help |
abd4aa5a9 undeprecate raw d... |
493 494 |
The raw driver permits block devices to be bound to /dev/raw/rawN. Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O. |
1da177e4c Linux-2.6.12-rc2 |
495 |
See the raw(8) manpage for more details. |
abd4aa5a9 undeprecate raw d... |
496 |
Applications should preferably open the device (eg /dev/hda1) |
1da177e4c Linux-2.6.12-rc2 |
497 |
with the O_DIRECT flag. |
0de502aa4 [PATCH] raw drive... |
498 |
config MAX_RAW_DEVS |
0078bff52 Allow setting of ... |
499 |
int "Maximum number of RAW devices to support (1-65536)" |
0de502aa4 [PATCH] raw drive... |
500 501 502 503 504 505 |
depends on RAW_DRIVER default "256" help The maximum number of RAW devices that are supported. Default is 256. Increase this number in case you need lots of raw devices. |
1da177e4c Linux-2.6.12-rc2 |
506 507 508 509 510 511 512 |
config HPET bool "HPET - High Precision Event Timer" if (X86 || IA64) default n depends on ACPI help If you say Y here, you will have a miscdevice named "/dev/hpet/". Each open selects one of the timers supported by the HPET. The timers are |
3cb2fccc5 Fix misc Kconfig ... |
513 |
non-periodic and/or periodic. |
1da177e4c Linux-2.6.12-rc2 |
514 |
|
1da177e4c Linux-2.6.12-rc2 |
515 516 517 518 519 520 521 522 523 524 525 526 |
config HPET_MMAP bool "Allow mmap of HPET" default y depends on HPET help If you say Y here, user applications will be able to mmap the HPET registers. In some hardware implementations, the page containing HPET registers may also contain other things that shouldn't be exposed to the user. If this applies to your hardware, say N here. |
1da177e4c Linux-2.6.12-rc2 |
527 528 |
config HANGCHECK_TIMER tristate "Hangcheck timer" |
abf3ea1b5 [S390] Kconfig: c... |
529 |
depends on X86 || IA64 || PPC64 || S390 |
1da177e4c Linux-2.6.12-rc2 |
530 531 532 533 534 535 536 537 538 539 540 541 |
help The hangcheck-timer module detects when the system has gone out to lunch past a certain margin. It can reboot the system or merely print a warning. config MMTIMER tristate "MMTIMER Memory mapped RTC for SGI Altix" depends on IA64_GENERIC || IA64_SGI_SN2 default y help The mmtimer device allows direct userspace access to the Altix system timer. |
fbd8ae106 drivers/char/uv_m... |
542 543 544 545 546 547 548 |
config UV_MMTIMER tristate "UV_MMTIMER Memory mapped RTC for SGI UV" depends on X86_UV default m help The uv_mmtimer device allows direct userspace access to the UV system timer. |
1da177e4c Linux-2.6.12-rc2 |
549 |
source "drivers/char/tpm/Kconfig" |
1a80ba882 [PATCH] Telecom C... |
550 |
config TELCLOCK |
03154a271 [PATCH] minor upd... |
551 |
tristate "Telecom clock driver for ATCA SBC" |
4d99bfac9 [PATCH] CONFIG_TE... |
552 |
depends on EXPERIMENTAL && X86 |
1a80ba882 [PATCH] Telecom C... |
553 554 |
default n help |
03154a271 [PATCH] minor upd... |
555 556 557 558 559 560 561 |
The telecom clock device is specific to the MPCBL0010 and MPCBL0050 ATCA computers and allows direct userspace access to the configuration of the telecom clock configuration settings. This device is used for hardware synchronization across the ATCA backplane fabric. Upon loading, the driver exports a sysfs directory, /sys/devices/platform/telco_clock, with a number of files for controlling the behavior of this hardware. |
1a80ba882 [PATCH] Telecom C... |
562 |
|
4f911d64e Make /dev/port co... |
563 564 565 566 567 |
config DEVPORT bool depends on !M68K depends on ISA || PCI default y |
61d48c2c3 [S390] Kconfig: u... |
568 |
source "drivers/s390/char/Kconfig" |
56d611a04 char drivers: RAM... |
569 570 |
config RAMOOPS tristate "Log panic/oops to a RAM buffer" |
b7e5d1f04 ramoops: add HAS_... |
571 |
depends on HAS_IOMEM |
56d611a04 char drivers: RAM... |
572 573 574 575 |
default n help This enables panic and oops messages to be logged to a circular buffer in RAM where it can be read back at some later point. |
73210a135 drivers/char: add... |
576 577 578 579 580 581 582 |
config MSM_SMD_PKT bool "Enable device interface for some SMD packet ports" default n depends on MSM_SMD help Enables userspace clients to read and write to some packet SMD ports via device interface for MSM chipset. |
dbcb4a1a3 arch/tile: add hy... |
583 584 585 586 587 588 589 590 591 592 |
config TILE_SROM bool "Character-device access via hypervisor to the Tilera SPI ROM" depends on TILE default y ---help--- This device provides character-level read-write access to the SROM, typically via the "0", "1", and "2" devices in /dev/srom/. The Tilera hypervisor makes the flash device appear much like a simple EEPROM, and knows how to partition a single ROM for multiple purposes. |
1da177e4c Linux-2.6.12-rc2 |
593 |
endmenu |